Skip to content

Fix compiler diagnostic severity and continuation context - #561

Open
natew wants to merge 1 commit into
getsentry:mainfrom
natew:fix/compiler-diagnostic-severity-context
Open

natew wants to merge 1 commit into
getsentry:mainfrom
natew:fix/compiler-diagnostic-severity-context

Conversation

@natew

@natew natew commented Oct 25, 2026

Copy link
Copy Markdown

Compiler warnings can include error: in their message or printed source, causing them to appear as compiler errors. For example:

/tmp/Bridge.cpp:4:2: warning: variable may be uninitialized [-Wconditional-uninitialized]
    4 | log("execution error: message");
      | ^

Parse diagnostic headers using their explicit severity, and retain source, caret, and note continuations for both warnings and errors. Use the same classification for final diagnostic raw output. Preserve compiler, fatal, tool, and timestamped errors, including multiline raw output. Build status continues to follow the execution outcome.

Validation: 69 focused parser, domain result, and run-state tests; npm run build, npm run typecheck, and npm run lint. Saved-log replay and warning/error/chunking controls also checked. No native builds, snapshot tests, or smoke tests.

@natew
natew marked this pull request as ready for review October 25, 2026 10:08

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant