Comment 9 for bug 1836929

I have reviewed and Nacked the MP for the force-badtest.
Lets continue here, summary:

Summarizing:
- actually two issues seem to break chrony tests
  1. some yet unknown change in a package added stderr which needs [1] for bug 1836882
     The new thing is that this now also affects Disco
  2. (this bug) due to upstream clksim changes things don't properly match anymore.
     We need [2] and maybe [3]
- We will not need to add a badtest, we just fix the tests and iproute will then pass testing
  against the new version.

I was able to reproduce that locally and will create a branch/ppa/test for it that you later on (if I can make it in time) can take a look at.

[1]: https://git.launchpad.net/ubuntu/+source/chrony/commit/?id=ebdec551cbb6a0986bfd489e4ca90ef103e37a07
[2]: https://salsa.debian.org/debian/chrony/commit/bb79b3247c1938b40f7532a4aa445da16148f822
[3]: https://salsa.debian.org/debian/chrony/commit/bc402d6270fef5b6ed1b166abe198efeb78e0b16