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.

Sign up for GitHub

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

Jump to bottom

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

Closed
cockroach-teamcity opened this issue May 16, 2024 · 3 comments
Closed

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

cockroach-teamcity opened this issue May 16, 2024 · 3 comments
Assignees
@andrewbaptist
Labels
A-testing Testing tools and infrastructure branch-release-23.2 Used to mark GA and release blockers, technical advisories, and bugs for 23.2 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-2 Issues/test failures with a fix SLA of 3 months T-kv KV Team
Milestone
23.2

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented May 16, 2024 •
edited by cockroach-jira-scripts
Loading

roachtest.failover/chaos/read-only failed with artifacts on release-23.2 @ 2a64678e65fab1fdeb761ef0d2cc06698c1abb7a:

(test_runner.go:1153).runTest: test timed out (1h0m0s)
test artifacts and logs in: /artifacts/failover/chaos/read-only/run_1

Parameters:

  • ROACHTEST_arch=amd64
  • ROACHTEST_cloud=gce
  • ROACHTEST_coverageBuild=false
  • 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

/cc @cockroachdb/kv-triage

This test on roachdash | Improve this report!

Jira issue: CRDB-38808
@cockroach-teamcity cockroach-teamcity added branch-release-23.2 Used to mark GA and release blockers, technical advisories, and bugs for 23.2 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 16, 2024
@cockroach-teamcity cockroach-teamcity added this to the 23.2 milestone May 16, 2024
@pav-kv
Copy link
Collaborator

pav-kv commented May 17, 2024

Looks similar to #123607 and #123122. Potentially need to backport the fix mentioned in #123122 (comment).

Having some trouble with TeamCity - can't open artifacts now to confirm anything.

@cockroach-teamcity
Copy link
Member Author

roachtest.failover/chaos/read-only failed with artifacts on release-23.2 @ 63500cca942227225a77aa69a60f77f978100b82:

(failover.go:1779).sleepFor: sleep failed: context canceled
(monitor.go:153).Wait: monitor failure: monitor user task failed: t.Fatal() was called
(cluster.go:2344).Run: context canceled
(cluster.go:2344).Run: context canceled
(cluster.go:2344).Run: context canceled
(cluster.go:2344).Run: context canceled
test artifacts and logs in: /artifacts/failover/chaos/read-only/run_1

Parameters:

  • ROACHTEST_arch=amd64
  • ROACHTEST_cloud=gce
  • ROACHTEST_coverageBuild=false
  • 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

This test on roachdash | Improve this report!

@kvoli kvoli 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 P-2 Issues/test failures with a fix SLA of 3 months and removed release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. labels May 20, 2024
@cockroach-teamcity cockroach-teamcity mentioned this issue May 25, 2024
Closed
@cockroach-teamcity cockroach-teamcity mentioned this issue Jun 5, 2024
Closed
@pav-kv pav-kv mentioned this issue Jun 5, 2024
Closed
@andrewbaptist
Copy link
Collaborator

Closing now that #124608 is merged.

@github-project-automation github-project-automation bot moved this to roachtest/unit test backlog in KV Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@andrewbaptist andrewbaptist

Labels
A-testing Testing tools and infrastructure branch-release-23.2 Used to mark GA and release blockers, technical advisories, and bugs for 23.2 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-2 Issues/test failures with a fix SLA of 3 months T-kv KV Team
Projects
No open projects
KV
Status: roachtest/unit test backlog
Milestone
23.2
Development

No branches or pull requests
4 participants
@pav-kv @cockroach-teamcity @kvoli @andrewbaptist