-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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/compile/internal/syntax: TestStdLib verbosely broken on Windows #35175
Comments
Ah, here we go:
|
The actual error was a silly oversight for Windows (hardwired path separator). The verbose long test output is independent. Will fix separately (see #35223). |
Change https://golang.org/cl/203889 mentions this issue: |
Change https://golang.org/cl/223703 mentions this issue: |
@gopherbot, please consider this issue for backport to Go 1.13. This is a test fix. It is needed to resolve a test failure in the |
Backport issue(s) opened: #37901 (for 1.13). Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://golang.org/wiki/MinorReleases. |
…ath separator in test Windows uses '\' not '/'. For #35175. Fixes #37901. Change-Id: Ib3d01dcf148fc0675496d5213f5bcc9cf210a6fc Reviewed-on: https://go-review.googlesource.com/c/go/+/203889 Reviewed-by: Bryan C. Mills <[email protected]> Run-TryBot: Brad Fitzpatrick <[email protected]> (cherry picked from commit a754d29) Reviewed-on: https://go-review.googlesource.com/c/go/+/223703 Reviewed-by: Robert Griesemer <[email protected]> Run-TryBot: Andrew Bonventre <[email protected]>
https://build.golang.org/log/1d9e9c5f8db18b185d84dffca1c0372654dfcfa1 shows an amazingly long test failure on the
windows-amd64-longtest
builder.I can't make heads or tails of it myself, and I don't know how long it's been broken, but it seems clear that something is going very wrong in the test on Windows.
CC @alexbrainman @zx2c4
The text was updated successfully, but these errors were encountered: