MozillaSecurity / MozillaSecurity/FuzzManager
libFuzzer merge cycle should be more robust against interruptions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 208
- Forks
- 48
- Avg merge
- 23h 5m
- Merged PRs (30d)
- 2
Description
Currently, a libFuzzer merge cycle with S3 performs the following steps:
- Delete closed queues
- Download remaining queues (thereby closing them)
- Local merge
- Corpus reupload
If the task gets interrupted in step 3 or 4, the next run will delete the queues closed previously, even though they haven't been merged yet. To make this more robust, we should probably close the queues only after completing step 4 successfully.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace the libFuzzer merge cycle's S3 queue lifecycle, focusing on deletion, downloading, local merging, and corpus reupload. Reproduce or reason through an interruption during local merge or reupload, then verify that an interrupted run does not discard queues before a successful reupload.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- testing-qa, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100