roachtest: monitor_failure failed

cockroachdb / cockroach

CockroachDB — the cloud native, distributed SQL database designed for high availability, effortless scale, and control over data placement.

Other

29.89k stars 3.77k forks source link

roachtest.monitor_failure failed with artifacts on release-24.1 @ 74b732729e074694be98190cc41eef6f845c3df3:

test restore/tpce/8TB/aws/nodes=10/cpus=8 failed: (monitor.go:154).Wait: monitor failure: pq: query execution canceled
EOF [owner=test-eng]
test artifacts and logs in: /artifacts/restore/tpce/8TB/aws/nodes=10/cpus=8/run_1

Parameters:

ROACHTEST_arch=amd64
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

Same failure on other branches

- #127634 roachtest: monitor_failure failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-24.1.3-rc] - #126792 roachtest: monitor_failure failed [O-roachtest O-robot T-testeng X-infra-flake branch-master]

/cc @cockroachdb/test-eng

This test on roachdash | Improve this report!

Jira issue: CRDB-41979

test failover/non-system/deadlock failed: (failover.go:1787).sleepFor: sleep failed: context canceled (monitor.go:154).Wait: monitor failure: monitor user task failed: t.Fatal() was called EOF [owner=test-eng] test artifacts and logs in: /artifacts/failover/non-system/deadlock/cpu_arch=arm64/run_1

cockroachdb / cockroach

roachtest: monitor_failure failed #130292