The inputs in these failures look very similar to me.

(Maybe this has something to do with the Unicode replacement value, if the test input happens not to be valid UTF-8?)

Change https://golang.org/cl/356649 mentions this issue: cmd/go: skip flaky fuzz tests

I don't think this is a UTF-8 issue. What this test is basically checking is that the coordinator can reconstruct the mutated input if it wasn't provided by the worker (e.g. because of a non-recoverable crash). It reconstructs it by using the count of mutations that is stored in shared memory. If that number is 1 off (either too big or too small), it would look a lot like these errors, since all of the incorrect inputs are only slightly different from the expected inputs.

I'm not able to reproduce this locally, unfortunately, which makes debugging this more difficult.

I have a theory. It's a bit of a longshot, but seems plausible?

When fuzzing, if an unrecoverable error occurs, the coordinator uses the count written to memory to reconstruct the input that caused the failure. This count is increased inside fuzzOnce right before we execute fuzzFn (the fuzz function).
The fuzz test in test_fuzz_mutator_repeat writes to a file on the 100th execution of the fuzz target, and exits in a way that is unrecoverable. If an execution of fuzzFn triggers new code coverage, then we attempt to deflake to make sure the coverage is legitimate. This calls fuzzOnce, which would in turn increase count by one before fuzzFn is called.

I see one possible way this number could be off. If the 99th execution of fuzzFn increases coverage, and a crash occurs during the de-flake (i.e. the 100th execution), then the count will accurately describe how many times the fuzz function was called, but will be 1 bigger than the number of times mutate was called.

This would explain why it happens so rarely. The fix for this isn't totally straightforward. We can't for example just not increase the count when we're deflaking, because the count is used for -fuzztime=Xx. But I have a few other ideas that should work.

Change https://golang.org/cl/358094 mentions this issue: internal/fuzz: don't deflake coverage found while fuzzing

Unfortunately this test is still occasionally failing on linux-386-longtest. (Does it depend on instrumentation?)

greplogs --dashboard -md -l -e 'FAIL: TestScript/test_fuzz_mutator_repeat' --since=2021-10-23

2021-11-17T17:36:36-0555ea3/linux-386-longtest
2021-11-17T17:16:18-ab75484/linux-386-longtest

From some further builds, the recent failures are looking like a regression as of CL 364214.

greplogs --dashboard -md -l -e 'FAIL: TestScript/test_fuzz_mutator_repeat' --since=2021-10-23

2021-11-17T19:51:32-9a33945/linux-386-longtest
2021-11-17T19:51:32-9a33945/linux-amd64-longtest
2021-11-17T19:51:32-9a33945/windows-amd64-longtest
2021-11-17T19:50:58-88474d4/linux-386-longtest
2021-11-17T19:50:58-88474d4/linux-amd64-longtest
2021-11-17T19:18:24-aa34ea2/linux-386-longtest
2021-11-17T19:18:24-aa34ea2/linux-amd64-longtest
2021-11-17T18:14:41-0981724/linux-386-longtest
2021-11-17T18:14:41-0981724/windows-amd64-longtest
2021-11-17T18:14:23-9bdbed1/linux-386-longtest
2021-11-17T18:14:23-9bdbed1/linux-amd64-longtest
2021-11-17T18:14:06-17b7604/linux-386-longtest
2021-11-17T18:14:06-17b7604/windows-amd64-longtest
2021-11-17T17:36:36-0555ea3/linux-386-longtest
2021-11-17T17:16:18-ab75484/linux-386-longtest

Change https://golang.org/cl/364758 mentions this issue: cmd/go: skip broken fuzz test

Change https://golang.org/cl/364954 mentions this issue: cmd/go: deflake test_fuzz_mutator_repeat

Change https://golang.org/cl/365175 mentions this issue: internal/fuzz: fix chunk swap mutator

Change https://golang.org/cl/365294 mentions this issue: internal/fuzz: compute correct number of mutations

@rolandshoemaker @katiehockman Is this okay to resolve after beta1? If so, feel free to apply the label for tracking.