-
-
Notifications
You must be signed in to change notification settings - Fork 174
Python-3.13-iOS-support.b4 crash in -[iOSTestbedTests testPython] #259
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
I also tested https://github.com/beeware/Python-Apple-support/releases/tag/3.13-b5 have the exact same crash. |
Thanks for the report. The good news is that this isn't a crash - it's Xcode handling a completely expected signal (SIGINT) that the CPython test suite raises as part of testing that the interpreter is working as expected. CPython code involves using (and catching) signals, and so the test suite needs to raise SIGINT (and some other signals) as part of a normal testing run. Unfortunately, the default behavior of Xcode is to insert a breakpoint whenever SIGINT (and a couple of other signals) are raised. When you hit one (as you have in the provided screenshots), the debugger should have the PLAY/PAUSE button enabled; you should be able to hit "PLAY" when you hit this signal, and the test suite will keep running... until it hits the next signal (the test suite raises a lot of them). This is a behavior that can be disabled... manually. Unfortunately, there's no way (that I'm aware of) for us to ship a configuration that disables these breakpoints by default. The process for manually disabling these signals can be found in the iOS README for the CPython repo. You can also avoid the breakpoints by running the test suite from the command line ( |
Thanks for the explanation @freakboy3742. After this change, I was able to run tests. Looks like most of tests are passed.
Attached full Xcode log: pythonframetest.log |
Those failures are both expected. The The |
Describe the bug
Hello,
This is great project, thanks for making it.
OS: Mac OS 14.7.1 (23H222)
Xcode: 16.2
Python framework: 3.13-b4
Steps to reproduce
Expected behavior
Unit tests pass in iOSTestbedTests.
Screenshots
No response
Environment
Logs
Xcode Console logs:
Additional context
No response
The text was updated successfully, but these errors were encountered: