go: sync: TestPool failure on windows-amd64-2016
Noticed on build.golang.org.
https://build.golang.org/log/a3f357b132ef8cb703e42085a50c8c4499e64301
##### sync -cpu=10
--- FAIL: TestPool (0.00s)
pool_test.go:29: got "b"; want a
FAIL
FAIL sync 0.412s
First showed up after CL 42090, although that seems unlikely to be the cause.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 16 (14 by maintainers)
Note that the test is formally broken/incorrect. So any innocent change can suddenly cause increased failure rate it in. Does cl/42770 help? We could also use procPin/procUnpin around the test, that should reflect the intention of the test – within same P reuse order is LIFO.