cockroachdb / cockroachdb/cockroach

basalt-26.3.2-rc-20260908: crosscluster/logical/txnmode: TestTxnModeCreateLogicallyReplicated failed

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

Nobody has claimed this yet.

A-cdc branch-basalt-26.3.2-rc-20260908 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.TestTxnModeCreateLogicallyReplicated failed on basalt-26.3.2-rc-20260908 @ 807558e5e81666af257c811e925e4cae570abc28:

=== RUN   TestTxnModeCreateLogicallyReplicated
    test_log_scope.go:172: test logs captured to: outputs.zip/logTestTxnModeCreateLogicallyReplicated414479952
    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.
    txnmode_test.go:700: Job 1211867007004704769 status: running
    utils.go:54: waiting for logical replication job 1211867007004704769 to reach replicated time of 1789902871.582351929,0
    utils.go:54: waiting for logical replication job 1211867007004704769 to reach replicated time of 1789902927.631687605,0

Parameters:

  • attempt=1
  • race=true
  • run=1
  • shard=4
Help

See also: How To Investigate a Go Test Failure (internal)

/cc @cockroachlabs/cdc

This test on roachdash | Improve this report!

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 the linked test report and captured logs, then inspect crosscluster/logical/txnmode/txnmode_test.go around TestTxnModeCreateLogicallyReplicated and line 700. Identify why the logical replication job remains running at the reported replicated times; done means the test completes successfully without the failure.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.