testplans: lotus-soup: use default WPoStChallengeWindow #6400
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is:
Updating
lotus-soupinitialisation to not scale down theWPoStChallengeWindow- this results in preseal sectors in the bootstrapper node to fail the minimum deal duration validation (see fix bootstrapper (genesis block generation) in lotus-soup #6379). Given that we don't test PoSt faults at the moment, we don't really need to scale this window down at this stage. As soon as we introduce tests for faults, we will need to decide how to speed up the tests - either by using a fake clock, or by reducing these windows.Updating the base and runtime docker images, that include the latest
filecoin-ffilib.Tests are passing at: https://ci.testground.ipfs.team/tasks#taskID_c2uu7gt5p7ae493pkipg