x/net/http2: test timeouts on js-wasm builder #36088
Open
Milestone
Comments
The earliest of these failures I could find by manual inspection of the dashboard is https://build.golang.org/log/8d467bcc05d2e38b1b903835bb15858dfc547a62, at CL 208798. |
That's also in The failure mode is otherwise the same: stuff blocked in |
CC @neelance in case you haven't seen this one. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2019-12-09T16:08:50-c0dbc17/js-wasm has an interesting timeout failure.
It's not obvious to me whether it is due to a bug in the test, a bug in the
js/wasm
standard library, or a bug inx/net/http2
or one of its dependencies that happens to be exposed by the different goroutine scheduling onjs/wasm
.The presence of a goroutine blocked in
net.(*bufferedPipe).Read
viacrypto/tls
makes me suspect a concurrency bug in eithergolang.org/x/net/http2
orcrypto/tls
, but admittedly that evidence is not compelling.I also can't reliably determine how often this occurs or on what platforms because I can't fetch most of the
x/net
logs (#35515).CC @bradfitz @FiloSottile @tombergan
The text was updated successfully, but these errors were encountered: