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: tpce/c=5000/nodes=3 failed #124208

Closed
cockroach-teamcity opened this issue May 15, 2024 · 2 comments
Closed

roachtest: tpce/c=5000/nodes=3 failed #124208

cockroach-teamcity opened this issue May 15, 2024 · 2 comments
Assignees
Labels
A-testing Testing tools and infrastructure branch-release-24.1.0-rc Used to mark GA and release blockers and technical advisories for 24.1.0-rc 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. T-kv KV Team
Milestone

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented May 15, 2024

roachtest.tpce/c=5000/nodes=3 failed with artifacts on release-24.1.0-rc @ 9d77dad6162bc528e725d0c57ec01c6a07d2aea2:

(cluster.go:2349).Run: full command output in run_120110.966370923_n4_sudo-docker-run-usea.log: COMMAND_PROBLEM: exit status 101
(monitor.go:154).Wait: monitor failure: monitor user task failed: t.Fatal() was called
test artifacts and logs in: /artifacts/tpce/c=5000/nodes=3/run_1

Parameters:

  • ROACHTEST_arch=amd64
  • ROACHTEST_cloud=gce
  • ROACHTEST_coverageBuild=false
  • ROACHTEST_cpu=4
  • ROACHTEST_encrypted=false
  • ROACHTEST_fs=ext4
  • ROACHTEST_localSSD=true
  • ROACHTEST_metamorphicBuild=false
  • ROACHTEST_ssd=1
Help

See: roachtest README

See: How To Investigate (internal)

See: Grafana

Same failure on other branches

/cc @cockroachdb/test-eng

This test on roachdash | Improve this report!

Jira issue: CRDB-38766

@cockroach-teamcity cockroach-teamcity added branch-release-24.1.0-rc Used to mark GA and release blockers and technical advisories for 24.1.0-rc 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-testeng TestEng Team labels May 15, 2024
@cockroach-teamcity cockroach-teamcity added this to the 24.1 milestone May 15, 2024
@nvanbenschoten
Copy link
Member

thread 'main' panicked at 'No option 'bucket-auth' defined', /usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/getopts-0.2.21/src/lib.rs:799:21

I must have broken this with https://github.com/cockroachlabs/tpc-e/pull/81.

@nvanbenschoten nvanbenschoten removed the release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. label May 15, 2024
@nvanbenschoten nvanbenschoten self-assigned this May 15, 2024
@exalate-issue-sync exalate-issue-sync bot added T-kv KV Team and removed T-testeng TestEng Team labels May 15, 2024
@blathers-crl blathers-crl bot added this to Incoming in KV May 15, 2024
@pav-kv pav-kv 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 May 15, 2024
@nvanbenschoten
Copy link
Member

Should be fixed by https://github.com/cockroachlabs/tpc-e/pull/82.

Test Engineering automation moved this from Triage to Done May 15, 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-24.1.0-rc Used to mark GA and release blockers and technical advisories for 24.1.0-rc 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. T-kv KV Team
Projects
KV
Incoming
Development

No branches or pull requests

3 participants