-
Notifications
You must be signed in to change notification settings - Fork 619
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
Conversation
There was a problem hiding this 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) |
There was a problem hiding this comment.
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 😅
There was a problem hiding this comment.
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
var allNodes []testutil.ChainHeighter | ||
for _, node := range chain.Nodes() { | ||
allNodes = append(allNodes, node) | ||
} | ||
|
||
testutil.WaitForInSync(ctx, chain, allNodes...) |
There was a problem hiding this comment.
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 🤔
There was a problem hiding this comment.
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 🤷🏻♂️
There was a problem hiding this comment.
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!
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.
docs/
) or specification (x/<module>/spec/
).godoc
comments.Files changed
in the Github PR explorer.Codecov Report
in the comment section below once CI passes.