-
Notifications
You must be signed in to change notification settings - Fork 662
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
Fix Wasm E2E Tests #6660
Fix Wasm E2E Tests #6660
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.
Approving, waiting for CI
when running tests locally with older images these tests pass. We'll need to decide how to proceed with this breaking change |
oh, this is a contract api breaking change 👀 |
An attempt was made. 733539c |
|
Can we merge this so I can run tests on #6644? or is there anything else left to do? |
@damiannolan think we can merge when ready, and can look into any failures after your PR gets merged after the fact |
* wip: fixing wasm tests * chore: fix wasm tests * chore: removed excess log lines --------- Co-authored-by: Damian Nolan <damiannolan@gmail.com>
Description
Marking as R4R to trigger E2Es.
This PR fixes the E2E wasm tests (with the exclusion of the MsgTransfer tests which fail due to ics20-v2)
The Setup logic is moved into SetupSuite and SetupTest, and the
ConfigureRelayer
fn is finally removed 🥳I added some additional log lines as debugging the hyperspace relayer was quite difficult due to it hanging rather than erroring.
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/
).godoc
comments.Files changed
in the GitHub PR explorer.SonarCloud Report
in the comment section below once CI passes.