-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
3.13b3 crashes in Cython test suite #121253
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
|
Are you using a debug build of Python? How can I only re-run tests which are triggering the crashes (not run the full test suite)? |
It's using the regular CPython package that the setup-python action installs. But I was using a debug build locally (when I failed to reproduce the crash), so yes, that might make a difference.
To run the test suite, see
https://github.com/cython/cython/wiki/HackerGuide#the-test-suite
|
I ran tests on Python 3.13 built in debug mode:
I got an assertion error:
and a Fatal Error:
and another assertion error:
|
The doc says "To select a specific test (or a set of tests), just pass the name(s) as parameters." If I ran |
I also failed to reproduce it on my own laptop so I'm not sure I can really help. I don't really know what's failing and what I'm trying to reproduce.
This should be the right way to run it. I'd add Sorry not to be more useful... This bug beat me too. |
I don't reproduce the crash if I only run methodmangling_T5. |
I made some progress: on Windows (using the official installer) it crashes semi-reliably (most but not all of the time) the first time it runs (that's running just If I clear all the .pyc files from the cython directory then it crashes again. I wasn't able to find much useful from trying to debug it, but it does seem like it needs to generate pyc files at least on Windows. (Don't know right now if this applies to other platforms - I suspect it does but haven't tried) |
If I run
|
I reproduced the methodmangling_T5 bug on Linux: I created #121863 for this bug. |
This bug is tracked as #121860 which has no reproducer yet. |
At some point I'll try get the Cython test suite running against a debug build of Python as part of our regular CI runs (we already do some runs with It's needs these versions to be available on GitHub actions easily. |
Python CI clones the Git repository and builds Python from scratch, it takes 60 seconds in total. You can clone a specific Git tag. |
@da-woods: What's the status of this issue with Python 3.13 rc1? |
Py3.13rc1 runs fine on our side. Thanks! |
Crash report
What happened?
With the release of CPython 3.13b3, Cython's test suite started crashing on Linux/macOS/Windows in Github Actions. The position given by the CPython crash stack trace looks random, but it seems to be related to running the @no_gc test. However, I failed to reproduce the crash locally when running only that test.
Some of the crash logs (look for "Fatal Python error"):
https://github.com/cython/cython/actions/runs/9746719041/job/26897743924
https://github.com/cython/cython/actions/runs/9746719041/job/26897748128
Note that the test runs are sharded, so there's some noise in the output from other test processes. The crash predictably happens in shard
[2]
.[Side note: Py3.13 is missing from the issue form in
crash.yml
.]CPython versions tested on:
CPython main branch
Operating systems tested on:
No response
Output from running 'python -VV' on the command line:
No response
The text was updated successfully, but these errors were encountered: