Thanks for the tip Uwe!
Not hearing any objections, so I'll give the dynamic-timeout a try on our
jobs. Can always revert on the off chance that objections trickle in late
here...
Best,
Jason
On Tue, Jul 9, 2024 at 7:55 AM Uwe Schindler wrote:
> Hi,
>
> on Policeman Jenkins I use the dynamic
> What is the current timeout? You propose setting it to 3 hours?
For all the jobs I listed above, the timeout on the Jenkins job itself
is currently 24 hours (!), and I'm proposing lowering that to 3 hours
on each of those listed jobs.
Maybe we should have timeouts on specific test cases or tes
What is the current timeout? You propose setting it to 3 hours? Are
you referring to a Jenkins job specific thing or a Java based test
suite timeout? I've looked into the latter, which is set to 2 hours
in LuceneTestCase (see @TimeoutSuite) -- pretty crazy and IMO should
not be set there at all.
Hey all,
I spent some time last week looking into a few ASF Jenkins jobs that
hung indefinitely until the timeout killed them nearly a day later.
The specific cause has since been fixed, but it raised the question:
why is the timeout for our builds so long?
Allowing "stuck" builds to linger block
