clusterfuzz
clusterfuzz copied to clipboard
Chore/revert uworker safe
We apparently had a drop in succesful batch runs from #4000 and subsequent PRs, so reverting for good measure
I don't think we should revert this yet.
- The brekage is not user-visible yet as it only affects fuzz_task.
- I am addressing the errors now and should have fixes for all of them in the next 30 minutes.
- The errors don't appear easy to reproduce locally so having them occur in prod is valuable teaching moments.
I also somewhat doubt the batch metric is correctly reading this. Most batch jobs are probably not the result of fuzzing from that day.
I also somewhat doubt the batch metric is correctly reading this. Most batch jobs are probably not the result of fuzzing from that day.
What would be desirable for us to debug this kind of issue in the future? Success rate, given a fuzzing task start time?