Unfortunately, a bug ( https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1942276) meant that I've had to upload glibc again. This will trigger all the tests in the world again, but I believe it's both possible and reasonable to not actually run all these tests. We should definitely run a subset, like letting a random 10% of the tests run would make sense to me, although I don't know how to do that . Hopefully someone else does :)
Cheers, mwh On Tue, 17 Aug 2021 at 10:12, Michael Hudson-Doyle < michael.hud...@canonical.com> wrote: > So glibc 2.34 is now in impish proposed and all the autopkgtests have run. > I've started a discourse thread to coordinate handling the fallout: > https://discourse.ubuntu.com/t/migrating-glibc-2-34/23749 > > On Wed, 11 Aug 2021 at 11:49, Michael Hudson-Doyle < > michael.hud...@canonical.com> wrote: > >> Hi everyone, >> >> This is just a bit of advance notice that we'll be uploading the new >> release of glibc, 2.34, to impish in about 24 hours and are hoping we can >> get it migrated before feature freeze next week. So expect autopkgtest >> queues to be a bit clogged for a while. >> >> As Matthias mailed yesterday we have done a test rebuild with the new >> glibc and while it causes a few build failures we're working through there >> is no evidence of trouble running existing binaries so hopefully the new >> version won't be too disruptive. But finding that out is what all >> those autopkgtests are for :-) >> >> Cheers, >> mwh >> >
-- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
