-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Introduce checkpoint itest #12755
Comments
@Kubuxu was the itest in there flaky? I see green ticks on the Checks for that PR and the itest seems reasonable (although maybe the last |
Yes, the itest in that PR is flaky, and both Steb and I spent 10+ hours trying to unflake it. |
@Kubuxu : what's the verdict on this? What test coverage are we missing not having this? From an "insist on high standards", should we get to the bottom of this? |
2025-01-24 conversation: we believe we should have this for nv25 because it isn't handled by passive testing because in passive testing none of finalization is consensus-impacting. |
Was attempted in #12659
Hits a weird bug in the mining loop.
The text was updated successfully, but these errors were encountered: