cockroachdb / cockroachdb/cockroach
basalt-26.3.2-rc-20260916: sql/tests: TestSplitAtTableBoundary failed
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
sql/tests.TestSplitAtTableBoundary [failed](https://mesolite.cluster.engflow.com/invocations/default/9f7a7420-cbb9-454a-8939-99ee51e4cf97?testReportRun=1&testReportShard=16&testReportAttempt=1#targets-Ly9wa2cvc3FsL3Rlc3RzOnRlc3RzX3Rlc3Q=) on basalt-26.3.2-rc-20260916 @ [20b5b7762461dc7d59206ab797cd12d09c877eaa](https://github.com/cockroachdb/cockroach/commits/20b5b7762461dc7d59206ab797cd12d09c877eaa):
```
=== RUN TestSplitAtTableBoundary
test_log_scope.go:172: test logs captured to: outputs.zip/logTestSplitAtTableBoundary863634628
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:639: DRPC is enabled (via testserver factory defaults)
table_split_test.go:53: condition failed to evaluate within 3m45s: from table_split_test.go:60: expected range start key /Tenant/10/Table/109; got /Tenant/10/Table/84
goroutine dump: /mnt/engflow/worker/work/0/exec/bazel-out/k8-fastbuild/testlogs/pkg/sql/tests/tests_test/shard_16_of_16_run_1_of_3/test.outputs/goroutine_dump_3635551376.txt
panic.go:694: -- test log scope end --
test logs left over in: outputs.zip/logTestSplitAtTableBoundary863634628
--- FAIL: TestSplitAtTableBoundary (1551.01s)
```
Parameters:
- attempt=1
- race=true
- run=1
- shard=16
Help
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
Same failure on other branches
- #175509 basalt-26.3.2-rc-20260914: sql/tests: TestSplitAtTableBoundary failed [C-test-failure O-robot T-sql-queries branch-basalt-26.3.2-rc-20260914 release-blocker]
- #175422 basalt-26.3.2-rc-20260913: sql/tests: TestSplitAtTableBoundary failed [OOM] [C-test-failure O-robot T-sql-queries branch-basalt-26.3.2-rc-20260913]
- #174997 basalt-26.3.2-rc-20260908: sql/tests: TestSplitAtTableBoundary failed [OOM] [C-test-failure O-robot T-sql-queries branch-basalt-26.3.2-rc-20260908]
- #174915 basalt-26.3.2-rc-20260908: sql/tests: TestSplitAtTableBoundary failed [C-test-failure O-robot T-sql-queries branch-basalt-26.3.2-rc-20260908]
- #174818 release-26.3: sql/tests: TestSplitAtTableBoundary failed [C-test-failure O-robot T-sql-queries branch-release-26.3]
- #174815 release-26.2: sql/tests: TestSplitAtTableBoundary failed [OOM] [C-test-failure O-robot T-sql-queries branch-release-26.2]
- #174697 basalt-26.3: sql/tests: TestSplitAtTableBoundary failed [C-test-failure O-robot T-sql-queries branch-basalt-26.3]
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestSplitAtTableBoundary.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)
Contributor guide
Research direction
Start with pkg/sql/tests/table_split_test.go, especially the failure at lines 53 and 60, and run TestSplitAtTableBoundary with the race configuration. Inspect the linked test report, captured logs, and goroutine dump to determine why the expected range start key differs from the observed key. Done means the underlying failure is addressed and the test passes reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, sql
- Domain
- databases, distributed-systems, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100