Comment 55 for bug 2002043

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Checking the jammy amd64 autopkgtest runs[1], we can see that the top most one is the run for this sru. Its log[2] is showing, at the end, a good run, but if you look more carefully, there are some test failures that apparently are being ignored.

In particular:
1910s ======================================================================
1910s FAIL: test_customize_compiler (distutils.tests.test_sysconfig.SysconfigTestCase)
1910s ----------------------------------------------------------------------
1910s Traceback (most recent call last):
1910s File "/usr/lib/python2.7/distutils/tests/test_sysconfig.py", line 110, in test_customize_compiler
1910s 'env_cc --sc-cflags --env-cflags --env-cppflags')
1910s AssertionError: 'env_cc -fno-strict-aliasing --env-cflags --env-cppflags' != 'env_cc --sc-cflags --env-cflags --env-cppflags'

That is exactly the function being touched by this patch. Could we have a bit of an investigation on what's going on? Was it failing before, and keeps failing now? Is this SRU patch affecting this test?

1. https://autopkgtest.ubuntu.com/packages/python2.7/jammy/amd64
2. https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/p/python2.7/20240202_171211_eb91c@/log.gz