We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
According to dashboard linux-amd64-longtest was having timeouts starting from 28 May 17:08 until 29 May 17:45. Log say that timeout was 3 minutes.
linux-amd64-longtest
We should consider raising the timeout limit because testing of cmd/go takes at least 3 minutes.
The text was updated successfully, but these errors were encountered:
Change https://golang.org/cl/115016 mentions this issue: dashboard: increase TIMEOUT_SCALE to 2 for linux-amd64-longtest
dashboard: increase TIMEOUT_SCALE to 2 for linux-amd64-longtest
Sorry, something went wrong.
golang/build@e7d3cfb
Timeouts all over the dashboard. I guess it was not deployed yet...
Ended up raising the same in #25886, because I failed to find this issue. We can use that one to track why the builder hasn't seen the fix.
No branches or pull requests
According to dashboard
linux-amd64-longtest
was having timeouts starting from 28 May 17:08 until 29 May 17:45. Log say that timeout was 3 minutes.We should consider raising the timeout limit because testing of cmd/go takes at least 3 minutes.
The text was updated successfully, but these errors were encountered: