-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
test_trace fails with -S #63597
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
Comments
$ ./python -S -m test test_trace
[1/1] test_trace
test test_trace failed -- Traceback (most recent call last):
File "/home/antoine/cpython/default/Lib/test/test_trace.py", line 313, in test_coverage
self.assertTrue("pprint.cover" in files)
AssertionError: False is not true |
This is the "emergency" patch to solve this issue. The main issue is, [sky@localhost cpython]$ ./python -Sc "import sys; print(sys.path)" Let me "zoom" it for you. [sky@localhost cpython]$ ./python -Sc "import sys; print(sys.path[2])" The "extra" slash is the culprit. I need to investigate whether this is deliberate or not. |
I finally found the main culprit which puts extra '/' in my sys.path. The patch removed the extra '/' and also fixed this test automatically. |
The test should use the more specific assertXyz method: The error message would then be the more informative |
Attached the patch to accommodate Terry J. Reedy's request. |
The separator is needed if the relative path is not empty and the prefix doesn't end with the separator. This patch seems also fixes most problems of bpo-28655. |
New changeset db220f2df5a9 by Serhiy Storchaka in branch '3.5': New changeset 1a88baaed7a0 by Serhiy Storchaka in branch '3.6': New changeset 82607e7c24c7 by Serhiy Storchaka in branch 'default': New changeset 237ef36fb1bb by Serhiy Storchaka in branch '2.7': |
Misc/NEWS
so that it is managed by towncrier #552Note: 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: