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

cmd/go: script test hanging with blocked output pipes #53400

Closed
bcmills opened this issue Jun 15, 2022 · 2 comments
Closed

cmd/go: script test hanging with blocked output pipes #53400

bcmills opened this issue Jun 15, 2022 · 2 comments
Assignees
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone

Comments

@bcmills bcmills added this to the Go1.20 milestone Jun 15, 2022
@bcmills bcmills self-assigned this Jun 15, 2022
@bcmills bcmills added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Jun 15, 2022
@bcmills
Copy link
Member Author

bcmills commented Jun 15, 2022

This is some script test hanging while waiting on the subprocess's output pipes to close, with the output pipes stuck open.

This is quite possibly a bug in the go command, but it will be much more straightforward to diagnose once #50436 is implemented. (A workaround in the interim is possible but more complex, because we would either have to run our own pipe-copying goroutines or direct all of the stderr and stdout output pipes for script tests to files.)

I plan to implement #50436 for Go 1.20, so milestoning to Go 1.20.

@bcmills
Copy link
Member Author

bcmills commented Sep 21, 2022

Duplicate of #50187.

@bcmills bcmills closed this as not planned Won't fix, can't repro, duplicate, stale Sep 21, 2022
@golang golang locked and limited conversation to collaborators Sep 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Development

No branches or pull requests

2 participants