-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/go: TestGoTestJSON failing on Plan 9, DragonFly BSD and Solaris #22665
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
Comments
This test seems to succeed only on SMP machines. |
I see linux/386 failures, too https://build.golang.org/log/b6647d0a867799ff03d09540c1f1e6c40940815a and here on linux/amd64: https://build.golang.org/log/43557fbe0bd51a2e49a16899b26bde30fc791aa1 I think it's just flaky. |
Yes, it's flaky, but it also never works on the plan9/386 builder which is uniprocessor. I reproduced the issue at home by running the test on the same Plan 9 machine with SMP enabled and SMP disabled: the test only works when SMP is enabled. |
Change https://golang.org/cl/77130 mentions this issue: |
The flakiness can probably be reduced by increasing the number of tries. |
Ah, thanks. We'll need another issue to track the flakiness, then. |
I think it should be fine to track it here. |
Yes, the Dragonfly builder happens to be uniprocessor. |
Change https://golang.org/cl/77310 mentions this issue: |
CL 76873 added TestGoTestJSON. This test is failing on Plan 9, DragonFly BSD and Solaris.
See https://build.golang.org/log/16d3232d3e0ff30e3239e6a139f65267b9f2bab2
@rsc
The text was updated successfully, but these errors were encountered: