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.
To add the current memory from the cu for both testnet and devnet, you can run
yarn update-memory-fixtures
- these are not included by default because they are quite large (300mb+).This PR is setup to run with testnet memory - the current WASM binary used in the tests matches this memory and works.
If you attempt to run with devnet it will not work - this is likely because one memory is from a wasm64 module (testnet) and devnet is a wasm32 module.
Further testing would be required to identify if this is the issue, but also just as likely that simply being different modules make the memory incompatible (not just because they are different build types)
Further work:
If it is desired to have invariance testing with existing memory on both, simply add a network ENV var and conditionaly read the target AOS_WASM and existing memory fixtures.