It is the build phase that fails.
Reproduced in armhf container on canonistack.
1. get the source and build deps
2. build that until it breaks
3. re-run via
$ cd ~/chrony-3.5/test/system
$ ./run -i 20 -m 2
In this repro environment I get two extra fails at:
005-scfilter Testing system call filter:
non-default settings:
extra_chronyd_options=-F -1
starting chronyd ERROR
FAIL
stopping chronyd ERROR
But also the actual issues:
007-cmdmon Testing chronyc commands:
starting chronyd OK
running chronyc makestep ERROR
checking chronyc output OK
running chronyc trimrtc ERROR
checking chronyc output OK
running chronyc writertc ERROR
checking chronyc output OK
stopping chronyd OK
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876886
Title:
chrony autopkgtest fails on armhf (groovy)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1876886/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
