fix: handle PoXAnchorBlockRequired in boot_to_epoch_25_reward_cycle#6992
Conversation
Signed-off-by: Jacinta Ferrant <236437600+jacinta-stacks@users.noreply.github.com>
Codecov Report✅ All modified and coverable lines are covered by tests. ❌ Your project status has failed because the head coverage (60.09%) is below the adjusted base coverage (84.96%). You can increase the head coverage or adjust the Removed Code Behavior.
Additional details and impacted files@@ Coverage Diff @@
## develop #6992 +/- ##
============================================
- Coverage 84.96% 60.09% -24.87%
============================================
Files 412 412
Lines 219958 219958
Branches 338 338
============================================
- Hits 186883 132182 -54701
- Misses 33075 87776 +54701 see 313 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Fixes failing
tests::signer::v0::multiple_miners_mock_sign_epoch_25. Similar problem was identified and fixed inboot_to_epoch_3. The test was panicking becauseget_reward_set_signers()returns a400 PoXAnchorBlockRequirederror when the prepare phase anchor block hasn't been determined yet. The original code used.expect()on this result, causing a hard failure on a transient condition. (Gives coordinator time to catch up)