Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: update e2e upgrade workflow and test configuration #5388

Merged
merged 6 commits into from
Dec 13, 2023

Conversation

damiannolan
Copy link
Member

@damiannolan damiannolan commented Dec 12, 2023

Description

Now passing in CI with multi validator/node setup: https://github.com/cosmos/ibc-go/actions/runs/7183852859/job/19563569360


Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

  • Targeted PR against correct branch (see CONTRIBUTING.md).
  • Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
  • Code follows the module structure standards and Go style guide.
  • Wrote unit and integration tests.
  • Updated relevant documentation (docs/) or specification (x/<module>/spec/).
  • Added relevant godoc comments.
  • Provide a commit message to be used for the changelog entry in the PR description for review.
  • Re-reviewed Files changed in the Github PR explorer.
  • Review Codecov Report in the comment section below once CI passes.

Copy link
Contributor

@colin-axner colin-axner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for all the debugging work to get those green tests!!! 🍾 ❤️

@@ -28,7 +28,7 @@ import (
)

const (
haltHeight = uint64(350)
haltHeight = uint64(325)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

whoops, forgot to push 'start a review'

did you figure out why this height change was needed? mainly curious here on why its done 😅

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just dropped it lower because we were unnecessarily waiting for longer than we needed to. And the test runs long enough! :D

@damiannolan damiannolan merged commit 9c24bd2 into main Dec 13, 2023
74 checks passed
@damiannolan damiannolan deleted the damian/e2e-wasm-upgrade branch December 13, 2023 09:30
Comment on lines +102 to +107
var allNodes []testutil.ChainHeighter
for _, node := range chain.Nodes() {
allNodes = append(allNodes, node)
}

testutil.WaitForInSync(ctx, chain, allNodes...)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

curious as to why other tests weren't running into issues because of this 🤔

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same! I can add this snippet to the other upgrade tests as well, I see no reason why we shouldn't have it 🤷🏻‍♂️

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In practise node operators will set their halt height or just wait for a node to panic in the upgrade module requesting the new chain binary - so anything that reduces any room for out of sync nodes in the test is good imo!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants