Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

internal/fuzz: test_fuzz_mutate_crash failure on windows/amd64 due to failure to find float64 crasher #52852

Closed
bcmills opened this issue May 11, 2022 · 1 comment
Closed

internal/fuzz: test_fuzz_mutate_crash failure on windows/amd64 due to failure to find float64 crasher #52852

bcmills opened this issue May 11, 2022 · 1 comment
Labels
FrozenDueToAge fuzz Issues related to native fuzzing support NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Go1.19

Comments

@bcmills
Copy link
Contributor

bcmills commented May 11, 2022 

--- FAIL: TestScript (0.01s)
    --- FAIL: TestScript/test_fuzz_mutate_crash (88.46s)
        script_test.go:260: 
            # Tests that a crash caused by a mutator-discovered input writes the bad input
            # to testdata, and fails+reports correctly. This tests the end-to-end behavior
            # of the mutator finding a crash while fuzzing, adding it as a regression test
            # to the seed corpus in testdata, and failing the next time the test is run. (0.000s)
            # Running the seed corpus for all of the targets should pass the first
            # time, since nothing in the seed corpus will cause a crash. (2.332s)
            # Running the fuzzer should find a crashing input quickly. (12.085s)
            # Now, the failing bytes should have been added to the seed corpus for
            # the target, and should fail when run without fuzzing. (62.971s)
            # Running the fuzzer should find a crashing input quickly for fuzzing two types. (2.694s)
            # Running the fuzzer should find a crashing input quickly for an integer. (4.696s)
            # Running the fuzzer should find a crashing input quickly for a bool. (2.045s)
            # Running the fuzzer should find a crashing input quickly for a float. (1.497s)
            > ! go test -run=FuzzFloat -fuzz=FuzzFloat -fuzztime=100x -fuzzminimizetime=1000x
            [stdout]
            warning: starting with empty corpus
            fuzz: elapsed: 0s, execs: 0 (0/sec), new interesting: 0 (total: 0)
            fuzz: elapsed: 0s, execs: 100 (806/sec), new interesting: 1 (total: 1)
            PASS
            ok  	m	0.271s
            FAIL: testdata\script\test_fuzz_mutate_crash.txt:89: unexpected command success
            
FAIL
FAIL	cmd/go	210.036s

greplogs -l -e 'FAIL: TestScript/test_fuzz_mutate_crash .*(\n\s+.*)* unexpected command success'
2022-05-10T19:40:04-526de61/windows-amd64-longtest

(attn @golang/fuzzing)
@bcmills bcmills added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. fuzz Issues related to native fuzzing support labels May 11, 2022
@bcmills bcmills added this to the Go1.19 milestone May 11, 2022
@gopherbot
Copy link

Change https://go.dev/cl/405855 mentions this issue: cmd/go: don't assume decimal in test_fuzz_mutate_crash

@golang golang locked and limited conversation to collaborators May 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge fuzz Issues related to native fuzzing support NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
Go Security
Status: No status
Milestone
Go1.19
Development

No branches or pull requests
2 participants
@bcmills @gopherbot