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

kv/kvserver/loqrecovery: TestRetrieveApplyStatus failed #98623

Closed
cockroach-teamcity opened this issue Mar 14, 2023 · 1 comment · Fixed by #101295
Closed

kv/kvserver/loqrecovery: TestRetrieveApplyStatus failed #98623

cockroach-teamcity opened this issue Mar 14, 2023 · 1 comment · Fixed by #101295
Assignees
Labels
branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot.
Milestone

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Mar 14, 2023

kv/kvserver/loqrecovery.TestRetrieveApplyStatus failed with artifacts on master @ 7f2afbcb1b7aef600fa3506649b9d3383a2f5bf9:

Fatal error:

panic: test timed out after 4m55s

Stack:

goroutine 245772 [running]:
testing.(*M).startAlarm.func1()
	GOROOT/src/testing/testing.go:2036 +0x88
created by time.goFunc
	GOROOT/src/time/sleep.go:176 +0x38
Log preceding fatal error

=== RUN   TestRetrieveApplyStatus
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/ea0927e04eade2740899effbae326bb2/logTestRetrieveApplyStatus4175440691
    test_log_scope.go:79: use -show-logs to present logs inline

Help

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

/cc @cockroachdb/replication

This test on roachdash | Improve this report!

Jira issue: CRDB-25371

@cockroach-teamcity cockroach-teamcity added branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. labels Mar 14, 2023
@cockroach-teamcity cockroach-teamcity added this to the 23.1 milestone Mar 14, 2023
@aliher1911
Copy link
Contributor

Looks like this test is suffering the same issue as current WIP startup retry.
WaitForFullReplication doesn't guarantee that system ranges get 5 replicas after it is called (as a part of startup or separately).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants