cockroachdb / cockroachdb/cockroach

roachtest: tpcc-nowait/isolation-level=mixed/nodes=3/w=1 failed

Open
#175,652 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

branch-release-25.4 C-test-failure O-roachtest O-robot release-blocker T-testeng
Dominant language
Go
Stars
32.5k
Forks
4.1k
PR metrics pending

Description

roachtest.tpcc-nowait/isolation-level=mixed/nodes=3/w=1 failed with artifacts on release-25.4 @ d1138426154abf499fb7c8ac15d92a28ff30c294:

(monitor.go:267).Wait: monitor failure: full command output in run_084501.504741516_n4_cockroach-workload-r.log: COMMAND_PROBLEM: exit status 1
test artifacts and logs in: /artifacts/tpcc-nowait/isolation-level=mixed/nodes=3/w=1/run_1

Parameters:

  • arch=amd64
  • cloud=gce
  • coverageBuild=false
  • cpu=16
  • encrypted=false
  • metamorphicLeases=leader
  • runtimeAssertionsBuild=false
  • ssd=0
Help

See: roachtest README

See: How To Investigate (internal)

See: Grafana

/cc @cockroachlabs/test-eng

This test on roachdash | Improve this report!

Jira issue: CRDB-68552

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with pkg/cmd/roachtest/README.md and monitor.go:267, then inspect the linked TeamCity artifacts and run_084501.504741516_n4_cockroach-workload-r.log. Trace why the tpcc-nowait run exits with status 1, identify the root cause, and verify the test passes after the fix.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
databases, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.