Reduce test jobs that run for pubnet and testnet #774
Merged
Conversation
This file contains hidden or 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
13 tasks
sagpatil
approved these changes
Sep 30, 2025
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.
What
Reduce test jobs that run for pubnet and testnet.
Why
The test jobs for pubnet and testnet are longer because they require syncing to public networks. This means they use more resources, make the overall build slower, and due to the external connectivity can fail sometimes slowing us down as we repeatedly try to rerun them. As long as we run all the variants of tests with the local network, there isn't as much value in running all the variants with pubnet and testnet. By running less variants of the tests we reduce random failures that often just affect one or two variants randomly.