Repository navigation
testing: parallel fuzzing hangs with -parallel=1 #50217
Description
Activity
- addedfuzzIssues related to native fuzzing supportIssues related to native fuzzing support
on Dec 16, 2021 Bisected down to b2b6be7
cc @golang/fuzzing
- addedNeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
on Dec 16, 2021 This seems like one of the things that should just be disabled, both within the
f.Fuzzfunction, and disallowing the flag, since I'm not really sure what it would do. @katiehockman what do you think?FWIW, in terms of what it could do, the design doc includes:
// Run the fuzz test f.Fuzz(func(t *testing.T, a string, num *big.Int) { t.Parallel() // seed corpus tests can run in parallelCertainly seems reasonable to disallow it though, especially for a first version.
Running seed corpus entries in parallel actually works (as far as I can tell) and is very useful for me. If there is not enough time to fix it for
-parallel=1edge case, maybe just explicitly fail in that case instead of hanging or removing the whole feature.t.Parallel()in a fuzz target should be a no-op during fuzzing, but is similar to at.Parallel()inside at.Run()in that it runs the seed corpus in parallel when-fuzzisn't set.
This is just a bug I think. If we can't fix it, then just removing that functionality for 1.18 also seems fine. Will take a look.- addedNeedsFixThe path to resolution is known, but the work has not been done.The path to resolution is known, but the work has not been done.and removedNeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
on Dec 20, 2021 Change https://golang.org/cl/374054 mentions this issue:
testing: fix deadlock with t.Parallel in testing seed corpus- added a commit that references this issue
on Jun 21, 2022 - locked and limited conversation to collaborators
on Jun 22, 2023 - added a commit that references this issue
on Sep 19, 2024
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsNo status
The following test hangs when run with
go test -parallel=1:It works with
-parallel=2and other values. I think it should work in any case.Small self-contained example is there: https://github.com/AlekSi/go-bug/tree/master/50217