cockroachdb / cockroachdb/cockroach

pkg/upgrade/upgrademanager/upgrademanager_test: TestPostJobInfoTableQueryDuplicateJobInfo failed

Open
#175,303 0 comments 0 reactions 0 assignees View on GitHub
branch-master C-test-failure O-robot release-blocker T-release
Dominant language
Go
Stars
32.5k
Forks
4.1k
PR merge metrics
PR metrics pending

Description

pkg/upgrade/upgrademanager/upgrademanager_test.TestPostJobInfoTableQueryDuplicateJobInfo [failed](https://mesolite.cluster.engflow.com/invocations/default/cd32df21-8143-4a6c-8ca3-f50ec6d19433?testReportRun=3&testReportShard=1&testReportAttempt=1#targets-Ly9wa2cvdXBncmFkZS91cGdyYWRlbWFuYWdlcjp1cGdyYWRlbWFuYWdlcl90ZXN0) on master @ [11498498a6837bce989898f7f06648a57215e9ce](https://github.com/cockroachdb/cockroach/commits/11498498a6837bce989898f7f06648a57215e9ce):

```
=== RUN TestPostJobInfoTableQueryDuplicateJobInfo
test_log_scope.go:172: test logs captured to: outputs.zip/logTestPostJobInfoTableQueryDuplicateJobInfo93582759
test_log_scope.go:82: use -show-logs to present logs inline
=== RUN TestPostJobInfoTableQueryDuplicateJobInfo/tenant
manager_external_test.go:330: setting cluster version to 1000026.3-upgrading-to-1000026.4-step-002
```

Parameters:
- attempt=1
- race=true
- run=3
- shard=1
Help

See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)

/cc @cockroachlabs/release-eng @cockroachlabs/release-eng

[Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)

Jira issue: CRDB-68332

Contributor guide

Open the contributing guide

Research direction

Start with pkg/upgrade/upgrademanager/upgrademanager_test.TestPostJobInfoTableQueryDuplicateJobInfo and the linked test report, including the captured logs. Reproduce the failure with race detection and determine why the tenant case stops after setting the cluster version; done means the test passes reliably on master.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.