-
Notifications
You must be signed in to change notification settings - Fork 3.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
roachtest: restore2TB/nodes=32 failed #84132
Comments
roachtest.restore2TB/nodes=32 failed with artifacts on release-22.1 @ 64d9c24214b7d6912ecc1a8c8ed93073134c860d:
Same failure on other branches
|
determined this is a test infra flake. Closing this issue. We see the same error message on roachtests restore2TB* across master, 22.1, and 21.2.
I could not repro this, implying these roachtests are not failing consistently, but clearly they’re failing quite often, and across many releases. After scanning the commit histories of each branch, notably 21.2 which has the fewest commits, I do not see any commit (e.g. a gcs vendor upgrade) that could relate to these new networking issues, which makes me think the root cause is unrelated to restore or the cockroach binary. It's also worth noting that we have hit this error before and that it was made retryable way back in 2018 - googleapis/google-cloud-go@d19004d |
roachtest.restore2TB/nodes=32 failed with artifacts on release-22.1 @ f9e7181a96fa72e48e3ac0df730843fed4a09ec4:
Help
See: roachtest README
See: How To Investigate (internal)
Same failure on other branches
This test on roachdash | Improve this report!
Jira issue: CRDB-17481
The text was updated successfully, but these errors were encountered: