fix: report partial script compilation failures on stderr - #300
Merged
Conversation
swananan
marked this pull request as ready for review
September 6, 2026 04:59
swananan
force-pushed
the
fix/bitfield-integer-promotion
branch
from
September 6, 2026 09:32
957f16e to
543e64d
Compare
swananan
force-pushed
the
fix/report-partial-script-failures
branch
from
September 6, 2026 11:30
7b5d007 to
f418dcf
Compare
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
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 script containing both valid and invalid trace targets could keep tracing the valid targets while hiding the failed targets when logging and status output were disabled.
Report partial compilation failures on stderr independently of those settings. Keep the successful probe configurations and existing attachment and exit-code behavior. Complete failures continue through the existing error path.
Rebased onto main at
f28b207; one commit, two files.git range-diffconfirms the original patch is unchanged.Validation on
f418dcf:--no-log --no-statusregression.