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: tpce/c=100000/nodes=5 failed #117722

Closed
cockroach-teamcity opened this issue Jan 12, 2024 · 3 comments
Closed

roachtest: tpce/c=100000/nodes=5 failed #117722

cockroach-teamcity opened this issue Jan 12, 2024 · 3 comments
Labels
branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. T-testeng TestEng Team
Milestone
24.1

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Jan 12, 2024 •
edited by cockroach-jira-scripts
Loading

roachtest.tpce/c=100000/nodes=5 failed with artifacts on master @ 19f20e8748aea41a9400946bd2517fc729112346:

(cluster.go:2272).Run: full command output in run_073321.872989923_n6_sudo-docker-run-cock.log: COMMAND_PROBLEM: exit status 1
(monitor.go:153).Wait: monitor failure: monitor user task failed: t.Fatal() was called
test artifacts and logs in: /artifacts/tpce/c=100000/nodes=5/run_1

Parameters:

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

See: roachtest README

See: How To Investigate (internal)

See: Grafana

/cc @cockroachdb/test-eng

This test on roachdash | Improve this report!

Jira issue: CRDB-35319
@cockroach-teamcity cockroach-teamcity added branch-master Failures and bugs on the master branch. 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 Jan 12, 2024
@cockroach-teamcity cockroach-teamcity added this to the 24.1 milestone Jan 12, 2024
@renatolabs
Copy link
Contributor

See #117567 (comment).

@renatolabs renatolabs removed the release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. label Jan 12, 2024
@cockroach-teamcity
Copy link
Member Author

roachtest.tpce/c=100000/nodes=5 failed with artifacts on master @ e2ad8d72175a985b11fefe1cb6eacede0654a36c:

(cluster.go:2293).Run: full command output in run_012856.666404387_n6_sudo-docker-run-usea.log: COMMAND_PROBLEM: exit status 1
(monitor.go:153).Wait: monitor failure: monitor user task failed: t.Fatal() was called
test artifacts and logs in: /artifacts/tpce/c=100000/nodes=5/run_1

Parameters:

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

See: roachtest README

See: How To Investigate (internal)

See: Grafana

This test on roachdash | Improve this report!

@renatolabs
Copy link
Contributor

Fixed by #117795.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. T-testeng TestEng Team
Projects
No open projects
Test Engineering
Status: Done
Milestone
24.1
Development

No branches or pull requests
2 participants
@cockroach-teamcity @renatolabs