Closed Bug 831500 Opened 7 years ago Closed 4 years ago

run fuzzer on ASAN builds during idle times

Categories

(Release Engineering :: General, defect)

x86
macOS
defect
Not set

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: joduinn, Assigned: decoder)

References

(Blocks 1 open bug)

Details

(Keywords: sec-want)

Spinning out from bug#753148.

Per :decoder, he'd like to run fuzzers on these ASAN builds as part of the usual set of idle-time fuzzer jobs. Spinning out this bug to figure out what is wanted, and then do it.
Probably a misunderstanding here, it's not me who would run these, but Jesse (it's only about running domfuzz right now, afaik). I'm not sure what his plans are but as far as I remember, he wanted to run idle-time fuzzer jobs with ASan builds on RelEng once the builds are there :)

Ccing Jesse to find out what's necessary to do here :)
Both domfuzz and jsfunfuzz are being run now. The driver script, bot.py, chooses randomly between the two. They are currently being run on regular non-ASAN builds.

For reference, the script for the current usual set of idle-time fuzzer jobs is located here:

https://hg.mozilla.org/build/tools/file/default/scripts/fuzzing/fuzzer.sh
Product: mozilla.org → Release Engineering
Note the dependency for this landed.
Is there anything for RelEng to do here? Or can you guys adjust bot.py to use ASAN builds as well?
(In reply to Chris AtLee [:catlee] from comment #4)
> Is there anything for RelEng to do here? Or can you guys adjust bot.py to
> use ASAN builds as well?

I bet Gary knows :)
Flags: needinfo?(gary)
Jesse is probably a better option - he works more with Firefox binaries these days, and I *think* the ASAN ones as well.
Flags: needinfo?(gary) → needinfo?(jruderman)
For Linux I need a fix for bug 855881 (or bug 628573?).

For Mac I need fixes for bug 923916, bug 937582, and bug 935795.
Flags: needinfo?(jruderman)
Depends on: 937830
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.