Skip to content

cmd/go: TestScript/test_fuzz_cache failures [consistent failure] #70429

@gopherbot

Description

@gopherbot
#!watchflakes
default <- pkg == "cmd/go" && test == "TestScript/test_fuzz_cache"

Issue created automatically to collect these failures.

Example (log):

=== RUN   TestScript/test_fuzz_cache
=== PAUSE TestScript/test_fuzz_cache
=== CONT  TestScript/test_fuzz_cache
    script_test.go:139: 2024-11-18T20:59:42Z
    script_test.go:141: $WORK=/home/swarming/.swarming/w/ir/x/t/cmd-go-test-1660985446/tmpdir2734166923/test_fuzz_cache3878632668
2024/11/18 20:59:42 hello.txt:
> handle fossil
> env USER=rsc
> fossil init --date-override 2017-09-22T01:15:36Z hello.fossil
[stdout]
...
        > go test -fuzz=FuzzEmpty -fuzztime=10000x .
        [stdout]
        warning: starting with empty corpus
        fuzz: elapsed: 0s, execs: 0 (0/sec), new interesting: 0 (total: 0)
        fuzz: elapsed: 1s, execs: 10000 (14044/sec), new interesting: 2 (total: 2)
        PASS
        ok  	example.com/y	0.722s
        > stdout 'new interesting: 1'
    script_test.go:163: FAIL: testdata/script/test_fuzz_cache.txt:31: stdout 'new interesting: 1': no match for `(?m)new interesting: 1` in stdout
--- FAIL: TestScript/test_fuzz_cache (74.00s)

watchflakes

Metadata

Metadata

Assignees

No one assigned

    Labels

    NeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions