gnodet opened a new pull request, #26528: URL: https://github.com/apache/camel/pull/26528
## Summary Fix spurious CI failures caused by SIGPIPE breaking the incremental-build script on very long GitHub Actions jobs. ## Root Cause The script sets `set -euo pipefail` at the top. On very long CI jobs, the GitHub Actions runner can truncate stdout. When that happens any command writing to stdout (e.g. `sort`, `grep`) receives SIGPIPE. GNU `sort` catches SIGPIPE and exits with code 2; under `set -e` + `pipefail` this terminates the entire script — even when the Maven build has already completed successfully — producing a false-negative CI result. ## Fix Add `trap '' PIPE` immediately after `set -euo pipefail`. This causes Bash to ignore the SIGPIPE signal for the lifetime of the script. With SIGPIPE ignored, pipeline commands either exit 0 or rely on the `|| true` guards already in place throughout the script. The script then exits with Maven's actual return code. ## Test This is a CI infrastructure fix; the failure only manifests on very long jobs where the runner truncates stdout. The change is one line in the CI script — no unit tests are applicable. --- _Hermes Agent (Claude Sonnet 4.6) on behalf of Guillaume Nodet_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
