add fuzzer build to the PreCQ/CQ |
||||
Issue descriptionwith the uptick in fuzzing adoption, we're starting to see some breakage that is fuzzing-specific. which means people have to monitor the config and then find/fix the broken logic after the fact. we should add this to the precq/cq instead. this would be a single build, and it should be faster than most other configs as it doesn't run tests. it's build-only. Manoj: can you link to the existing builder so we get a sense of timing ?
,
Nov 30
Mike, this is a really quick config change. We don't have builder capacity for PreCQ just now so only do this for CQ.
,
Jan 7
I'm CI primary this week so I'm going to go ahead and proceed with introducing these new builds to the CQ. -- Mike
,
Jan 7
,
Jan 7
Fuzzer builds just got broken again by CL:1391610 so given them CQ protection would be great.
,
Jan 10
I'm still poking at this. Add fuzzer builds to the CQ is not a simply config change; these use a completely different type of build class which means this is not a simple plug-and-play configuration change. I have a change in-flight but am still resolving some issues and validating. -- Mike |
||||
►
Sign in to add a comment |
||||
Comment 1 by manojgupta@chromium.org
, Nov 30