New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test failure in test_sysconfig_module #59389
Comments
On default, have this single failure on my box (Gentoo amd64): ====================================================================== Traceback (most recent call last):
File "/home/gbr/devel/python/Lib/distutils/tests/test_sysconfig.py", line 105, in test_sysconfig_module
self.assertEqual(global_sysconfig.get_config_var('LDSHARED'),sysconfig.get_config_var('LDSHARED'))
AssertionError: 'gcc -pthread -shared' != '/usr/bin/clang -shared'
- gcc -pthread -shared
+ /usr/bin/clang -shared While clang is installed, I haven't set anything to clang while configuring, or in my environment. |
This test failure points at a few issues:
I recommend the following steps:
|
Sounds good. |
Moving stuff common to both sysconfig modules into a shared module sounds good, but the existence and API of distutils.sysconfig needs to be preserved. |
Moving to blocker for beta2. |
Georg, are you still able to reproduce this? I've subsequently tried on a Debian platform with an installed clang and could not reproduce. And, after further inspecting the current code, I really don't see how the clang substitution could happen on a non-darwin platform. My initial speculation about test_unixcompiler was incorrect as well as the proposed patch to preserve config vars in it (that test does not actually affect _config_vars and _config_vars is a dict so has to be deep-copied to be restorable). I'm proceeding with the _osx_support consolidation but I sure would like to know what was behind the behavior you reported. |
I suspect the problem is related to http://bugs.python.org/issue15298. Basically the global sysconfig module caches the results of parsing Makefile in Lib/_sysconfigdata.py. This can cause you to get the config vars from an old configure and build. |
I don't see how this is related to bpo-15298. In the failure here, sysconfig returns the expected value; the problem is with what distutils.sysconfig returns. |
New changeset d76b83803e7e by Ned Deily in branch 'default': |
I've committed an updated version of the refactoring patch which attempts to handle some additional edge cases and which includes a number of additional tests. I still have not been able to reproduce the original failure so I'm setting the status to pending awaiting a test report from Georg or someone else who is able to reproduce it. |
Buildbot test failure: |
Damn, I don't have clang on this machine. Will install and test. |
These failures are not new, and the buildbot is an unstable one. As for clang, the Lion buildbot uses it and is green. Its configure line is "./configure --with-pydebug CC=clang": |
The problem isn't with clang. The problem was that the test appeared to be taking an OS X only code path apparently because a clang was installed on a Gentoo machine. |
OK, test passes here now with clang installed. |
FYI, Added two FreeBSD based buildslaves to the cluster not long ago, one is dedicated to python+CLANG http://buildbot.python.org/all/buildslaves/koobs-freebsd-clang |
The new buildbot failure is due to that buildbot using env variables for some of the config variables during execution. The new tests need to isolate themselves from that. Should have a fix shortly. |
New changeset 295b715b6875 by Ned Deily in branch 'default': |
I believe I've fixed the buildbot failure but the buildbot is not very stable and test runs aren't always completing. I'll check back on it later. |
New changeset 31349bc40214 by Ned Deily in branch 'default': |
New changeset c286d50ecd19 by Ned Deily in branch 'default': |
The buildbot failures were reproducible on OS X 10.6 with Xcode 3. With the latest two fixes and with the fixes for bpo-15188, I believe this issue is resolved for 3.3. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: