Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
cockroach-teamcity opened this issue May 25, 2024 · 1 comment
Closed

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

cockroach-teamcity opened this issue May 25, 2024 · 1 comment
Labels
A-testing Testing tools and infrastructure branch-release-23.1 Used to mark GA and release blockers, technical advisories, and bugs for 23.1 C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. P-3 Issues/test failures with no fix SLA release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-kv KV Team
Projects
Milestone

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented May 25, 2024

roachtest.failover/chaos/read-only failed with artifacts on release-23.1 @ 621dd2486f24a0e76ecbc63a98f3f244e42d734d:

(disk_stall.go:301).Setup: full command output in run_121431.610825887_n1-10_echo-0-sudo-blockdev.log: COMMAND_PROBLEM: exit status 1
(cluster.go:2144).Run: context canceled
(cluster.go:2144).Run: context canceled
(cluster.go:2144).Run: 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_metamorphicBuild=false
  • ROACHTEST_ssd=0
Help

See: roachtest README

See: How To Investigate (internal)

See: Grafana

Same failure on other branches

/cc @cockroachdb/kv-triage

This test on roachdash | Improve this report!

Jira issue: CRDB-39018

@cockroach-teamcity cockroach-teamcity added branch-release-23.1 Used to mark GA and release blockers, technical advisories, and bugs for 23.1 C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-kv KV Team labels May 25, 2024
@cockroach-teamcity cockroach-teamcity added this to the 23.1 milestone May 25, 2024
@cockroach-teamcity cockroach-teamcity added this to roachtest/unit test backlog in KV May 25, 2024
@nicktrav nicktrav added the P-3 Issues/test failures with no fix SLA label Jun 10, 2024
@andrewbaptist
Copy link
Collaborator

Closing as this is on 23.1. This was fixed on the 23.2+ releases.

@arulajmani arulajmani added C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. A-testing Testing tools and infrastructure labels Jun 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-testing Testing tools and infrastructure branch-release-23.1 Used to mark GA and release blockers, technical advisories, and bugs for 23.1 C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. P-3 Issues/test failures with no fix SLA release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-kv KV Team
Projects
KV
roachtest/unit test backlog
Development

No branches or pull requests

4 participants