test/system: Connect system tests to Meson

[HarryMichal]

A bit of plumbing in the build files has been done to accommodate the change as much as possible. If we're to use meson.build in the 'test/system' subdir we better also install the data from there.

This also adjust the CI playbooks to launch the tests via Meson by specifying the specific test suite ('system').

[softwarefactory-project-zuul[bot]]

Build failed.

:x: unit-test TIMED_OUT in 10m 48s :heavy_check_mark: system-test-fedora-rawhide SUCCESS in 16m 48s :heavy_check_mark: system-test-fedora-36 SUCCESS in 10m 36s :heavy_check_mark: system-test-fedora-35 SUCCESS in 10m 48s :heavy_check_mark: system-test-fedora-34 SUCCESS in 11m 42s

[softwarefactory-project-zuul[bot]]

Build succeeded.

:heavy_check_mark: unit-test SUCCESS in 7m 07s :heavy_check_mark: system-test-fedora-rawhide SUCCESS in 16m 00s :heavy_check_mark: system-test-fedora-36 SUCCESS in 10m 33s :heavy_check_mark: system-test-fedora-35 SUCCESS in 11m 16s :heavy_check_mark: system-test-fedora-34 SUCCESS in 12m 10s

[softwarefactory-project-zuul[bot]]

Build failed. https://softwarefactory-project.io/zuul/t/local/buildset/98aebe71640041ac9b228d1e345b36f5

:x: unit-test RETRY_LIMIT in 7m 33s :x: unit-test-migration-path-for-coreos-toolbox RETRY_LIMIT in 1m 54s :x: unit-test-restricted RETRY_LIMIT in 6m 48s :x: system-test-fedora-rawhide RETRY_LIMIT in 7m 34s :x: system-test-fedora-38 RETRY_LIMIT in 7m 20s :x: system-test-fedora-37 RETRY_LIMIT in 7m 33s

[softwarefactory-project-zuul[bot]]

Build failed. https://softwarefactory-project.io/zuul/t/local/buildset/f7859340ef014e9ca967f2732d88976e

:heavy_check_mark: unit-test SUCCESS in 8m 21s :heavy_check_mark: unit-test-migration-path-for-coreos-toolbox SUCCESS in 3m 11s :x: unit-test-restricted RETRY_LIMIT in 6m 38s :x: system-test-fedora-rawhide FAILURE in 37m 06s :heavy_check_mark: system-test-fedora-38 SUCCESS in 25m 35s :heavy_check_mark: system-test-fedora-37 SUCCESS in 25m 02s

[softwarefactory-project-zuul[bot]]

Build failed. https://softwarefactory-project.io/zuul/t/local/buildset/5a67bebfe51b41799880595f76f1dfbe

:heavy_check_mark: unit-test SUCCESS in 8m 13s :heavy_check_mark: unit-test-migration-path-for-coreos-toolbox SUCCESS in 3m 08s :heavy_check_mark: unit-test-restricted SUCCESS in 7m 04s :x: system-test-fedora-rawhide FAILURE in 35m 50s :heavy_check_mark: system-test-fedora-38 SUCCESS in 25m 09s :heavy_check_mark: system-test-fedora-37 SUCCESS in 24m 24s

[HarryMichal]

They no longer have a working counter:

This seems to be a deliberate design decision from Meson. This issue seems to be related to that. I'll ask around.

The reasons for a failure are also no longer shown

That is a known issue (https://github.com/mesonbuild/meson/issues/11185) and is yet to be resolved. We could contribute that feature but who has the time :). Until then (and most likely even after) we can upload meson-logs as an artifact.

Finally, are the codespell tests failing on Ubuntu?

Once we start uploading the log artifacts, we'll know for sure :).