It was flaky and now resolved in proposed migration. But I'd want to understand why we fail 4/5 times.
So the debugging tests in the bileto ticket [1] will go on for a bit. [1]: https://bileto.ubuntu.com/#/ticket/4049 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/1876886 Title: chrony autopkgtest fails on armhf (groovy) Status in chrony package in Ubuntu: New Status in libcap2 package in Ubuntu: Confirmed Bug description: Test fails on armhf only: running chronyc makestep ERROR checking chronyc output OK running chronyc trimrtc ERROR checking chronyc output OK running chronyc writertc ERROR This might be a new twist on https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1863590 as it is libcap2 again. This reproduces through a bunch of retries http://autopkgtest.ubuntu.com/packages/c/chrony/groovy/armhf But as I said is armfh only: http://autopkgtest.ubuntu.com/packages/chrony Flagging update-excuse, but I won't be able to get to it immediately ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1876886/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp

