[RunAllTests] Use faster Bazel setup with 4.0 LTS #2693
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
Switch to previously approved Bazel setup action.
Switch back to uses: abhinavsingh/setup-bazel@v3 for setup. The one we used previously doesn't seem to work currently with 4.0: jwlawson/actions-setup-bazel#11
|
Ah nice. This is much faster: compute affected targets took ~18s instead of the ~1.5 minutes from before. There will still be a slight delay from cloning the custom tools repo, but it should still be a nice improvement over what the previous setup was doing. |
jcqli
approved these changes
Feb 12, 2021
|
Thanks! Looks like another JVM crash in CI. :( Restarting failing tests & enabling auto-merge. |
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.
This is a follow-up from #1904.
This is meant to speed up Bazel in CI by using a much leaner repository containing custom Bazel setup (just the Android tools from https://github.com/oppia/oppia-bazel-tools versus cloning the much larger oppia/bazel repository). This is expected to shave up to 30 seconds off each test action requiring Bazel (depending on how long the Bazel setup action itself takes).