cockroachdb / cockroachdb/cockroach

sql: TestTruncateTable failed

Open
#175,636 0 comments 0 reactions 0 assignees View on GitHub
branch-master C-test-failure O-robot release-blocker T-sql-foundations
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/21522803?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_UnitTests/21522803?buildTab=artifacts#/) on master @ [bfd5d19a59842a55a6acc9b9110e6795b1effff8](https://github.com/cockroachdb/cockroach/commits/bfd5d19a59842a55a6acc9b9110e6795b1effff8):

```
=== RUN TestTruncateTable
test_log_scope.go:172: test logs captured to: /artifacts/tmp/_tmp/004ac2cdb3e4dcce971cd33db6280729/logTestTruncateTable4148950692
test_log_scope.go:82: use -show-logs to present logs inline
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_3732252052.txt
panic.go:694: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/004ac2cdb3e4dcce971cd33db6280729/logTestTruncateTable4148950692
--- FAIL: TestTruncateTable (53.32s)
```
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-68508

Contributor guide

Open the contributing guide

Research direction

Start with sql.TestTruncateTable in multitenant_admin_function_test.go, especially the condition reported at lines 451 and 488. Review the linked TeamCity logs and artifacts to compare the expected descriptor path with the observed result on the ARM64 run. Done means the test completes without the 45-second condition failure and verifies the expected truncate result.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, sql
Domain
databases, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.