test: upgrading ibc/network vats at many points in protocol #8948
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
- use contracts in net/ibc upgrade test
For testing upgrades while an operation is pending (i.e., before it is `dequeue`d)
Serializing them causes them to appear on the console, which is very misleading
|
the relevant parts of this got merged |
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.
refs: #8867
Description
Following the upgrade-at-each-point-in-a-flow test pattern, test upgrade at various points in an network/ibc vat flow.
Security / Scaling / Documentation Considerations
n/a
Testing / Upgrade Considerations
This is an upgrade test.