I grabbed one of the focal failures from comment #49, mercurial: focal amd64 mercurial 5.3.1-1ubuntu1 4 python2.7/2.7.18-1~20.04.4
That is indeed mostly red in [1], including the recent run with python2.7 from this SRU. And it's not showing up as a failure in the excuses[2] report. But it's hinted[3] on s390x: # mercurial tests are flakey in focal https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956697 force-badtest mercurial/5.3.1-1ubuntu1/s390x So that would explain it not being flagged for s390x, but not for amd64. I'm still puzzled: I didn't find another hint. I retriggered the mercurial amd64 test, let's see if a new result refreshes the report. 1. https://autopkgtest.ubuntu.com/packages/m/mercurial/focal/amd64 2. https://ubuntu-archive-team.ubuntu.com/proposed-migration/focal/update_excuses.html#python2.7 3. https://git.launchpad.net/~ubuntu-release/britney/+git/hints-ubuntu/commit/?id=8f4fd5462e98199c76909d3510911c573f0fa071 ** Bug watch added: Debian Bug tracker #956697 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956697 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2002043 Title: Python extension modules get built using wrong compiler flags with python2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/2002043/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
