Of course now it had to work :-/
I'm suggesting enhanced debug to Debian in
https://salsa.debian.org/debian/chrony/-/merge_requests/4
And consider this done for now.
** Changed in: libcap2 (Ubuntu)
Status: Confirmed => Invalid
** Changed in: chrony (Ubuntu)
Status: New =>
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
I have restarted it again on LP in case it was a flaky network after
all.
At the same time I have added some debug statements and prepare a bileto
ticket to run the tests there as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Ha, that was a good red-herring
It doesn't fail at this test despite all the error messages thrown out.
It does
1. build chrony without root (works with tests skipped as it isn't root)
2. passes other tests as it ERRORs but detects that the environment is the
reason for that
The actual error
At the actual build time it is skipped for being "non-root".
But I think this is as easy as now trying to set HW-time in a container.
** Also affects: chrony (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch
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
Example log:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-groovy/groovy/armhf/c/chrony/20200501_151956_0271e@/log.gz
Old issue was: https://bugzilla.kernel.org/show_bug.cgi?id=206539
and resolved in 2.32
The release notes on 2.33 are not
7 matches
Mail list logo
