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. I've overridden this for the Crave build with an unsatisfying hack.
On Mon, Jul 8, 2024 at 1:58 PM Jason Gerlowski <gerlowsk...@gmail.com> wrote: > > 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 blocks other jobs from running, and > seemingly even our longest-running jobs should complete in a few > hours. Would anyone object to my lowering some of these long build > timeouts to, say, 3 hours? > > The following jobs would be affected: > > - Solr-BadApples-Tests-main > - Solr-check-9.6 > - Solr-Check-9.x > - Solr-Check-main > - Solr-Check-main-s390x > - Solr-Docker-Nightly-9.6 > - Solr-Docker-Nightly-9.x > - Solr-Docker-Nightly-main > - Solr-Docker-Official-Test-main > - Solr-Docker-Test-main > - Solr-NightlyTests-main > - Solr-Smoketest-9.6 > - Solr-Smoketest-9.x > > Best, > > Jason > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org > For additional commands, e-mail: dev-h...@solr.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org For additional commands, e-mail: dev-h...@solr.apache.org
