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/internal/envcmd: FuzzPrintEnvEscape failures #59998
Comments
Found new dashboard test flakes for:
2023-05-05 14:28 freebsd-amd64-12_3 go@f379e789 cmd/go/internal/envcmd.FuzzPrintEnvEscape (log)
|
Found new dashboard test flakes for:
2023-05-05 14:37 freebsd-amd64-13_0 go@72c33a5e cmd/go/internal/envcmd.FuzzPrintEnvEscape (log)
2023-05-05 14:54 freebsd-amd64-12_3 go@574431cf cmd/go/internal/envcmd.FuzzPrintEnvEscape (log)
|
Found new dashboard test flakes for:
2023-05-05 15:03 freebsd-amd64-12_3 go@761e8138 cmd/go/internal/envcmd.FuzzPrintEnvEscape (log)
|
This may be a variation on #22315. I suggest that we modify the test to pass the script directly to |
Found new dashboard test flakes for:
2023-05-05 19:07 freebsd-amd64-13_0 go@26899ef3 cmd/go/internal/envcmd.FuzzPrintEnvEscape (log)
|
Found new dashboard test flakes for:
2023-05-08 13:37 freebsd-amd64-13_0 go@9fa81a88 cmd/go/internal/envcmd.FuzzPrintEnvEscape (log)
|
TryBot failures for me too: https://storage.googleapis.com/go-build-log/71a7e610/freebsd-amd64-12_3_94d04626.log cc @matloob |
Change https://go.dev/cl/493555 mentions this issue: |
Found new dashboard test flakes for:
2023-05-08 16:50 freebsd-amd64-12_3 go@bc3bdfa9 cmd/go/internal/envcmd.FuzzPrintEnvEscape (log)
|
Instead of writing them to a file and executing that file. For #59998 Change-Id: I341786926762359f67dccb475295afbbb8ed1054 Reviewed-on: https://go-review.googlesource.com/c/go/+/493555 Run-TryBot: Michael Matloob <matloob@golang.org> Reviewed-by: Michael Matloob <matloob@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com>
Should have been fixed by CL 493555, if our hypothesis about the cause is correct. |
Let's assume it is fixed by the CL. If it happens again watchflakes will reopen. Thanks. |
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: