cockroachdb / cockroachdb/cockroach

basalt-26.3: sql/physicalplan: TestFakeSpanResolver failed

Open
#174,785 2 comments 0 reactions 0 assignees View on GitHub
branch-basalt-26.3 C-test-failure O-robot T-sql-queries
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/f7fa05d2-f7ed-4423-b932-342e560e818b?testReportRun=2&testReportShard=3&testReportAttempt=1#targets-Ly9wa2cvc3FsL3BoeXNpY2FscGxhbjpwaHlzaWNhbHBsYW5fdGVzdA==) on basalt-26.3 @ [fafc66a354bc3374b5e38f8c3789047d52859fee](https://github.com/cockroachdb/cockroach/commits/fafc66a354bc3374b5e38f8c3789047d52859fee):

```
=== RUN TestFakeSpanResolver
test_log_scope.go:172: test logs captured to: outputs.zip/logTestFakeSpanResolver1214871156
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=2
- shard=3
Help

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

Same failure on other branches

- #172053 release-26.3: sql/physicalplan: TestFakeSpanResolver failed [C-test-failure O-robot T-sql-queries branch-release-26.3 target-release-26.4.0]

[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-67982

Contributor guide

Open the contributing guide

Research direction

Start with the linked test report for sql/physicalplan.TestFakeSpanResolver and read the comment at the top of test_server_shim.go, then consult the internal Go test failure investigation guide. Reproduce the failure with the reported race, run, and shard parameters. Done means the test passes on basalt-26.3 with race detection enabled and the underlying failure is addressed.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, sql
Domain
databases, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.