go test proxy running at GOPROXY=http://127.0.0.1:54100/mod
--- FAIL: TestScript (0.01s)
    --- FAIL: TestScript/test_fuzz_minimize_interesting (3.78s)
        script_test.go:257: 
            # Test that when an interesting value is discovered (one that expands coverage),
            # the fuzzing engine minimizes it before writing it to the cache.
            #
            # The program below starts with a seed value of length 100, but more coverage
            # will be found for any value other than the seed. We should end with a value
            # in the cache of length 1 (the minimizer currently does not produce empty
            # strings). check_cache.go confirms that.
            #
            # We would like to verify that ALL values in the cache were minimized to a
            # length of 1, but this isn't always possible when new coverage is found in
            # functions called by testing or internal/fuzz in the background. (3.574s)
            > go test -c -fuzz=.  # Build using shared build cache for speed.
            > env GOCACHE=$WORK/gocache
            > exec ./fuzz.test$GOEXE -test.fuzzcachedir=$GOCACHE/fuzz -test.fuzz=FuzzMinCache -test.fuzztime=1000x
            [stdout]
            --- FAIL: FuzzMinCache (0.60s)
                cannot unmarshal empty string
            FAIL
            [stderr]
            fuzz: elapsed: 0s, gathering baseline coverage: 0/1 completed
            fuzz: elapsed: 0s, gathering baseline coverage: 1/1 completed, now fuzzing with 16 workers
            fuzz: elapsed: 1s, execs: 551 (1226/sec), new interesting: 4 (total: 4)
            [exit status 1]
            FAIL: testdata\script\test_fuzz_minimize_interesting.txt:18: unexpected command failure
            
FAIL
FAIL	cmd/go	277.000s