ci: Exclude avm from Anchor downstream project tests
#4221
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem
CI tests for downstream projects include
avm(Anchor Version Manager), which doesn't depend on any Solana or SPL dependencies.avm's tests triggered a rate-limit error in CI, as mentioned in the #devops Discord channel.Although
avmtests only send 3 API requests in total, it still makes sense to skip those tests because they are completely unrelated to the goal of keeping Agave and Anchor compatible.Summary of changes
Exclude
avmfrom Anchor downstream project tests in CI.