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.

Sign up for GitHub

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

Jump to bottom

kv/kvserver: TestRangefeedCheckpointsRecoverFromLeaseExpiration failed #124178

Open
cockroach-teamcity opened this issue May 14, 2024 · 5 comments
Open

kv/kvserver: TestRangefeedCheckpointsRecoverFromLeaseExpiration failed #124178

cockroach-teamcity opened this issue May 14, 2024 · 5 comments
Assignees
@andrewbaptist
Labels
branch-release-24.1 Used to mark GA and release blockers and technical advisories for 24.1 C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. 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. skipped-test T-kv-replication KV Replication Team X-duplicate Closed as a duplicate of another issue.
Milestone
24.1

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented May 14, 2024 •
edited by cockroach-jira-scripts

kv/kvserver.TestRangefeedCheckpointsRecoverFromLeaseExpiration failed with artifacts on release-24.1 @ 556680db129ea635342767fdd916628409071ef1:

=== RUN   TestRangefeedCheckpointsRecoverFromLeaseExpiration
    test_log_scope.go:170: test logs captured to: /artifacts/tmp/_tmp/37ddc8e37e5448832e32de57f39c38ec/logTestRangefeedCheckpointsRecoverFromLeaseExpiration544955870
    test_log_scope.go:81: use -show-logs to present logs inline
    replica_rangefeed_test.go:1517: 
        	Error Trace:	github.com/cockroachdb/cockroach/pkg/kv/kvserver_test/pkg/kv/kvserver/replica_rangefeed_test.go:1517
        	Error:      	Received unexpected error:
        	            	liveness record changed while incrementing epoch for liveness(nid:2 epo:1 exp:1715719335.242344971,0); actual is liveness(nid:2 epo:1 exp:1715719334.132890321,0); is the node still live?
        	            	(1) liveness record changed while incrementing epoch for liveness(nid:2 epo:1 exp:1715719335.242344971,0); actual is liveness(nid:2 epo:1 exp:1715719334.132890321,0); is the node still live?
        	            	Error types: (1) *liveness.ErrEpochCondFailed
        	Test:       	TestRangefeedCheckpointsRecoverFromLeaseExpiration
    panic.go:626: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/37ddc8e37e5448832e32de57f39c38ec/logTestRangefeedCheckpointsRecoverFromLeaseExpiration544955870
--- FAIL: TestRangefeedCheckpointsRecoverFromLeaseExpiration (1.64s)
Help

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

Same failure on other branches

/cc @cockroachdb/replication

This test on roachdash | Improve this report!

Jira issue: CRDB-38746
@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-kv-replication KV Replication Team labels May 14, 2024
@cockroach-teamcity cockroach-teamcity added this to the 24.1 milestone May 14, 2024
@cockroach-teamcity
Copy link
Member Author

kv/kvserver.TestRangefeedCheckpointsRecoverFromLeaseExpiration failed with artifacts on release-24.1 @ a3f808338f097ce9f2b183ad65311a96d8fa5766:

=== RUN   TestRangefeedCheckpointsRecoverFromLeaseExpiration
    test_log_scope.go:170: test logs captured to: /artifacts/tmp/_tmp/37ddc8e37e5448832e32de57f39c38ec/logTestRangefeedCheckpointsRecoverFromLeaseExpiration3693211046
    test_log_scope.go:81: use -show-logs to present logs inline
    replica_rangefeed_test.go:1517: 
        	Error Trace:	github.com/cockroachdb/cockroach/pkg/kv/kvserver_test/pkg/kv/kvserver/replica_rangefeed_test.go:1517
        	Error:      	Received unexpected error:
        	            	liveness record changed while incrementing epoch for liveness(nid:2 epo:1 exp:1715719915.062259685,0); actual is liveness(nid:2 epo:1 exp:1715719913.950302220,0); is the node still live?
        	            	(1) liveness record changed while incrementing epoch for liveness(nid:2 epo:1 exp:1715719915.062259685,0); actual is liveness(nid:2 epo:1 exp:1715719913.950302220,0); is the node still live?
        	            	Error types: (1) *liveness.ErrEpochCondFailed
        	Test:       	TestRangefeedCheckpointsRecoverFromLeaseExpiration
    panic.go:626: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/37ddc8e37e5448832e32de57f39c38ec/logTestRangefeedCheckpointsRecoverFromLeaseExpiration3693211046
--- FAIL: TestRangefeedCheckpointsRecoverFromLeaseExpiration (1.66s)
Help

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

Same failure on other branches

This test on roachdash | Improve this report!

@cockroach-teamcity
Copy link
Member Author

kv/kvserver.TestRangefeedCheckpointsRecoverFromLeaseExpiration failed on release-24.1 @ 6e68cb2b3a4fb7f02cfafcccc5f81d6356de171e:

=== RUN   TestRangefeedCheckpointsRecoverFromLeaseExpiration
    test_log_scope.go:170: test logs captured to: outputs.zip/logTestRangefeedCheckpointsRecoverFromLeaseExpiration460166722
    test_log_scope.go:81: use -show-logs to present logs inline
    replica_rangefeed_test.go:1517: 
        	Error Trace:	github.com/cockroachdb/cockroach/pkg/kv/kvserver_test/pkg/kv/kvserver/replica_rangefeed_test.go:1517
        	Error:      	Received unexpected error:
        	            	liveness record changed while incrementing epoch for liveness(nid:2 epo:1 exp:1715758759.283332402,0); actual is liveness(nid:2 epo:1 exp:1715758758.182541957,0); is the node still live?
        	            	(1) liveness record changed while incrementing epoch for liveness(nid:2 epo:1 exp:1715758759.283332402,0); actual is liveness(nid:2 epo:1 exp:1715758758.182541957,0); is the node still live?
        	            	Error types: (1) *liveness.ErrEpochCondFailed
        	Test:       	TestRangefeedCheckpointsRecoverFromLeaseExpiration
    panic.go:626: -- test log scope end --
test logs left over in: outputs.zip/logTestRangefeedCheckpointsRecoverFromLeaseExpiration460166722
--- FAIL: TestRangefeedCheckpointsRecoverFromLeaseExpiration (1.63s)

Parameters:

  • attempt=1
  • run=17
  • shard=1
Help

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

Same failure on other branches

This test on roachdash | Improve this report!

@cockroach-teamcity
Copy link
Member Author

kv/kvserver.TestRangefeedCheckpointsRecoverFromLeaseExpiration failed with artifacts on release-24.1 @ 28735b05c5a8caae045a92939a5dc233d0c3915f:

=== RUN   TestRangefeedCheckpointsRecoverFromLeaseExpiration
    test_log_scope.go:170: test logs captured to: /artifacts/tmp/_tmp/37ddc8e37e5448832e32de57f39c38ec/logTestRangefeedCheckpointsRecoverFromLeaseExpiration2079952082
    test_log_scope.go:81: use -show-logs to present logs inline
    replica_rangefeed_test.go:1517: 
        	Error Trace:	github.com/cockroachdb/cockroach/pkg/kv/kvserver_test/pkg/kv/kvserver/replica_rangefeed_test.go:1517
        	Error:      	Received unexpected error:
        	            	liveness record changed while incrementing epoch for liveness(nid:2 epo:1 exp:1715768670.279313075,0); actual is liveness(nid:2 epo:1 exp:1715768669.115703473,0); is the node still live?
        	            	(1) liveness record changed while incrementing epoch for liveness(nid:2 epo:1 exp:1715768670.279313075,0); actual is liveness(nid:2 epo:1 exp:1715768669.115703473,0); is the node still live?
        	            	Error types: (1) *liveness.ErrEpochCondFailed
        	Test:       	TestRangefeedCheckpointsRecoverFromLeaseExpiration
    panic.go:626: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/37ddc8e37e5448832e32de57f39c38ec/logTestRangefeedCheckpointsRecoverFromLeaseExpiration2079952082
--- FAIL: TestRangefeedCheckpointsRecoverFromLeaseExpiration (1.99s)
Help

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

Same failure on other branches

This test on roachdash | Improve this report!

@cockroach-teamcity
Copy link
Member Author

kv/kvserver.TestRangefeedCheckpointsRecoverFromLeaseExpiration failed on release-24.1 @ 6e68cb2b3a4fb7f02cfafcccc5f81d6356de171e:

=== RUN   TestRangefeedCheckpointsRecoverFromLeaseExpiration
    test_log_scope.go:170: test logs captured to: outputs.zip/logTestRangefeedCheckpointsRecoverFromLeaseExpiration3831727626
    test_log_scope.go:81: use -show-logs to present logs inline
    replica_rangefeed_test.go:1517: 
        	Error Trace:	github.com/cockroachdb/cockroach/pkg/kv/kvserver_test/pkg/kv/kvserver/replica_rangefeed_test.go:1517
        	Error:      	Received unexpected error:
        	            	liveness record changed while incrementing epoch for liveness(nid:2 epo:1 exp:1715770804.597098206,0); actual is liveness(nid:2 epo:1 exp:1715770802.133394759,0); is the node still live?
        	            	(1) liveness record changed while incrementing epoch for liveness(nid:2 epo:1 exp:1715770804.597098206,0); actual is liveness(nid:2 epo:1 exp:1715770802.133394759,0); is the node still live?
        	            	Error types: (1) *liveness.ErrEpochCondFailed
        	Test:       	TestRangefeedCheckpointsRecoverFromLeaseExpiration
    panic.go:626: -- test log scope end --
test logs left over in: outputs.zip/logTestRangefeedCheckpointsRecoverFromLeaseExpiration3831727626
--- FAIL: TestRangefeedCheckpointsRecoverFromLeaseExpiration (5.66s)

Parameters:

  • attempt=1
  • race=true
  • run=1
  • shard=1
Help

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

Same failure on other branches

This test on roachdash | Improve this report!

@pav-kv pav-kv mentioned this issue May 15, 2024
Merged
@pav-kv
Copy link
Collaborator

pav-kv commented May 15, 2024

Dup of #123551 which was skipped in #123752.

Skipping in 24.1 too: #124209.

@pav-kv pav-kv added C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. skipped-test X-duplicate Closed as a duplicate of another issue. labels May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@andrewbaptist andrewbaptist

Labels
branch-release-24.1 Used to mark GA and release blockers and technical advisories for 24.1 C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. 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. skipped-test T-kv-replication KV Replication Team X-duplicate Closed as a duplicate of another issue.
Projects
None yet
Milestone
24.1
Development

No branches or pull requests
3 participants
@pav-kv @cockroach-teamcity @andrewbaptist