test: state-sync in e2e #1572
Closed
test: state-sync in e2e #1572
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
Codecov Report
@@ Coverage Diff @@
## main #1572 +/- ##
=======================================
Coverage 19.57% 19.57%
=======================================
Files 243 243
Lines 32299 32299
=======================================
Hits 6322 6322
Misses 24822 24822
Partials 1155 1155 Continue to review full report at Codecov.
|
mergify bot
pushed a commit
that referenced
this pull request
May 25, 2022
Closes: #XXX ## What is the purpose of the change Upgrade SDK with the app version change and set the app version in the upgrade handler ## Testing and Verifying - e2e test for state sync is in progress: #1572 - upgrade itself is verified by the existing e2e test - needs manual testing ## Documentation and Release Note - Does this pull request introduce a new feature or user-facing behavior changes? yes - Is a relevant changelog entry added to the `Unreleased` section in `CHANGELOG.md`? yes - How is the feature or change documented? not applicable
mergify bot
pushed a commit
that referenced
this pull request
May 25, 2022
Closes: #XXX ## What is the purpose of the change Upgrade SDK with the app version change and set the app version in the upgrade handler ## Testing and Verifying - e2e test for state sync is in progress: #1572 - upgrade itself is verified by the existing e2e test - needs manual testing ## Documentation and Release Note - Does this pull request introduce a new feature or user-facing behavior changes? yes - Is a relevant changelog entry added to the `Unreleased` section in `CHANGELOG.md`? yes - How is the feature or change documented? not applicable (cherry picked from commit 1510160) # Conflicts: # app/upgrades/v9/upgrades.go
p0mvn
added a commit
that referenced
this pull request
May 25, 2022
… (#1574) * chore: upgrade sdk with app version fix for state-sync (#1570) Closes: #XXX ## What is the purpose of the change Upgrade SDK with the app version change and set the app version in the upgrade handler ## Testing and Verifying - e2e test for state sync is in progress: #1572 - upgrade itself is verified by the existing e2e test - needs manual testing ## Documentation and Release Note - Does this pull request introduce a new feature or user-facing behavior changes? yes - Is a relevant changelog entry added to the `Unreleased` section in `CHANGELOG.md`? yes - How is the feature or change documented? not applicable (cherry picked from commit 1510160) # Conflicts: # app/upgrades/v9/upgrades.go * resolve conflicts Co-authored-by: Roman <roman@osmosis.team>
Closed
Closed
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.
Closes: #XXX
What is the purpose of the change
(E.g.: This pull request improves documation of area A by adding ....
Brief Changelog
(for example:)
Testing and Verifying
(Please pick one of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)
Documentation and Release Note
Unreleasedsection inCHANGELOG.md? (yes / no)x/<module>/spec/) / Osmosis docs repo / not documented)