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
pypy test has started failing #463
Comments
Between that build and the prior run, the PyPy version changed from 7.3.11 (Python 3.9.16) to 7.3.12 (Python 3.9.17). |
Testing locally, I have pypy 7.3.10-alpha, and tests pass. Looks like maybe the reason I have an old pypy is because I built/installed it from source to support macOS ARM. It does appear that 7.3.12 is available on homebrew now. |
After realizing that |
I am, however, able to replicate the issue using pypy 3.9.
|
Well, I did replicate it once, but the failure went away.
WTH? Note that while I did rebuild the environment above, it wasn't the rebuilding the environment that allowed the tests to start passing. After the original error occurred, I set out to use pdb to triage, and even then, the replicated failure did not occur:
|
I've repeated that command using |
In an attempt to understand better the differences between a fresh failing run and a passing run, I ran the following:
Here's the output from that last command:
|
Curiously (and maybe unrelated), there seems to be a glitch in path handling that's causing the duplicate path to be created in That fact may be implicated in the failure, which I can now repeat without reinstalling pypy, but instead removing _testmultiphase prior to running the tests:
Based on timing and other common factors, I suspect the issue is related to pypy/pypy#3953. |
I do see both |
When you say Python 3.9.16, do you mean CPython or PyPy? If the former, that's interesting and surprising as this issue was previously isolated to PyPy... and tests have been passing reliably on CPython across popular platforms throughout. Do you have a way to replicate it? I have re-enabled the PyPy tests in CI, since upstream skeleton has bumped from 3.9 to 3.10, bypassing the underlying issue. Moreover, now that I have pypy 7.3.13 (3.9.18), I'm no longer able to replicate the issue locally, even after deleting
|
When I say Python 3.9.16 I mean CPython. And yes, it looks like it is reproducible reliably. When I played with
I do not have CPython > 3.9.16 handy so I cannot confirm. |
Although the issue may be similar, I think it's better to track the new failure in a separate issue Thanks for filing #479. |
Around two weeks ago, in this build, tests started failing on PyPy, implicating f5a5617. Is it the case that
pypy3.9
needs-dev
?The text was updated successfully, but these errors were encountered: