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.

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

cmd/go: TestScript/test_fuzz_dup_cache failing locally #51024

Closed
katiehockman opened this issue Feb 4, 2022 · 2 comments
Closed

cmd/go: TestScript/test_fuzz_dup_cache failing locally #51024

katiehockman opened this issue Feb 4, 2022 · 2 comments
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. Testing An issue that has been verified to require only test changes, not just a test failure.
Milestone

Comments

@katiehockman
Copy link
Contributor

katiehockman commented Feb 4, 2022

I'm seeing local failures for the test_fuzz_dup_cache locally.

~ go test cmd/go -run=Script/test_fuzz_dup_cache
go test proxy running at GOPROXY=http://127.0.0.1:61194/mod
--- FAIL: TestScript (0.01s)
    --- FAIL: TestScript/test_fuzz_dup_cache (3.32s)
        script_test.go:259: 
            # This test checks that cached corpus loading properly handles duplicate entries (this can
            # happen when a f.Add value has a duplicate entry in the cached corpus.) Duplicate entries
            # should be discarded, and the rest of the cache should be loaded as normal. (3.195s)
            > env GOCACHE=$WORK/cache
            > env GODEBUG=fuzzdebug=1
            > mkdir -p $GOCACHE/fuzz/fuzztest/FuzzTarget
            > go run ./populate $GOCACHE/fuzz/fuzztest/FuzzTarget
            > go test -fuzz=FuzzTarget -fuzztime=10x .
            [stderr]
            package fuzztest: no Go files in /Users/katiehockman/godev/src/fuzztest
            [exit status 1]
            FAIL: testdata/script/test_fuzz_dup_cache.txt:14: unexpected command failure
            
FAIL
FAIL    cmd/go  4.716s
FAIL

/cc @rolandshoemaker

@katiehockman katiehockman added Testing An issue that has been verified to require only test changes, not just a test failure. 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 Feb 4, 2022
@katiehockman katiehockman added this to the Go1.18 milestone Feb 4, 2022
@bcmills
Copy link
Member

bcmills commented Feb 4, 2022

Is it possible that your GOROOT/src includes a fuzztest subdirectory?

If so, this could be a symptom of #39285.

@katiehockman
Copy link
Contributor Author

Yep, that's it.
I'll go ahead and close this, and we can track the work in that issue. Thanks for the find :)

@golang golang locked and limited conversation to collaborators Feb 4, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
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. Testing An issue that has been verified to require only test changes, not just a test failure.
Projects
Status: No status
Development

No branches or pull requests

3 participants