From a4f0ae5e41b92db1cfcc4172269dbd585410218d Mon Sep 17 00:00:00 2001 From: Aleksandr Nogikh Date: Tue, 9 May 2023 14:43:47 +0200 Subject: syz-ci: increase bisection job timeout Earlier it was limited to 8 hours mostly because syz-ci could execute only one job at a time. Now that it's no longer the case, we can increase the timeout to 12 hours. --- syz-ci/jobs.go | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) (limited to 'syz-ci') diff --git a/syz-ci/jobs.go b/syz-ci/jobs.go index 38a2546c6..b717ade4f 100644 --- a/syz-ci/jobs.go +++ b/syz-ci/jobs.go @@ -484,11 +484,9 @@ func (jp *JobProcessor) bisect(job *Job, mgrcfg *mgrconfig.Config) error { // - 4026 finished under 10h (98.8%) // - 4032 finished under 12h (98.9%) // Significant increase in errors starts after ~12h. - // The current timeout also take into account that bisection jobs - // compete with patch testing jobs (it's bad delaying patch testing). - // When/if bisection jobs don't compete with patch testing, - // it makes sense to increase this to 12-24h. - Timeout: 8 * time.Hour, + // Bisection jobs are now executed in parallel to patch testing, so it doesn't destroy user experience. + // Let's set the timeout to 12h. + Timeout: 12 * time.Hour, Fix: req.Type == dashapi.JobBisectFix, DefaultCompiler: mgr.mgrcfg.Compiler, CompilerType: mgr.mgrcfg.CompilerType, -- cgit mrf-deployment