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/benchmarks/sweet/cmd/sweet: timeout in TestSweetEndToEnd #51052
Comments
That's very odd. Other successful runs of this test take around 3-4 minutes. Based on the output, this looks like maybe a deadlock in bleve? |
There are some I suspect that the timeout is due to a subprocess (compare #50436):
|
The subprocess seems to be the one executing |
Yeah, that makes sense. I mistakenly thought I'd landed the change that dumps subprocess output. I did not. Since it's |
Mainly, plumb through Contexts everywhere, so that if things are broken you can have the subprocess dump useful errors before the text is terminated. You can use |
greplogs --dashboard -md -l -e 'panic: test timed out .*\n(?:\ngoroutine \d+ .*:\n(.+\n)*)*^golang\.org/x/benchmarks/sweet/cmd/sweet_test.TestSweetEndToEnd' --since=2022-01-01
2022-02-07T07:14:28-e4ea61d-334a591/linux-amd64-longtest
(attn @mknyszek)
The text was updated successfully, but these errors were encountered: