itests: support larger sector sizes; add large deal test. #7148
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
magik6k
reviewed
Aug 20, 2021
itests/kit/sectors.go
Outdated
|
|
||
| // EnableLargeSectors enables 512MiB sectors. This is useful in combination with | ||
| // mock proofs, for testing larger transfers. | ||
| func EnableLargeSectors() { |
There was a problem hiding this comment.
We should probably use t.Cleanup here to return the global policy state back to the default.
Stebalien
approved these changes
Aug 23, 2021
|
|
||
| dh := kit.NewDealHarness(t, client, miner, miner) | ||
|
|
||
| client.WaitTillChain(ctx, kit.HeightAtLeast(5)) |
There was a problem hiding this comment.
Do we need this? I don't think we need it anymore.
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.
Up until now, itests has been limited by the 2KiB sector size. It has been impractical to use larger sizes because we would go download the proof parameters, even if using mock proofs.
This PR:
MinerNodeOpt.Future
Now that we can perform deals with more interesting sizes, we should look into the following: