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

kv/kvserver.TestLoadQPSStats [failed](https://mesolite.cluster.engflow.com/invocations/default/36252f8d-8f49-40a2-b8b8-d6dd84ae76b7?testReportRun=2&testReportShard=31&testReportAttempt=1#targets-Ly9wa2cva3Yva3ZzZXJ2ZXI6a3ZzZXJ2ZXJfdGVzdA==) on basalt-26.3.2-rc-20260914 @ [d3eb08ebdd1dacc8d3dac0b107a7db5929e09969](https://github.com/cockroachdb/cockroach/commits/d3eb08ebdd1dacc8d3dac0b107a7db5929e09969):

```
=== RUN TestLoadQPSStats
test_log_scope.go:172: test logs captured to: outputs.zip/logTestLoadQPSStats3599563317
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
replica_rankings_test.go:420:
Error Trace: pkg/kv/kvserver/replica_rankings_test.go:420
Error: Not equal:
expected: 0
actual : 1
Test: TestLoadQPSStats
panic.go:694: -- test log scope end --
test logs left over in: outputs.zip/logTestLoadQPSStats3599563317
--- FAIL: TestLoadQPSStats (5.88s)
```

Parameters:
- attempt=1
- race=true
- run=2
- shard=31
Help

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

Same failure on other branches

- #175617 basalt-26.3.2-rc-20260916: kv/kvserver: TestLoadQPSStats failed [A-testing C-bug C-test-failure O-robot P-2 T-kv branch-basalt-26.3.2-rc-20260916]
- #174985 basalt-26.3.2-rc-20260908: kv/kvserver: TestLoadQPSStats failed [A-testing C-bug C-test-failure O-robot T-kv X-duplicate branch-basalt-26.3.2-rc-20260908]
- #174654 kv/kvserver: TestLoadQPSStats failed [A-testing C-bug C-test-failure O-robot T-kv branch-master]

/cc @cockroachlabs/kv-triage

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

Start with TestLoadQPSStats in pkg/kv/kvserver/replica_rankings_test.go, especially the assertion at line 420, and inspect the linked test report and captured logs. Reproduce the failure with the reported race-enabled configuration and trace why the expected value is 0 while the actual value is 1. Done means the underlying failure is explained and the test passes reliably on the affected branches.

Written by the indexing model from the issue text.