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

ci: allow flaky interchaintest to rerun. #1034

Conversation

tuantran1702
Copy link
Contributor

@tuantran1702 tuantran1702 commented Jul 7, 2024

Description

Update Github actions to attempt failed interchaintest tests for max 2 times so that CI pass in case of flakiness.

@tuantran1702 tuantran1702 marked this pull request as ready for review July 8, 2024 02:49
@tuantran1702 tuantran1702 marked this pull request as draft July 8, 2024 02:49
@tuantran1702 tuantran1702 changed the title ci ci: allow flaky interchaintest to rerun. Jul 8, 2024
@tuantran1702 tuantran1702 marked this pull request as ready for review July 8, 2024 03:38
@faddat
Copy link
Contributor

faddat commented Jul 8, 2024

dude :D

@faddat faddat mentioned this pull request Jul 8, 2024
@dimiandre
Copy link
Member

thanks for the pr, accepting it for now.

In the future we need to either fix interchaintest or switch to something else

@dimiandre dimiandre merged commit 61632fe into CosmosContracts:dimi/v23-upgrade-handler Jul 8, 2024
20 checks passed
@tuantran1702 tuantran1702 deleted the dimi/v23-upgrade-handler branch July 8, 2024 05:56
dimiandre added a commit that referenced this pull request Jul 9, 2024
* basic upgrade handler for v23

* remove icq from store upgrades

* migrate icq params in upgrade handler

* builder module account conversion

* port back tf patch from mainnet with a better implementation

* lint

* refuse in tf update

* core1 vesting migration

* lint

* lint 2

* remove uneccessary consensus params migration

* ci: allow flaky interchaintest to rerun. (#1034)

* ci

* test

* test2

* test3

---------

Co-authored-by: Tuan Tran <[email protected]>
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.

3 participants