-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
os: TestPipeEOF failures with "timed out waiting for read" #36107
Comments
This comment has been minimized.
This comment has been minimized.
A more thorough history, including a failure in 2021:
2021-03-25T19:24:25-569c86d/darwin-amd64-10_14 |
This test has an arbitrary short timeout: It also has several moderately long (10ms) sleeps, whose purpose isn't obvious: |
The sleeps come straight from the test case in #24164. I expect it could be written better. |
Change https://go.dev/cl/457336 mentions this issue: |
Change https://go.dev/cl/458015 mentions this issue: |
- Use testenv.Command instead of exec.Command to try to get more useful timeout behavior. - Parallelize tests that appear not to require global state. (And add explanatory comments for a few that are not parallelizable for subtle reasons.) - Consolidate some “Helper” tests with their parent tests. - Use t.TempDir instead of os.MkdirTemp when appropriate. - Factor out subtests for repeated test helpers. For #36107. Updates #22315. Change-Id: Ic24b6957094dcd40908a59f48e44c8993729222b Reviewed-on: https://go-review.googlesource.com/c/go/+/458015 Reviewed-by: Ian Lance Taylor <iant@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Bryan Mills <bcmills@google.com> Auto-Submit: Bryan Mills <bcmills@google.com>
2019-12-12T13:32:03-c39cd41/darwin-amd64-10_14:
See previously #35275, which had a very similar failure mode but with an additional
file already closed
message at the end.This is the only failure I could find after CL 204800.
CC @ianlancetaylor
The text was updated successfully, but these errors were encountered: