Share compiler crash detection across Python conformance checks - #542
Open
charliermarsh wants to merge 2 commits into
Open
Share compiler crash detection across Python conformance checks#542charliermarsh wants to merge 2 commits into
charliermarsh wants to merge 2 commits into
Conversation
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
1 participant
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.
A compiler driver could report a crashed child with exit code 1 and satisfy the generated-binding gate's expected rejection. We share crash-diagnostic detection across the Python conformance checks, inspect both output streams, and reject unexpected exit statuses before treating a result as a source diagnostic. Conformance source identities include the shared classifier and detect changes during an audit.
Regression coverage replays the captured Clang frontend failure through the actual gate, rejects mid-run classifier changes, and checks standalone imports with Python safe-path mode. Python harness tests, three incorrect-frontend fault cases, a native Csmith control, and independent generated C/Rust audits pass.