cockroachdb / cockroachdb/cockroach

basalt-26.3.2-rc-20260914: kv/kvserver: TestStoreRangeMergeSplitRace_MergeWins failed

Open
#175,668 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

branch-basalt-26.3.2-rc-20260914 C-test-failure O-robot release-blocker T-kv
Dominant language
Go
Stars
32.5k
Forks
4.1k
PR merge metrics
PR metrics pending

Description

kv/kvserver.TestStoreRangeMergeSplitRace_MergeWins failed on basalt-26.3.2-rc-20260914 @ d3eb08ebdd1dacc8d3dac0b107a7db5929e09969:

=== RUN   TestStoreRangeMergeSplitRace_MergeWins
    test_log_scope.go:172: test logs captured to: outputs.zip/logTestStoreRangeMergeSplitRace_MergeWins2143839408
    test_log_scope.go:82: use -show-logs to present logs inline
    test_server_shim.go:146: using test tenant configuration from testserver factory defaults
    client_merge_test.go:1655: merge failed: checking RHS manifest before merge: descriptor generation mismatch: expected 2, found 3
    panic.go:694: -- test log scope end --
test logs left over in: outputs.zip/logTestStoreRangeMergeSplitRace_MergeWins2143839408
--- FAIL: TestStoreRangeMergeSplitRace_MergeWins (5.49s)

Parameters:

  • attempt=1
  • race=true
  • run=3
  • shard=13
Help

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

Same failure on other branches

  • #175616 basalt-26.3.2-rc-20260916: kv/kvserver: TestStoreRangeMergeSplitRace_MergeWins failed [C-test-failure O-robot T-kv branch-basalt-26.3.2-rc-20260916 release-blocker]
  • #175040 basalt-26.3: kv/kvserver: TestStoreRangeMergeSplitRace_MergeWins failed [C-test-failure O-robot P-3 T-kv X-duplicate branch-basalt-26.3]
  • #174984 basalt-26.3.2-rc-20260908: kv/kvserver: TestStoreRangeMergeSplitRace_MergeWins failed [C-test-failure O-robot P-3 T-kv X-duplicate branch-basalt-26.3.2-rc-20260908]
  • #174777 kv/kvserver: TestStoreRangeMergeSplitRace_MergeWins failed [A-testing C-bug C-test-failure O-robot P-3 T-kv branch-master]

/cc @cockroachlabs/kv-triage

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 kv/kvserver's TestStoreRangeMergeSplitRace_MergeWins and the failure at client_merge_test.go:1655. Inspect the captured test logs in outputs.zip/logTestStoreRangeMergeSplitRace_MergeWins2143839408 and compare the repeated failures linked in the issue. Done means the test no longer fails with the descriptor generation mismatch.

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
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.