From 3478a0d8a0faf1fb640fd3873b558d6d93d4623c Mon Sep 17 00:00:00 2001 From: hamzeh Date: Mon, 16 Dec 2019 16:25:50 -0800 Subject: [PATCH] Adding capability to granular disable of fuzzer This change is to add granularity for disabling of the fuzzer from running on host, device or both. Bug: 145824604 Test: make haiku successfully completes after change Change-Id: I686b439e36c622108f7b5b3e3f4738b8295320a7 --- cc/fuzz.go | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/cc/fuzz.go b/cc/fuzz.go index 0d3cc7430..8b84be8df 100644 --- a/cc/fuzz.go +++ b/cc/fuzz.go @@ -27,9 +27,10 @@ import ( type FuzzConfig struct { // Email address of people to CC on bugs or contact about this fuzz target. Cc []string `json:"cc,omitempty"` - // Boolean specifying whether to disable the fuzz target from running - // automatically in continuous fuzzing infrastructure. - Disable *bool `json:"disable,omitempty"` + // Specify whether to enable continuous fuzzing on devices. Defaults to true. + Fuzz_on_haiku_device *bool `json:"fuzz_on_haiku_device,omitempty"` + // Specify whether to enable continuous fuzzing on host. Defaults to true. + Fuzz_on_haiku_host *bool `json:"fuzz_on_haiku_host,omitempty"` // Component in Google's bug tracking system that bugs should be filed to. Componentid *int64 `json:"componentid,omitempty"` // Hotlists in Google's bug tracking system that bugs should be marked with.