cockroachdb / cockroachdb/cockroach
pkg/ccl/testccl/sqlccl/sqlccl_test: TestReadCommittedVolatileUDF failed
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
pkg/ccl/testccl/sqlccl/sqlccl_test.TestReadCommittedVolatileUDF [failed](https://mesolite.cluster.engflow.com/invocations/default/bf1b0237-f3fe-418b-b188-4352b5cbd52e?testReportRun=1&testReportShard=6&testReportAttempt=1#targets-Ly9wa2cvY2NsL3Rlc3RjY2wvc3FsY2NsOnNxbGNjbF90ZXN0) on master @ [dd7c17488b8195e0faf32209df0cbd5e298423ed](https://github.com/cockroachdb/cockroach/commits/dd7c17488b8195e0faf32209df0cbd5e298423ed):
```
=== RUN TestReadCommittedVolatileUDF
test_log_scope.go:172: test logs captured to: outputs.zip/logTestReadCommittedVolatileUDF780756407
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.
test_server_shim.go:637: DRPC is enabled (via testserver factory defaults)
read_committed_test.go:370:
Error Trace: pkg/ccl/testccl/sqlccl/read_committed_test.go:370
Error: Should be false
Test: TestReadCommittedVolatileUDF
panic.go:694: -- test log scope end --
test logs left over in: outputs.zip/logTestReadCommittedVolatileUDF780756407
--- FAIL: TestReadCommittedVolatileUDF (17.41s)
```
Parameters:
- attempt=1
- race=true
- run=1
- shard=6
Help
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
[Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)
Jira issue: CRDB-68387
Contributor guide
Research direction
Start with TestReadCommittedVolatileUDF in pkg/ccl/testccl/sqlccl/read_committed_test.go, especially the failing assertion at line 370. Reproduce the failure with the reported race configuration and inspect the captured outputs.zip logs for the test. Done means the test reliably passes with the expected false assertion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, sql
- Domain
- databases, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100