Increase CI build timeout from 7 hours to 600 minutes (10h)

[Croway]

Summary

Claude Code on behalf of Federico Mariani

• Increase the per-cell matrix build timeout from 7 hours to 600 minutes (10h)
• camel-4.14.x has had 3 consecutive ABORTs (builds [CAMEL-7462] Do not treat <HTTP/1.1 100 Continue> as final response #160-162) due to this limit
• Build CAMEL-7447 Allow to stream the result of a database query #159 shows a cell legitimately needs ~9.8h (estimated duration) to complete
• Companion PR to Increase CI build timeout from 450 to 600 minutes #22378 (main branch)

Test plan

• CI Camel Core (Build and test) / camel-4.14.x should no longer ABORT due to timeout
• Monitor next few builds to confirm completion within 600 minutes

🤖 Generated with Claude Code

[apupier]

Could you provide the output when the abort occurred? From my experience, when the 7 hours is reached it is that the build is completely stuck and increasing to 10 hours won't change anything if it is the same case

recently, it was regularly the JMS tests which are blocked: https://issues.apache.org/jira/browse/CAMEL-23194

[Croway]

@apupier in the latest builds I could find any stuck test, but, the issue was with PPC/S390 hosts that waited too much in the queue

[apupier]

with the latest build on 4.14.x https://ci-builds.apache.org/job/Camel/job/Camel%20Core%20(Build%20and%20test)/job/camel-4.14.x/162/cloudbees-pipeline-explorer/?filter=43

it is also the JMS tests which are blcoked

 [INFO] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.36 s -- in org.apache.camel.component.jms.async.AsyncJmsProducerTest
	
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.304 s -- in org.apache.camel.component.jms.issues.JmsInOutPipelineWithBeanTest
	
[INFO] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 16.51 s -- in org.apache.camel.component.jms.issues.JmsInOutRoutingSlipTest
	
Cancelling nested steps due to timeout
	
Sending interrupt signal to process

[apupier]

easier to see with the timestamps:

[apupier]

sam eproblem with latest 4.18.x aborted build:

https://ci-builds.apache.org/job/Camel/job/Camel%20Core%20(Build%20and%20test)/job/camel-4.18.x/20/cloudbees-pipeline-explorer/?filter=86

[Croway]

I see, on the 4.18.x and 4.14.x some back ports are missing.

@apupier right now the surefire fork timeout is 20 minutes, do you think we can reduce it to 10? maybe with the reduced timeout, and higher CI build timeout we can gather more information? moreover, this way all the tests will be executed every time, this will provide more information about the build quality

[apupier]

@apupier right now the surefire fork timeout is 20 minutes, do you think we can reduce it to 10? maybe with the reduced timeout, and higher CI build timeout we can gather more information? moreover, this way all the tests will be executed every time, this will provide more information about the build quality

unfortunately no. The surefire timeout is bypassed. The current timeout is the one from the jenkins global job.

[apupier]

I see, on the 4.18.x and 4.14.x some back ports are missing.

not the root cause. it is still happening on the main branch. the previous attempts were infructuous. (see the reopeoned state of https://issues.apache.org/jira/browse/CAMEL-23194 )

[apupier]

as we checked that it is related to blocked tests as reported to https://issues.apache.org/jira/browse/CAMEL-23194 increasing the timeout will make the things worse as it will await even more for no chance to pass.