Move "Bazel Test" GitHub action to a large runner. #4119
Closed
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
![copybara-service[bot]](https://avatars.githubusercontent.com/in/44061?s=60&v=4){kind=small}
copybara-service
bot
force-pushed
the
test_578232997
branch
16 times, most recently
from
6d63c03 to
01bd4b2
Compare
copybara-service
bot
changed the title
local_test_jobs.
copybara-service
bot
force-pushed
the
test_578232997
branch
2 times, most recently
from
426492d to
bcff98c
Compare
copybara-service
bot
changed the title
copybara-service
bot
force-pushed
the
test_578232997
branch
2 times, most recently
from
9538e16 to
fde4828
Compare
"Bazel Test" has been the bottleneck of our builds for a while now. A large part of that is due to the default GitHub runner only having 2 cores and thus only being able to run at most 2 Bazel actions at a time. Things have also gotten worse due to the increasing number of tests in Dagger's codebase and the slowing down of tests due to the move to XProcessing Testing and possibly increased I/O due to golden files, though these issues aren't addressed in this CL. This CL moves our "Bazel Test" GitHub actions onto the large test runner. This runner now has 16 cores which should allow 8x more tests to run in parallel and we should see a similar improvement in the time it takes these GitHub actions to run. RELNOTES=N/A PiperOrigin-RevId: 578232997
copybara-service
bot
force-pushed
the
test_578232997
branch
from
fde4828 to
492f8dd
Compare
copybara-service
bot
force-pushed
the
test_578232997
branch
from
492f8dd to
221fc86
Compare
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.
Move "Bazel Test" GitHub action to a large runner.
"Bazel Test" has been the bottleneck of our builds for a while now. A large part of that is due to the default GitHub runner only having 2 cores and thus only being able to run at most 2 Bazel actions at a time. Things have also gotten worse due to the increasing number of tests in Dagger's codebase and the slowing down of tests due to the move to XProcessing Testing and possibly increased I/O due to golden files, though these issues aren't addressed in this CL.
This CL moves our "Bazel Test" GitHub actions onto the large test runner. This runner now has 16 cores which should allow 8x more tests to run in parallel and we should see a similar improvement in the time it takes these GitHub actions to run.
RELNOTES=N/A