We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Rel/nightly build started failing due to catch point test timeout failures.
Determine why the catch point test now takes longer than 10 seconds to advance to the next round (36 -> 37).
Medium
Output from failed test:
algod(29670) : Node running and accepting RPC requests over HTTP on port 127.0.0.1:41415. Press Ctrl-C to exit testingLogger.go:38: time="2021-06-03T01:46:30.640656 +0000" level=info msg="Second node catching up to round 1" file=catchpointCatchup_test.go function=github.com/[secure]/go-[secure]/test/e2e-go/features/catchup.TestBasicCatchpointCatchup line=201 testingLogger.go:38: time="2021-06-03T01:46:32.038616 +0000" level=info msg=" - done catching up!\n" file=catchpointCatchup_test.go function=github.com/[secure]/go-[secure]/test/e2e-go/features/catchup.TestBasicCatchpointCatchup line=211 testingLogger.go:38: time="2021-06-03T01:46:32.041614 +0000" level=info msg="primary node latest catchpoint - 36#WD6AJ46WCF26F5SR5SPFDWPVDS7Z23GUZN5FX4IUGBRCNRTQOSLA!\n" file=catchpointCatchup_test.go function=github.com/[secure]/go-[secure]/test/e2e-go/features/catchup.TestBasicCatchpointCatchup line=216 testingLogger.go:38: time="2021-06-03T01:46:32.044960 +0000" level=info msg="Second node catching up to round 36" file=catchpointCatchup_test.go function=github.com/[secure]/go-[secure]/test/e2e-go/features/catchup.TestBasicCatchpointCatchup line=221 fixture.go:105: Error Trace: catchpointCatchup_test.go:224 Error: Received unexpected error: timeout waiting for round 37 Test: TestBasicCatchpointCatchup --- FAIL: TestBasicCatchpointCatchup (51.30s)
The text was updated successfully, but these errors were encountered:
@algonautshant is investigating through #2239
Sorry, something went wrong.
No branches or pull requests
Summary
Rel/nightly build started failing due to catch point test timeout failures.
Scope/Requirements
Determine why the catch point test now takes longer than 10 seconds to advance to the next round (36 -> 37).
Urgency/Relative Priority
Medium
Notes
Output from failed test:
The text was updated successfully, but these errors were encountered: