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
fix changed code #5579
fix changed code #5579
Conversation
Thanks. I wonder why we didn't see it in PyPy in the CI? I'd thought we didn't allow failures on PyPy... |
Dunno. I think this is the one. It seems to pass here, but failed on my weekly PyPy + Cython build |
The only thing you're obviously doing differently is Do you think we should be setting |
It seems that is redefined to cython/Cython/Utility/ModuleSetupCode.c Lines 126 to 127 in f082052
|
The PyPy CI run is skipping the "Setup python" step since the condition is wrong cython/.github/workflows/ci.yml Line 223 in f082052
|
While we are at it, I am not sure what the cache step in CI is for. Is something else skipped if the cache is found? It is emitting warnings. A newer workflow is https://github.com/actions/cache/tree/main, but I am not sure how the caching is meant to work and how to check that a cache is being used. |
|
That's likely it. So possibly we're not actually setting up PyPy and just running everything in CPython... I'll investigate and fix if needed (but likely tomorrow). Thanks for spotting that! |
I submitted #5582 |
PR #5556 changed the code to use
__Pyx_PySequence_ITEM
, but changed a bit too much on this line. This was causing PyPy to fail thefused_def
test, after the fix the test passes.This is the change in the context of the PR