[Bug 1880839] Re: Clock skew on testbeds

[Balint Reczey]

We have a few options to fix the issue. The one I'd prefer would be
switching to systemd to depend on chrony as the preferred time-daemon
because timesynd turns back time and that can cause issues like this
one.

An other option is disabling systemd-timesyncd in the test VMs, that
would make the tests more reproducible but less similar to real
installations's behavour.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1880839

Title:
  Clock skew on testbeds

Status in Auto Package Testing:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Clock stepped backward on a testbed:

  https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  groovy/groovy/amd64/b/boost1.71/20200501_151103_1e387@/log.gz

  ...
  context              FAIL stderr: make[2]: Warning: File '/tmp/tmp.qPfGPM84a1/src/demo2.cpp' has modification time 0.52 s in the future
  autopkgtest [13:55:37]: test context:  - - - - - - - - - - stderr - - - - - - - - - -
  make[2]: Warning: File '/tmp/tmp.qPfGPM84a1/src/demo2.cpp' has modification time 0.52 s in the future
  make[2]: warning:  Clock skew detected.  Your build may be incomplete.
  ..

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1880839/+subscriptions