Skip to content

roachtest: failover/chaos/read-write failed #108663

@cockroach-teamcity

Description

@cockroach-teamcity

roachtest.failover/chaos/read-write failed with artifacts on master @ 7da4ef5af83c38680c536e7c18a9db61274b9d25:

(failover.go:1790).sleepFor: sleep failed: context canceled
(monitor.go:140).Wait: monitor failure: unexpected node event: n5: cockroach process died (exit code 134)
(cluster.go:2279).Run: cluster.RunE: context canceled
(cluster.go:2279).Run: cluster.RunE: context canceled
(cluster.go:2279).Run: cluster.RunE: context canceled
(cluster.go:2279).Run: cluster.RunE: context canceled
test artifacts and logs in: /artifacts/failover/chaos/read-write/run_1

Parameters: ROACHTEST_arch=amd64 , ROACHTEST_cloud=gce , ROACHTEST_cpu=2 , ROACHTEST_encrypted=false , ROACHTEST_fs=ext4 , ROACHTEST_localSSD=false , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

See: Grafana

/cc @cockroachdb/kv-triage

This test on roachdash | Improve this report!

Jira issue: CRDB-30575

Metadata

Metadata

Assignees

Labels

A-kv-replicationRelating to Raft, consensus, and coordination.C-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.C-test-failureBroken test (automatically or manually discovered).O-roachtestO-robotOriginated from a bot.T-kvKV TeamX-duplicateClosed as a duplicate of another issue.branch-masterFailures and bugs on the master branch.release-blockerIndicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked.

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions