autopkgtest failures: disco:
linux-oracle, linux-snapdragon: tests never passed; ignore dbus: this appears to be the same issue as is seen for systemd in bug 1829829; i'm re-running the test (again), but if it still doesn't pass I think we need to ignore it as a failure due to that bug. systemd (amd64): only failure is due to bug 1831459 systemd (ppc64el): also fails due to bug 1831459, and also has some upstream failed tests: FAILED TESTS: test/TEST-18-FAILUREACTION test/TEST-19-DELEGATE test/TEST-25-IMPORT test/TEST-27-STDOUTFILE I opened bug 1831468 to track these failures; they do not appear related/caused-by this upload. corosync (all archs): this has failed since before this upload, and looks like problem with the corosync source not being available in disco, possibly due to using disco-proposed. in any case, not caused or related to this upload and can be ignored. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1825997 Title: boot-smoke fails due to running jobs Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: Fix Committed Bug description: [impact] boot-smoke test reboots 5 times and verifies systemd is fully started up after each boot, including checking if there are any running jobs (with list-jobs). However, this test makes the assumption that no further jobs will be started after systemd reaches 'running' (or 'degraded') state, which is a false assumption. [test case] see various boot-smoke failures in autopkgtest.ubuntu.com [regression potential] possible false-positive or false-negative autopkgtest results. [other info] Note: This patch is not required for debian, because debian's boot- smoke does not include the wait for systemctl is-system-running. The problem appears to be that systemd reaches 'running' (or 'degraded') state, and then other systemd services are started. This confuses the boot-smoke test, because it sees that 'is-system-running' is done, but then it sees running jobs, which fails the test. What is starting jobs after systemd reaches running state appears to be X inside the test system. There are various services started by gnome-session and dbus-daemon. Additionally, from the artifacts of one example: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- bionic/bionic/i386/s/systemd/20190416_171327_478f6@/artifacts.tar.gz the artifacts/journal.txt shows that after the boot-smoke test causes the reboot and then re-ssh into the system after the reboot, it only gives the test system 9 seconds before deciding it has failed, and only 4 seconds after ssh'ing into the rebooted test system. Another wait is needed when checking for remaining running jobs. Or, the running jobs check could be removed entirely, and we can just trust that systemd correctly knows when it has reached running|degraded state. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
