cockroachdb / cockroachdb/cockroach
basalt-26.3: sql/row: TestNextRowPartialColumnFamily failed
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
sql/row.TestNextRowPartialColumnFamily [failed](https://mesolite.cluster.engflow.com/invocations/default/c7dd1aa1-f0fb-44b7-8ab3-e0fe3c625b76?testReportRun=1&testReportShard=1&testReportAttempt=1#targets-Ly9wa2cvc3FsL3Jvdzpyb3dfdGVzdA==) on basalt-26.3 @ [1326f194d41c7a5187da0509cee33d331d2229de](https://github.com/cockroachdb/cockroach/commits/1326f194d41c7a5187da0509cee33d331d2229de):
```
=== RUN TestNextRowPartialColumnFamily
test_log_scope.go:172: test logs captured to: outputs.zip/logTestNextRowPartialColumnFamily1278784990
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)
```
Parameters:
- attempt=1
- race=true
- run=1
- shard=1
Help
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
Same failure on other branches
- #174151 sql/row: TestNextRowPartialColumnFamily failed [C-test-failure O-robot T-sql-queries branch-master release-blocker]
- #173404 sql/row: TestNextRowPartialColumnFamily failed [C-test-failure O-robot T-sql-queries branch-master]
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestNextRowPartialColumnFamily.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)
Jira issue: CRDB-67732
Contributor guide
Research direction
Start with sql/row.TestNextRowPartialColumnFamily at commit 1326f194d41c7a5187da0509cee33d331d2229de, using the linked test report and captured outputs.zip logs. Run the test with race=true and inspect test_server_shim.go as indicated by the failure output. Done means determining the cause of the repeated failure and making the test pass reliably across the affected branches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100