clusterfuzz icon indicating copy to clipboard operation
clusterfuzz copied to clipboard

Chore/revert uworker safe

Open vitorguidi opened this issue 1 year ago • 3 comments

We apparently had a drop in succesful batch runs from #4000 and subsequent PRs, so reverting for good measure

vitorguidi avatar Jul 03 '24 13:07 vitorguidi

I don't think we should revert this yet.

  1. The brekage is not user-visible yet as it only affects fuzz_task.
  2. I am addressing the errors now and should have fixes for all of them in the next 30 minutes.
  3. The errors don't appear easy to reproduce locally so having them occur in prod is valuable teaching moments.

jonathanmetzman avatar Jul 03 '24 13:07 jonathanmetzman

I also somewhat doubt the batch metric is correctly reading this. Most batch jobs are probably not the result of fuzzing from that day.

jonathanmetzman avatar Jul 03 '24 13:07 jonathanmetzman

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?

vitorguidi avatar Jul 03 '24 13:07 vitorguidi