Skip to content

roachtest: failover/chaos/read-only failed #106108

@cockroach-teamcity

Description

@cockroach-teamcity

roachtest.failover/chaos/read-only failed with artifacts on master @ 428dc9da6a320de218460de6c6c8807caa4ded98:

(test_runner.go:1075).runTest: test timed out (1h0m0s)
(cluster.go:2282).Run: output in run_115254.651623685_n10_cockroach-workload-i: ./cockroach workload init kv --splits 1000 --insert-count 100000 {pgurl:1} returned: COMMAND_PROBLEM: exit status 137
(cluster.go:2282).Run: cluster.RunE: context canceled
(cluster.go:2282).Run: cluster.RunE: context canceled
(cluster.go:2282).Run: cluster.RunE: context canceled
(cluster.go:2282).Run: cluster.RunE: context canceled
test artifacts and logs in: /artifacts/failover/chaos/read-only/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)

/cc @cockroachdb/kv-triage

This test on roachdash | Improve this report!

Jira issue: CRDB-29407

Metadata

Metadata

Assignees

Labels

C-test-failureBroken test (automatically or manually discovered).O-roachtestO-robotOriginated from a bot.X-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