From 22a5adc992ff324ca3cba81b4fdde5b87762362a Mon Sep 17 00:00:00 2001 From: Jonathan Rajotte Date: Wed, 1 May 2019 16:46:01 -0400 Subject: [PATCH 1/1] Deactivate fuzzing on kvm_test for now Fuzzing jobs are nice but require bandwith. They should be moved to their on subset of jobs (kvm_test_fuzzing). Signed-off-by: Jonathan Rajotte --- scripts/system-tests/system-trigger.groovy | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/scripts/system-tests/system-trigger.groovy b/scripts/system-tests/system-trigger.groovy index 9736b02..3c66edf 100644 --- a/scripts/system-tests/system-trigger.groovy +++ b/scripts/system-tests/system-trigger.groovy @@ -367,10 +367,10 @@ configurationOfInterest.each { lttngBr, linuxBr -> currentJobs[jobName] = CraftConfig(linuxBr, lttngBr); // Add fuzzing job in vm_tests on master branches of lttng and linux. - if (jobType == 'vm_tests' && lttngBr == 'master' && linuxBr == 'master') { - def vmFuzzingJobName = CraftJobName(jobType + '_fuzzing', linuxBr, lttngBr); - currentJobs[vmFuzzingJobName] = CraftConfig(linuxBr, lttngBr); - } + //if (jobType == 'vm_tests' && lttngBr == 'master' && linuxBr == 'master') { + // def vmFuzzingJobName = CraftJobName(jobType + '_fuzzing', linuxBr, lttngBr); + // currentJobs[vmFuzzingJobName] = CraftConfig(linuxBr, lttngBr); + //} } //Add canary job -- 2.34.1