Just to clarify, I think that it would be better to turn off the test globally because we know it's flaky and unstable and we generally never roll out globally flaky tests so as not to annoy contributors (I'm not sure why Ubuntu CI should be different from any other CI system we use upstream). And then, it should be possible to run the test over and over again somewhere to see what fails updating the list along the way.
-- 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/1829829 Title: Ubuntu CI has been flaky for a week Status in systemd package in Ubuntu: Confirmed Bug description: It was originally reported in https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days ago. To judge from the logs VMs can't be rebooted there: ``` Ubuntu 18.04.2 LTS autopkgtest ttyS0 autopkgtest login: --------------------------------------------------- ------- nova show 91e76a78-d05c-412a-b383-55a26010ae69 (adt-bionic-amd64-systemd-upstream-20190516-051604) ------ +--------------------------------------+------------------------------------------------------------------------------------+ | Property | Value | +--------------------------------------+------------------------------------------------------------------------------------+ | OS-DCF:diskConfig | MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | euler | | OS-EXT-SRV-ATTR:hypervisor_hostname | euler.lcy01.scalingstack | | OS-EXT-SRV-ATTR:instance_name | instance-003d216a | | OS-EXT-STS:power_state | 1 | | OS-EXT-STS:task_state | - | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2019-05-16T07:00:42.000000 | | OS-SRV-USG:terminated_at | - | | accessIPv4 | | | accessIPv6 | | | config_drive | | | created | 2019-05-16T07:00:33Z | | flavor | autopkgtest (f878e70e-9991-46e0-ba02-8ea159a71656) | | hostId | 1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd | | id | 91e76a78-d05c-412a-b383-55a26010ae69 | | image | adt/ubuntu-bionic-amd64-server-20190516.img (d00bf12c-467e-433f-a4f5-15720f13bff1) | | key_name | testbed-juju-prod-ues-proposed-migration-machine-11 | | metadata | {} | | name | adt-bionic-amd64-systemd-upstream-20190516-051604 | | net_ues_proposed_migration network | 10.42.40.13 | | os-extended-volumes:volumes_attached | [] | | progress | 0 | | security_groups | autopkgtest@lcy01-27.secgroup | | status | ACTIVE | | tenant_id | afaef86b96dd4828a1ed5ee395ea1421 | | updated | 2019-05-16T07:00:42Z | | user_id | 8524250971084851b3792a68fbc398dd | +--------------------------------------+------------------------------------------------------------------------------------+ --------------------------------------------------- <VirtSubproc>: failure: Timed out on waiting for ssh connection autopkgtest [07:07:45]: ERROR: testbed failure: cannot send to testbed: [Errno 32] Broken pipe ``` Though judging by https://github.com/systemd/systemd/pull/12626, it appears that sometimes the tests pass. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1829829/+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
