Comment 0 for bug 1870144
Revision history for this message
| Christian Ehrhardt (paelzer) wrote chrony test 100-clockupdate flaky in autopkgtest | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
FYI Separated from bug 1867036
It seems to be racy/flaky.
It uses a comparison on "seconds" granularity.
I was adding debug to check the values it fails on.
It was somewhat reproducible in the bileto ticket (again autopkgtest infrastructure).
Therefore I inserted some debug code and re-ran it there.
Our test environment is too fast (sometimes) and hence the flakyness:
checking chronyc output OK
DEBUG before 1585747433
DEBUG before 1585747433
checking system clock BAD
That is checked with "lt" and here the results are ==.
I'll need to discuss if there is a strict reason for these to be non-equal.
Otherwise the fix might be as easy as using "-le" instead