Closed cockroach-teamcity closed 1 month ago
while i'm not sure why we hit this exact networking error, the fact that this job failed on this error is not fully unexpected. this patch should make 24.1 less flaky to these shenanigans https://github.com/cockroachdb/cockroach/pull/116957
roachtest.restore/tpce/8TB/aws/nodes=10/cpus=8 failed with artifacts on release-23.2 @ 7ca8340d8b1316144a9f0f53e736f168d99a0bab:
(monitor.go:153).Wait: monitor failure: read tcp 172.17.0.3:34146 -> 3.23.102.210:26257: read: connection timed out
test artifacts and logs in: /artifacts/restore/tpce/8TB/aws/nodes=10/cpus=8/cpu_arch=arm64/run_1
Parameters:
ROACHTEST_arch=arm64
ROACHTEST_cloud=aws
ROACHTEST_coverageBuild=false
ROACHTEST_cpu=8
ROACHTEST_encrypted=false
ROACHTEST_fs=ext4
ROACHTEST_localSSD=false
ROACHTEST_metamorphicBuild=false
ROACHTEST_ssd=0
See: roachtest README
See: How To Investigate (internal)
Grafana is not yet available for aws clusters
We weren't able to reproduce the original flake in this ticket and the follow up flake has no logs unfotunately.
roachtest.restore/tpce/8TB/aws/nodes=10/cpus=8 failed with artifacts on release-23.2 @ f88e669339210a94016ce6555168dfffa5df8159:
Parameters:
ROACHTEST_arch=arm64
ROACHTEST_cloud=aws
ROACHTEST_coverageBuild=false
ROACHTEST_cpu=8
ROACHTEST_encrypted=false
ROACHTEST_fs=ext4
ROACHTEST_localSSD=false
ROACHTEST_metamorphicBuild=false
ROACHTEST_ssd=0
Help
See: roachtest README
See: How To Investigate (internal)
Grafana is not yet available for aws clusters
/cc @cockroachdb/disaster-recoveryThis test on roachdash | Improve this report!
Jira issue: CRDB-39434