Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ccl/backupccl: TestRestoreRetryProcErr failed #121337

Open
cockroach-teamcity opened this issue Mar 29, 2024 · 0 comments
Open

ccl/backupccl: TestRestoreRetryProcErr failed #121337

cockroach-teamcity opened this issue Mar 29, 2024 · 0 comments
Labels
branch-release-24.1 Used to mark GA and release blockers and technical advisories for 24.1 C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. P-2 Issues/test failures with a fix SLA of 3 months T-disaster-recovery
Milestone

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Mar 29, 2024

ccl/backupccl.TestRestoreRetryProcErr failed on release-24.1 @ 557f4e6fe89d683d49082d88ba5adf6660e8f16f:

=== RUN   TestRestoreRetryProcErr
    test_log_scope.go:170: test logs captured to: outputs.zip/logTestRestoreRetryProcErr1555202584
    test_log_scope.go:81: use -show-logs to present logs inline
    backup_test.go:1638: -- test log scope end --
test logs left over in: outputs.zip/logTestRestoreRetryProcErr1555202584
--- FAIL: TestRestoreRetryProcErr (6.00s)
=== RUN   TestRestoreRetryProcErr/restore_processor_progress=true
    test_server_shim.go:157: automatically injected an external process virtual cluster under test; see comment at top of test_server_shim.go for details.
    backup_test.go:1636: 
        	Error Trace:	github.com/cockroachdb/cockroach/pkg/ccl/backupccl/backup_test.go:1636
        	            				github.com/cockroachdb/cockroach/pkg/testutils/subtest.go:28
        	Error:      	Not equal: 
        	            	expected: 1
        	            	actual  : 2
        	Test:       	TestRestoreRetryProcErr/restore_processor_progress=true
    testutils.go:289: no Invalid Descriptors
    --- FAIL: TestRestoreRetryProcErr/restore_processor_progress=true (3.04s)

Parameters:

  • attempt=1
  • run=30
  • shard=34
Help

See also: How To Investigate a Go Test Failure (internal)

Same failure on other branches

/cc @cockroachdb/disaster-recovery

This test on roachdash | Improve this report!

Jira issue: CRDB-37195

@cockroach-teamcity cockroach-teamcity added branch-release-24.1 Used to mark GA and release blockers and technical advisories for 24.1 C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-disaster-recovery labels Mar 29, 2024
@cockroach-teamcity cockroach-teamcity added this to the 24.1 milestone Mar 29, 2024
@msbutler msbutler removed the release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. label Apr 2, 2024
@msbutler msbutler added the P-2 Issues/test failures with a fix SLA of 3 months label Apr 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch-release-24.1 Used to mark GA and release blockers and technical advisories for 24.1 C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. P-2 Issues/test failures with a fix SLA of 3 months T-disaster-recovery
Development

No branches or pull requests

2 participants