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.
The following gets all containers running and relevant tests passing with the exception of
That is because those images require instructions sets that are not supported by Rosetta2 (likely AVX). As far as I can tell, pre-built binaries or images do not exist for linux/arm64, but they could potentially be built, akin to what I did for
solana-test-validator
.This was tested with 8 CPU / 24 GB memory under Docker resources with the command
tilt up -- --ci --num=2 --m1 --near=false --aptos=false --sui=false
. Fair warning it took nearly 2 hours, but that was with rebuilding nearly all of the images.Everything should succeed except
sdk-ci-tests
query-sdk-ci-tests
Solana queries testingrentEpoch
- the arm64solana-test-validator
is a different version than the old one. a future PR may attempt to make them the same version (likely updating the amd64 version used, better yet to use the same image)Additionally, this modifies the
sdk-ci-tests
to setmaxWorkers=50%
and exposes a tilt parameter. While in some instances, this may lead to performance improvements due to reusing workers, this is done here in an effort to save resources. In my benchmarking, the process was consuming up to 16GB of memory (and competing for resources) with the existing default workers, while--maxWorkers=1
only required 4GB. Here's the test times from CI a run.The longest test is
wormhole_relayer.ts
at 407s while the rest of the tests cumulatively are about 780s. Yet, here are the results from a few test runs. [default] [50%] [1]