Improve crash message: distinguish exit vs signal#98
Merged
nicoddemus merged 3 commits intopytest-dev:masterfrom Mar 2, 2026
Merged
Improve crash message: distinguish exit vs signal#98nicoddemus merged 3 commits intopytest-dev:masterfrom
nicoddemus merged 3 commits intopytest-dev:masterfrom
Conversation
When a forked test process exits with a non-zero exit code (signal == 0), the message previously said "CRASHED with signal 0" which is misleading — signal 0 is not a real signal and the process was not killed by one. Now: - Non-signal exit: "EXITED with status <N>" - Signal kill: "CRASHED with signal <N> (<NAME>)" e.g. "signal 11 (SIGSEGV)" signal.Signals() is called without a try/except because result.signal comes from os.WTERMSIG(), which extracts the signal from the kernel's wait status — the kernel can only kill a process with a valid signal number. Note: sys.exit() is caught by pytest as SystemExit and does not trigger report_process_crash; os._exit() bypasses the marshal pipe and does.
nicoddemus
approved these changes
Feb 20, 2026
Member
nicoddemus
left a comment
nicoddemus
left a comment
There was a problem hiding this comment.
LGTM!
Could you please also add a changelog entry? Thanks!
Contributor
Author
Thanks for the reivew! I added an item to the changelog. |
Member
|
Hmm the tests are failing, could you take a look? Thanks |
The reason_string pattern lacked a trailing wildcard, so it failed to match after the crash message started including the signal name (e.g. "signal 15 (SIGTERM)"). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Contributor
Author
|
Tests fixed 👍 (They run successfully locally in on MacOS on Python 3.13) |
nicoddemus
approved these changes
Feb 23, 2026
Member
nicoddemus
left a comment
nicoddemus
left a comment
There was a problem hiding this comment.
Thanks!
I will leave it open for a few days to give @RonnyPfannschmidt a chance to review, otherwise I will merge/squash it then.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When a forked test process exits with a non-zero exit code (signal == 0), the message previously said "CRASHED with signal 0" which is misleading — signal 0 is not a real signal and the process was not killed by one.
Now:
signal.Signals() is called without a try/except because result.signal comes from os.WTERMSIG(), which extracts the signal from the kernel's wait status — the kernel can only kill a process with a valid signal number.
Note: sys.exit() is caught by pytest as SystemExit and does not trigger report_process_crash; os._exit() bypasses the marshal pipe and does.