-
-
Notifications
You must be signed in to change notification settings - Fork 448
PyPy 3.9 nightlies are failing some tests #1426
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
nedbat
added a commit
that referenced
this issue
Jul 30, 2022
nedbat
added a commit
that referenced
this issue
Jul 30, 2022
nedbat
added a commit
that referenced
this issue
Jul 30, 2022
nedbat
added a commit
that referenced
this issue
Jul 30, 2022
nedbat
added a commit
that referenced
this issue
Jul 30, 2022
nedbat
added a commit
that referenced
this issue
Jul 30, 2022
nedbat
added a commit
that referenced
this issue
Jul 30, 2022
nedbat
added a commit
that referenced
this issue
Aug 2, 2022
nedbat
added a commit
that referenced
this issue
Aug 2, 2022
nedbat
added a commit
that referenced
this issue
Aug 2, 2022
I've xfail'ed two tests so the nightly tests can succeed. https://foss.heptapod.net/pypy/pypy/-/issues/3792 is the PyPy issue. |
This was fixed a while back, and the tests un-xfailed in 37ac634 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
https://github.com/nedbat/coveragepy/runs/7574680068?check_suite_focus=true
Output from the failing test
PyPy3.9 started reporting sys.argv[0] as an absolute file rather than relative. But it still shows relative files in tracebacks.
The text was updated successfully, but these errors were encountered: