Of course when things should be fast they are accompanied by a bunch of test errors.
I'm seeing these two: amd64 & s390x autopkgtest [14:27:33]: test run_destructive_system_tests: [----------------------- 100-clockupdate Testing update of system clock: ... checking system clock BAD ppc64: 007-cmdmon Testing chronyc commands: ... running chronyc shutdown OK stopping chronyd ERROR There were issues with HW specific clocks e.g. in VMs before - I'll have to revisit. But the chrony upload didn't really change anything so it must be other components that trigger this now. Liiking for other packages if any then IMHO it might be due to the new glibc, but I'll need to run some tests to prove that. That at least caused such issues in the past and would have been bumped at the right time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867036 Title: Focal Fossa : chronyd unable to sync system clock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1867036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
