Hello all, quick announcement for things to watch out for in PR integration tests.
After Zbigniew's meson build system work landed two days ago [1], I now set up our CI so that the "xenial-s390x" test builds using meson, while i386 and amd64 continue to run the classic autotools build. I initially set it up for amd64, but that causes reboot failures in the "boot-smoke" test which need some time to get investigated, as this doesn't reproduce in QEMU. Semaphore also still runs autotools. I just backported the necessary ninja/meson packages and I'll look at setting up another job for meson in the next days. While I was at it, I also fixed the "xenial-*" tests to rebase a PR to current master before building/testing. Until now they tested the literal PR code, which was an oversight. Now what is being built and tested reflects what will be landed much more closely, and this will also avoid the current PRs to suddenly fail because they weren't done against meson yet. But this rebase step also introduces a new failure mode, although github should already detect un-mergeability in most cases. I test-drived this in my old guinea pig [2] PR, which is ancient. I. e. that it succeeds proves that rebasing worked, and that the downstream packaging works correctly (enough) with meson. However, it currently fails with some linker errors [3], these still need to get fixed. Once they do, we'll have CI for the meson build and from then on hopefully don't break it any more. Thanks, Pitti [1] https://github.com/systemd/systemd/pull/5704 [2] https://github.com/systemd/systemd/pull/4611 [3] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-pitti-systemd-semaphore/xenial/s390x/s/systemd-upstream/20170427_101741_d8343@/log.gz _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
