From 7cd96a8d9587c056bc26348cc4ee8e58765a3f34 Mon Sep 17 00:00:00 2001 From: Francis Deslauriers Date: Wed, 21 Mar 2018 10:57:04 -0400 Subject: [PATCH] jjb: lava: Run fuzzing job daily regardless of code changes Since the kprobe fuzzing has in important random aspect, we can run it daily to increase the instrumentation coverage. Signed-off-by: Francis Deslauriers --- scripts/system-tests/system-trigger.groovy | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/scripts/system-tests/system-trigger.groovy b/scripts/system-tests/system-trigger.groovy index db5b1b5..151e9d5 100644 --- a/scripts/system-tests/system-trigger.groovy +++ b/scripts/system-tests/system-trigger.groovy @@ -396,9 +396,12 @@ def ongoingJobs = 0; currentJobs.each { jobName, jobInfo -> // If the job ran in the past, we check if the IDs changed since. - if (pastJobs.containsKey(jobName) && !jobName.contains('_canary')) { + // Fetch past results only if the job is not of type canary or fuzzing. + if (!jobName.contains('_canary') && !jobName.contains('_fuzzing') && + pastJobs.containsKey(jobName)) { pastJob = pastJobs[jobName]; - // Have the IDs changed? + + // If the code has not changed report previous status. if (pastJob['config'] == jobInfo['config']) { // if the config has not changed, we keep it. // if it's failed, we don't launch a new job and keep it failed. -- 2.34.1