cockroachdb / cockroachdb/cockroach

basalt-26.3: crosscluster/logical/txnmode: TestTxnModeLWW failed

Open
#174,380 3 comments 0 reactions 0 assignees View on GitHub
A-cdc branch-basalt-26.3 C-test-failure O-robot release-blocker T-cdc
Dominant language
Go
Stars
32.5k
Forks
4.1k
PR merge metrics
PR metrics pending

Description

crosscluster/logical/txnmode.TestTxnModeLWW [failed](https://mesolite.cluster.engflow.com/invocations/default/3972bad9-cd6a-4d0d-96fe-e830383525c5?testReportRun=1&testReportShard=3&testReportAttempt=1#targets-Ly9wa2cvY3Jvc3NjbHVzdGVyL2xvZ2ljYWwvdHhubW9kZTp0eG5tb2RlX3Rlc3Q=) on basalt-26.3 @ [56cb5d5d608e6e57059d3a85dfd948cc917c4a17](https://github.com/cockroachdb/cockroach/commits/56cb5d5d608e6e57059d3a85dfd948cc917c4a17):

```
=== RUN TestTxnModeLWW
test_log_scope.go:172: test logs captured to: outputs.zip/logTestTxnModeLWW3713448922
test_log_scope.go:82: use -show-logs to present logs inline
test_server_shim.go:168: automatically injected a shared process virtual cluster under test; see comment at top of test_server_shim.go for details.
=== RUN TestTxnModeLWW/transactional
```

Parameters:
- attempt=1
- race=true
- run=1
- shard=3
Help

See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)

/cc @cockroachlabs/cdc

[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestTxnModeLWW.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)

Jira issue: CRDB-67656

Contributor guide

Open the contributing guide

Research direction

Start with crosscluster/logical/txnmode.TestTxnModeLWW and reproduce the failure using the linked report's parameters: attempt=1, race=true, run=1, and shard=3. Inspect the captured logs referenced by test_log_scope.go and the shared process virtual-cluster context in test_server_shim.go; done means identifying the failure cause and getting the test to pass.

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
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.