basalt-26.3.2-rc-20260908: sql/physicalplan: TestFakeSpanResolver failed

sql/physicalplan.TestFakeSpanResolver [failed](https://mesolite.cluster.engflow.com/invocations/default/8e093717-3329-4dab-8a28-3ae7ce8b0293?testReportRun=1&testReportShard=3&testReportAttempt=1#targets-Ly9wa2cvc3FsL3BoeXNpY2FscGxhbjpwaHlzaWNhbHBsYW5fdGVzdA==) on basalt-26.3.2-rc-20260908 @ [807558e5e81666af257c811e925e4cae570abc28](https://github.com/cockroachdb/cockroach/commits/807558e5e81666af257c811e925e4cae570abc28):

```
=== RUN TestFakeSpanResolver
test_log_scope.go:172: test logs captured to: outputs.zip/logTestFakeSpanResolver1198109089
test_log_scope.go:82: use -show-logs to present logs inline
test_server_shim.go:168: automatically injected an external process virtual cluster under test; see comment at top of test_server_shim.go for details.
```

Parameters:
- attempt=1
- race=true
- run=1
- shard=3
Help

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

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

Start with sql/physicalplan.TestFakeSpanResolver and inspect the linked test report, captured logs, and commit 807558e5e81666af257c811e925e4cae570abc28. Reproduce the failure with the reported race, run, and shard parameters, then trace the failure in the physical plan test. Done means the test passes reliably under the reported configuration and the underlying cause is addressed.

Written by the indexing model from the issue text.