-
Notifications
You must be signed in to change notification settings - Fork 73
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
IF: Test failure: trx_finality_status_forked_if_test #2310
Comments
The logs for this look interesting. Need to dig into why |
IF: Test: trx_finality_status_forked_test
The log doesn't show a problem with IF I can seem The monotony check failures in node_03 are normals, as after the bridge is restored, we receive blocks from the other side which are earlier than the last block we voted on. However, the log show an issue (unrelated to IF work) where production is rescheduled too early after an error, causing repetitive log messages until the next block time is hit:
Issue #2380 was created to address this problem. |
https://github.com/AntelopeIO/leap/actions/runs/8270274635/job/22627758990?pr=2282#step:4:1738
The text was updated successfully, but these errors were encountered: