Comment 58 for bug 2002043

The only focal autopkgtest that really has me confused in the python2.7 failure. This is due to a unit test that fails. The strange thing is that this unit test actually fails in the Jammy autopkgtest, but the Jammy autopkgtest passes anyways. It has always been like this.

You will see

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

Which has always been like this - my patch did not cause this change.

I think this should be safe to ignore simply because the package has always been like this, and if it is an issue we should've found a bug for it by now.

I tried to see if the Debian autopkgtest also sees this behavior, but unfortunately those logs have been removed due to the retention policy.

I'm curious if the change I am doing will fix this unit test... So I created a PPA with the change enabled by default and will come back when the results are ready.