cockroachdb / cockroachdb/cockroach

basalt-26.3.2-rc-20260916: kv/kvserver: TestDelegateSnapshot failed

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

Nobody has claimed this yet.

branch-basalt-26.3.2-rc-20260916 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.TestDelegateSnapshot failed on basalt-26.3.2-rc-20260916 @ 024cf0f74e8abea8b9fe2f4a05441dac7dc66c41:

=== RUN   TestDelegateSnapshot
    test_log_scope.go:172: test logs captured to: outputs.zip/logTestDelegateSnapshot1433223104
    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
    test_server_shim.go:639: DRPC is enabled (via testserver factory defaults)
    replica_learner_test.go:471: 
        	Error Trace:	pkg/kv/kvserver/replica_learner_test.go:471
        	Error:      	Not equal: 
        	            	expected: 4
        	            	actual  : 1
        	Test:       	TestDelegateSnapshot
        	Messages:   	Wrong type of request range_id:88 coordinator_replica:<node_id:1 store_id:1 replica_id:1 type:VOTER_FULL > recipient_replica:<node_id:2 store_id:2 replica_id:4 type:LEARNER > delegated_sender:<node_id:4 store_id:4 replica_id:3 type:VOTER_FULL > term:6 first_index:24 descriptor_generation:6 queue_on_delegate_len:3 snap_id:f35ee192-a5ca-480e-9e37-00dfa8dc15cd 
    panic.go:694: -- test log scope end --
test logs left over in: outputs.zip/logTestDelegateSnapshot1433223104
--- FAIL: TestDelegateSnapshot (34.17s)

Parameters:

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

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

Same failure on other branches

  • #173954 kv/kvserver: TestDelegateSnapshot failed [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 TestDelegateSnapshot in pkg/kv/kvserver/replica_learner_test.go, especially the failing assertion at line 471. Review the linked test report and captured logs, then reproduce the failure with the reported race-enabled settings. Done means identifying the cause, applying an appropriate fix, and getting TestDelegateSnapshot to pass.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.