Skip to content
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

x/net/http2: TestServer failures with "write: broken pipe" on openbsd #52208

Open
bcmills opened this issue Apr 7, 2022 · 1 comment
Open

x/net/http2: TestServer failures with "write: broken pipe" on openbsd #52208

bcmills opened this issue Apr 7, 2022 · 1 comment
Labels
arch-arm64 arch-mips NeedsInvestigation OS-OpenBSD
Milestone

Comments

@bcmills
Copy link
Member

@bcmills bcmills commented Apr 7, 2022

--- FAIL: TestServer (10.64s)
    server_test.go:349: Error writing initial SETTINGS frame from client to server: write tcp 127.0.0.1:21462->127.0.0.1:34837: write: broken pipe
    server_test.go:267: Framer write log:
        2022-04-07 10:25:48.715770953 Framer 0xc001405500: wrote SETTINGS len=0
FAIL
FAIL	golang.org/x/net/http2	282.655s

greplogs --dashboard -md -l -e 'FAIL: TestServer .*(?:\n .*)*write: broken pipe'

2022-04-06T20:46:47-749bd19-81ae993/openbsd-mips64-jsing
2022-04-06T03:13:34-749bd19-5bb2628/openbsd-mips64-jsing
2022-02-08T15:30:12-cd36cc0-ef06a5f/openbsd-mips64-jsing
2021-09-12T16:46:58-a5e0955-ad97d20/openbsd-arm64-jsing

(attn @4a6f656c; CC @neild)

Since this only appears to affect certain OpenBSD builders, I plan to add a test skip and not follow up further.

@bcmills bcmills added OS-OpenBSD NeedsInvestigation arch-mips labels Apr 7, 2022
@bcmills bcmills added this to the Backlog milestone Apr 7, 2022
@gopherbot
Copy link

@gopherbot gopherbot commented Apr 7, 2022

Change https://go.dev/cl/398794 mentions this issue: http2: skip "write: broken pipe" failures in TestServer on OpenBSD

gopherbot pushed a commit to golang/net that referenced this issue Apr 7, 2022
This failure mode has been observed on openbsd/mips64 and
openbsd/arm64.

I have not diagnosed the precise root cause, but I suspect a platform
bug — perhaps a bad interaction with the relatively weakly-ordered
memory models on these CPUs.

For golang/go#52208.

Change-Id: I0ab0285cc395d22742ced8f28d5c9c3280fcd1e3
Reviewed-on: https://go-review.googlesource.com/c/net/+/398794
Trust: Bryan Mills <bcmills@google.com>
Run-TryBot: Bryan Mills <bcmills@google.com>
Reviewed-by: Ian Lance Taylor <iant@golang.org>
Auto-Submit: Bryan Mills <bcmills@google.com>
TryBot-Result: Gopher Robot <gobot@golang.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
arch-arm64 arch-mips NeedsInvestigation OS-OpenBSD
Projects
None yet
Development

No branches or pull requests

2 participants