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

kv/kvserver.TestLoadQPSStats [failed](https://mesolite.cluster.engflow.com/invocations/default/6d298377-987e-4619-be53-5ce590e72dc3?testReportRun=3&testReportShard=31&testReportAttempt=1#targets-Ly9wa2cva3Yva3ZzZXJ2ZXI6a3ZzZXJ2ZXJfdGVzdA==) on basalt-26.3.2-rc-20260916 @ [20b5b7762461dc7d59206ab797cd12d09c877eaa](https://github.com/cockroachdb/cockroach/commits/20b5b7762461dc7d59206ab797cd12d09c877eaa):

```
=== RUN TestLoadQPSStats
test_log_scope.go:172: test logs captured to: outputs.zip/logTestLoadQPSStats1200273122
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/logTestLoadQPSStats1200273122
--- FAIL: TestLoadQPSStats (5.31s)
```

Parameters:
- attempt=1
- race=true
- run=3
- 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

- #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 and the assertion at pkg/kv/kvserver/replica_rankings_test.go:420, then review the linked test report and compare the same failure in issues #174985 and #174654. Reproduce the failure with the reported race configuration and determine why the expected value is 0 while the actual value is 1. Done means the test passes reliably under the affected configuration.

Written by the indexing model from the issue text.