Skip to content

ccl/backupccl: TestScheduleChainingLifecycle failed #91640

@cockroach-teamcity

Description

@cockroach-teamcity

ccl/backupccl.TestScheduleChainingLifecycle failed with artifacts on release-22.2 @ 9a72dc474bd00f1f28089ac217794015dd351190:

=== CONT  TestScheduleChainingLifecycle
    schedule_pts_chaining_test.go:212: -- test log scope end --
test logs left over in: /go/src/github.com/cockroachdb/cockroach/artifacts/logTestScheduleChainingLifecycle316076359
--- FAIL: TestScheduleChainingLifecycle (4.39s)
=== RUN   TestScheduleChainingLifecycle/cluster
    schedule_pts_chaining_test.go:80: 
        	Error Trace:	/go/src/github.com/cockroachdb/cockroach/pkg/ccl/backupccl/schedule_pts_chaining_test.go:80
        	            				/go/src/github.com/cockroachdb/cockroach/pkg/ccl/backupccl/db.go:975
        	            				/go/src/github.com/cockroachdb/cockroach/pkg/ccl/backupccl/txn.go:961
        	            				/go/src/github.com/cockroachdb/cockroach/pkg/ccl/backupccl/db.go:974
        	            				/go/src/github.com/cockroachdb/cockroach/pkg/ccl/backupccl/db.go:937
        	            				/go/src/github.com/cockroachdb/cockroach/pkg/ccl/backupccl/db.go:916
        	            				/go/src/github.com/cockroachdb/cockroach/pkg/ccl/backupccl/schedule_pts_chaining_test.go:77
        	            				/go/src/github.com/cockroachdb/cockroach/pkg/ccl/backupccl/schedule_pts_chaining_test.go:178
        	Error:      	Received unexpected error:
        	            	protected timestamp record does not exist
        	            	(1) attached stack trace
        	            	  -- stack trace:
        	            	  | github.com/cockroachdb/cockroach/pkg/kv/kvserver/protectedts.init
        	            	  | 	/go/src/github.com/cockroachdb/cockroach/pkg/kv/kvserver/protectedts/protectedts.go:31
        	            	  | runtime.doInit
        	            	  | 	/usr/local/go/src/runtime/proc.go:6321
        	            	  | runtime.doInit
        	            	  | 	/usr/local/go/src/runtime/proc.go:6298
        	            	  | runtime.doInit
        	            	  | 	/usr/local/go/src/runtime/proc.go:6298
        	            	  | runtime.doInit
        	            	  | 	/usr/local/go/src/runtime/proc.go:6298
        	            	  | runtime.doInit
        	            	  | 	/usr/local/go/src/runtime/proc.go:6298
        	            	  | runtime.doInit
        	            	  | 	/usr/local/go/src/runtime/proc.go:6298
        	            	  | runtime.doInit
        	            	  | 	/usr/local/go/src/runtime/proc.go:6298
        	            	  | runtime.doInit
        	            	  | 	/usr/local/go/src/runtime/proc.go:6298
        	            	  | runtime.doInit
        	            	  | 	/usr/local/go/src/runtime/proc.go:6298
        	            	  | runtime.doInit
        	            	  | 	/usr/local/go/src/runtime/proc.go:6298
        	            	  | runtime.doInit
        	            	  | 	/usr/local/go/src/runtime/proc.go:6298
        	            	  | runtime.main
        	            	  | 	/usr/local/go/src/runtime/proc.go:233
        	            	  | runtime.goexit
        	            	  | 	/usr/local/go/src/runtime/asm_amd64.s:1594
        	            	Wraps: (2) protected timestamp record does not exist
        	            	Error types: (1) *withstack.withStack (2) *errutil.leafError
        	Test:       	TestScheduleChainingLifecycle/cluster
    --- FAIL: TestScheduleChainingLifecycle/cluster (1.10s)

Parameters: GOFLAGS=-json

Help

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

/cc @cockroachdb/disaster-recovery

This test on roachdash | Improve this report!

Jira issue: CRDB-21357

Epic CRDB-21942

Metadata

Metadata

Assignees

Labels

C-test-failureBroken test (automatically or manually discovered).O-robotOriginated from a bot.T-disaster-recoverybranch-release-22.2Used to mark GA and release blockers, technical advisories, and bugs for 22.2

Type

No type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions