Ok, the following confirms what I have assumed about glibc.
The reset let glibc pass but now we are just as broken. I remember having a discussion about that before, maybe now all changes are ready to be added.
revno: 4655
committer: Steve Langasek <email address hidden>
branch nick: hints-ubuntu
timestamp: Mon 2020-03-09 20:48:22 -0700
message:
badtest chrony
diff:
+## external testsuite downloaded at test time is incompatible with glibc 2.31
+force-reset-test chrony/3.5-5ubuntu1
+##
But that particular failure was in the sub-test "upstream-simulation-testsuite" and fixed in:
chrony/3.5-6ubuntu1 via
* debian/tests/upstream-simulation-test-suite:
- Update clknetsim version. This new version supports glibc >= 2.31 headers.
(LP: #1866753
So this is some new issue and I'll need to find what it is now.
Furthermore the PPC64 test issue seems to be a different one, that needs an extra check.
Ok, the following confirms what I have assumed about glibc.
The reset let glibc pass but now we are just as broken. I remember having a discussion about that before, maybe now all changes are ready to be added.
revno: 4655
committer: Steve Langasek <email address hidden>
branch nick: hints-ubuntu
timestamp: Mon 2020-03-09 20:48:22 -0700
message:
badtest chrony
diff:
+## external testsuite downloaded at test time is incompatible with glibc 2.31
+force-reset-test chrony/3.5-5ubuntu1
+##
But that particular failure was in the sub-test "upstream- simulation- testsuite" and fixed in: tests/upstream- simulation- test-suite:
chrony/3.5-6ubuntu1 via
* debian/
- Update clknetsim version. This new version supports glibc >= 2.31 headers.
(LP: #1866753
So this is some new issue and I'll need to find what it is now.
Furthermore the PPC64 test issue seems to be a different one, that needs an extra check.