cockroachdb / cockroachdb/cockroach
sql: TestTruncateTable failed
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
sql.TestTruncateTable [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_UnitTests/21522861?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_UnitTests/21522861?buildTab=artifacts#/) on master @ [96b96b3f5f6aa83a847cd2609ed21649289f7082](https://github.com/cockroachdb/cockroach/commits/96b96b3f5f6aa83a847cd2609ed21649289f7082):
```
=== RUN TestTruncateTable
test_log_scope.go:172: test logs captured to: /artifacts/tmp/_tmp/004ac2cdb3e4dcce971cd33db6280729/logTestTruncateTable1275205784
test_log_scope.go:82: use -show-logs to present logs inline
test_server_shim.go:637: DRPC is enabled (via testserver factory defaults)
multitenant_admin_function_test.go:451: condition failed to evaluate within 45s: from multitenant_admin_function_test.go:488: expected "" to be contained in result "" tenant=system row=0 col=0
goroutine dump: /artifacts/tmp/_tmp/004ac2cdb3e4dcce971cd33db6280729/goroutine_dump_3374114112.txt
panic.go:694: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/004ac2cdb3e4dcce971cd33db6280729/logTestTruncateTable1275205784
--- FAIL: TestTruncateTable (51.74s)
```
Help
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
/cc @cockroachlabs/sql-foundations
[Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)
Jira issue: CRDB-68512
Contributor guide
Research direction
Start with TestTruncateTable and the failure condition in multitenant_admin_function_test.go around lines 451 and 488. Reproduce the test using the linked CI log and artifacts, then determine why the observed table descriptor differs from the expected value. Done means the test passes reliably on the affected configuration with appropriate regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100