roachtest: restore/tpce/8TB/aws/nodes=10/cpus=8 failed [one node IO/CPU starved] #111160
Description
roachtest.restore/tpce/8TB/aws/nodes=10/cpus=8 failed with artifacts on master @ b1a641f1d27653a4e93154926be57d0cae864bd6:
(monitor.go:153).Wait: monitor failure: pq: pausing due to error; use RESUME JOB to try to proceed once the issue is resolved, or CANCEL JOB to rollback: exhausted retries: importing 14656 ranges: inbox communication error: grpc: context canceled [code 1/Canceled]
test artifacts and logs in: /artifacts/restore/tpce/8TB/aws/nodes=10/cpus=8/run_1
Parameters: ROACHTEST_arch=amd64
, ROACHTEST_cloud=aws
, ROACHTEST_cpu=8
, ROACHTEST_encrypted=false
, ROACHTEST_fs=ext4
, ROACHTEST_localSSD=false
, ROACHTEST_ssd=0
Help
See: roachtest README
See: How To Investigate (internal)
Grafana is not yet available for aws clusters
Same failure on other branches
- roachtest: restore/tpce/8TB/aws/nodes=10/cpus=8 failed #110764 roachtest: restore/tpce/8TB/aws/nodes=10/cpus=8 failed [A-kv-replication C-bug C-test-failure O-roachtest O-robot T-disaster-recovery T-kv-replication branch-release-23.1]
This test on roachdash | Improve this report!
Jira issue: CRDB-31795
Metadata
Metadata
Assignees
Labels
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Broken test (automatically or manually discovered).Originated from a bot.Prevent automatic commenting from CI test failuresFailures and bugs on the master branch.Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked.