Comment 24 for bug 1867036

Running in a autopkgtest-VM (x86):
- 2x all-proposed
- 1x just the new chrony from proposed

All these tests worked fine

At the same time I've prepped tests on s390x (KVM) and ppc64 (canonistack) - with all proposed.
There all tests ran successfully on both architectures.

x86(1-3):
SUMMARY:
  TOTAL 5
  PASSED 4
  FAILED 0 ()
  SKIPPED 1 (102-hwtimestamp)
ppc:
SUMMARY:
  TOTAL 5
  PASSED 4
  FAILED 0 ()
  SKIPPED 1 (102-hwtimestamp)
s390x:
SUMMARY:
  TOTAL 5
  PASSED 3
  FAILED 0 ()
  SKIPPED 2 (101-rtc 102-hwtimestamp)

With so much (probably false) confidence I re-ran the tests on the autopkgtest infrastructure.
Once as-is and once with all-proposed:
http://autopkgtest.ubuntu.com/packages/c/chrony/focal/amd64
http://autopkgtest.ubuntu.com/packages/c/chrony/focal/ppc64el
http://autopkgtest.ubuntu.com/packages/c/chrony/focal/s390x

PPC64/S390X were fixed just by these retry.
Both runs (all-proposed and just chrony from proposed) worked.

Furthermore in case this only triggers on LP to be able to iterate I put a new version to
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4000/+packages
With tests triggered from:
https://bileto.ubuntu.com/#/ticket/4000