[
https://issues.apache.org/jira/browse/CAMEL-24777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18116241#comment-18116241
]
Guillaume Nodet commented on CAMEL-24777:
-----------------------------------------
This issue is being investigated by a coding agent (on behalf of gnodet).
Preliminary analysis: The {{incremental-build.sh}} script uses {{set -euo
pipefail}} at line 31. For very long GitHub Actions jobs, the runner truncates
stdout ("This step has been truncated due to its large size"), causing any
command writing to stdout (such as {{sort}}) to receive SIGPIPE. GNU {{sort}}
catches SIGPIPE, prints {{sort: write failed: stdout: Broken pipe}} and exits
with code 2. Under {{set -e}}, this terminates the entire script even though
the Maven build completed successfully.
Proposed fix: add {{trap PIPE}} near the top of {{incremental-build.sh}} to
ignore SIGPIPE and prevent spurious failures.
_Note: This comment was generated by an AI coding agent and requires manual
verification._
> GitHub action failure for very long jobs: 'Broken pipe'
> -------------------------------------------------------
>
> Key: CAMEL-24777
> URL: https://issues.apache.org/jira/browse/CAMEL-24777
> Project: Camel
> Issue Type: Task
> Components: build system
> Affects Versions: 4.23.0
> Reporter: Aurélien Pupier
> Assignee: Guillaume Nodet
> Priority: Major
>
> {noformat}
> sort: write failed: 'standard output': Broken pipe
> sort: write error
> {noformat}
> despite the build went fine based on stored logs
> see for instance
> https://github.com/apache/camel/actions/runs/34954223946/job/104752329188?pr=26460#step:15:726
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
