Fix release smoke-test SIGPIPE - #3
Merged
Merged
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.
Outcome
Prevents the standalone release smoke test from reporting exit 141 after it successfully discovers the bundled bridge.
With
set -o pipefail, the previousawk ... { print; exit }could close the pipe whilepswas still writing. macOS then reported the upstreampsSIGPIPE as a build failure. The updated expression records and prints only the first matching child while continuing to consume the process list.Verification
bash -n native/Brain3D/Scripts/build-release-app.sh: pass.pipefail: exit 0.git diff --check: pass.The failed build's app and zip remain preserved locally and will not be published. A fresh clean-main standalone build will run after this PR passes CI and merges.