Add CI check that runs unit tests #39
Merged
+107
−1
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
syjn99
force-pushed
the
ci/unit-tests
branch
from
13f1a90 to
3427093
Compare
syjn99
force-pushed
the
ci/unit-tests
branch
from
3f32111 to
d8b4271
Compare
sb-anderson
approved these changes
Nov 27, 2024
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.
Adding CI job running unit tests for every PR. Leveraging #30 for better build performance.
As bazel server needs heavy environment, it is hard to run all unit tests at one instance hosted by Github. (Default storage: 14GB) It was found that
//config/...needs a lot of disk space, so I decided to separate all packages and run tests parellel.BuildBuddy or Buildkite can be an alternative for this issue as it provides dedicated instance and optimization for bazel.