cockroachdb / cockroachdb/cockroach
basalt-26.3: roachtest: tpcc-nowait/isolation-level=mixed/nodes=3/w=1 failed
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
roachtest.tpcc-nowait/isolation-level=mixed/nodes=3/w=1 failed with artifacts on basalt-26.3 @ 410866d934770553b0ff008caa721a72632dbaaa:
Failed with:
(monitor.go:267).Wait: monitor failure: full command output in run_090554.616522577_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
Cluster Node to Ip Mapping:
| Node | Public IP | Private IP |
|---|---|---|
| teamcity-21524345-1789883775-51-n4cpu16-0001 | 10.91.100.143 | |
| teamcity-21524345-1789883775-51-n4cpu16-0002 | 10.91.100.120 | |
| teamcity-21524345-1789883775-51-n4cpu16-0003 | 10.91.100.127 | |
| teamcity-21524345-1789883775-51-n4cpu16-0004 | 10.91.97.72 |
Parameters:
arch=amd64cloud=gcecoverageBuild=falsecpu=16diskCount=0encrypted=falsemetamorphicLeases=defaultruntimeAssertionsBuild=false
Help
See: roachtest README
See: How To Investigate (internal)
See: Grafana
Logs were not uploaded to Datadog
Same failure on other branches
- #175652 roachtest: tpcc-nowait/isolation-level=mixed/nodes=3/w=1 failed [C-test-failure O-roachtest O-robot T-testeng branch-release-25.4 release-blocker]
This test on roachdash | Improve this report!
Jira issue: CRDB-68572
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the run_090554.616522577_n4_cockroach-workload-r.log artifact under /artifacts/tpcc-nowait/isolation-level=mixed/nodes=3/w=1, then consult the roachtest README and Grafana link. Compare the same failure reported in #175652. Done means identifying the cause of the workload failure and resolving or clearly documenting the test failure.
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