cockroachdb / cockroachdb/cockroach
basalt-26.3: sql/physicalplan: TestFakeSpanResolver failed
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
sql/physicalplan.TestFakeSpanResolver [failed](https://mesolite.cluster.engflow.com/invocations/default/d239d62a-5965-4976-9f91-d90c819f20c9?testReportRun=3&testReportShard=3&testReportAttempt=1#targets-Ly9wa2cvc3FsL3BoeXNpY2FscGxhbjpwaHlzaWNhbHBsYW5fdGVzdA==) on basalt-26.3 @ [017b84cd0101b832a6ee0c1934d073d108d0b24a](https://github.com/cockroachdb/cockroach/commits/017b84cd0101b832a6ee0c1934d073d108d0b24a):
```
=== RUN TestFakeSpanResolver
test_log_scope.go:172: test logs captured to: outputs.zip/logTestFakeSpanResolver2552466580
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.
testcluster.go:665: polling for queued jobs to complete: poll-show-jobs: session record deleted
panic.go:694: -- test log scope end --
test logs left over in: outputs.zip/logTestFakeSpanResolver2552466580
--- FAIL: TestFakeSpanResolver (1174.52s)
```
Parameters:
- attempt=1
- race=true
- run=3
- 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)
Jira issue: CRDB-68062
Contributor guide
Research direction
Start by reproducing sql/physicalplan.TestFakeSpanResolver with the reported race=true, run=3, and shard=3 parameters, then inspect the linked test report and captured logs. The failure ends while polling queued jobs because the session record was deleted; done means identifying the cause and making the test pass reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100