-
Notifications
You must be signed in to change notification settings - Fork 18.4k
Closed
Labels
FrozenDueToAgeNeedsInvestigationSomeone 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.fuzzIssues related to native fuzzing supportIssues related to native fuzzing support
Milestone
Description
#!watchflakes
post <- pkg == "cmd/go" && `fuzz: elapsed: \d+m\d+s, execs: \d+ \(0/sec\),` && (date < "2023-10-01" || builder ~ `^go1.20`)
What version of Go are you using (go version
)?
$ go version go version go1.18rc1 linux/amd64
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env
)?
go env
Output
$ go env GO111MODULE="" GOARCH="amd64" GOBIN="" GOCACHE="/home/capnspacehook/.cache/go-build" GOENV="/home/capnspacehook/.config/go/env" GOEXE="" GOEXPERIMENT="" GOFLAGS="" GOHOSTARCH="amd64" GOHOSTOS="linux" GOINSECURE="" GOHOSTOS="linux" GOINSECURE="" GOMODCACHE="/home/capnspacehook/go/pkg/mod" GONOPROXY="" GONOSUMDB="" GOOS="linux" GOPATH="/home/capnspacehook/go" GOPRIVATE="" GOPROXY="https://proxy.golang.org,direct" GOROOT="/home/capnspacehook/sdk/go1.18rc1" GOSUMDB="sum.golang.org" GOTMPDIR="" GOTOOLDIR="/home/capnspacehook/sdk/go1.18rc1/pkg/tool/linux_amd64" GOVCS="" GOVERSION="go1.18rc1" GCCGO="gccgo" GOAMD64="v1" AR="ar" CC="gcc" CXX="g++" CGO_ENABLED="0" GOMOD="/home/capnspacehook/Documents/git/egress-eddie/go.mod" GOWORK="" CGO_CFLAGS="-g -O2" CGO_CPPFLAGS="" CGO_CXXFLAGS="-g -O2" CGO_FFLAGS="-g -O2" CGO_LDFLAGS="-g -O2" PKG_CONFIG="pkg-config" GOGCCFLAGS="-fPIC -m64 -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build1895014098=/tmp/go-build -gno-record-gcc-switches"
What did you do?
- Clone https://github.com/capnspacehook/toml
- Switch to the
invalid_utf8
branch - Clone https://github.com/capnspacehook/egress-eddie
- Switch to the
go_fuzzer_bug
branch - Replace your local fuzz cache with the contents of
fuzzcache
- Add a
replace
directive to thego.mod
file replacinggithub.com/BurntSushi/toml
with where you clonedgithub.com/capnspacehook/toml
- Start fuzzing:
go test -run Parse -fuzz Fuzz
What did you expect to see?
The fuzzer trying many inputs per second
What did you see instead?
fuzz: elapsed: 0s, gathering baseline coverage: 0/253 completed
fuzz: elapsed: 1s, gathering baseline coverage: 253/253 completed, now fuzzing with 12 workers
fuzz: elapsed: 3s, execs: 42532 (14175/sec), new interesting: 14 (total: 267)
fuzz: elapsed: 6s, execs: 78830 (12092/sec), new interesting: 20 (total: 273)
fuzz: elapsed: 9s, execs: 78830 (0/sec), new interesting: 20 (total: 273)
fuzz: elapsed: 12s, execs: 78830 (0/sec), new interesting: 20 (total: 273)
fuzz: elapsed: 15s, execs: 78830 (0/sec), new interesting: 20 (total: 273)
fuzz: elapsed: 18s, execs: 78830 (0/sec), new interesting: 20 (total: 273)
fuzz: elapsed: 21s, execs: 78830 (0/sec), new interesting: 20 (total: 273)
fuzz: elapsed: 24s, execs: 78830 (0/sec), new interesting: 20 (total: 273)
fuzz: elapsed: 27s, execs: 78830 (0/sec), new interesting: 20 (total: 273)
fuzz: elapsed: 30s, execs: 78830 (0/sec), new interesting: 20 (total: 273)
May be related to #48591.
colega
Metadata
Metadata
Assignees
Labels
FrozenDueToAgeNeedsInvestigationSomeone 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.fuzzIssues related to native fuzzing supportIssues related to native fuzzing support
Type
Projects
Status
Done
Status
Done
Status
Done