Open
Conversation
furtib
force-pushed
the
github_ci_billing_optimize
branch
from
f623901 to
6f183ff
Compare
furtib
force-pushed
the
github_ci_billing_optimize
branch
from
c21be68 to
46d7de0
Compare
Szelethus
reviewed
Feb 3, 2026
Contributor
Szelethus
left a comment
Szelethus
left a comment
There was a problem hiding this comment.
We really need to know what our budget is. I'll try to find out ASAP. If it's generous enough, saving those two minutes might be justifiable.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Why:
We use an unnecessarily large amount of minutes in GitHub Actions.
This happens because billing rounds up to a whole minute, so setup actions (like setup unit/foss) cost a minute instead of 2 seconds. Also, since we run multiple machines, we pay for the environment setup for each (~1 minute for each machine).
Cost in #181: (complete CI run in 6 minutes, cost: 38 minutes, ~8 minutes environment setup)
Running sequentially: complete CI: ~8 minutes, cost: 25 minutes (~4 minute environment setup)
Reorganizing jobs to be run sequentially saves us: ~13 minutes in billed minutes (for every PR), and loses us ~3 minutes in waiting for CI to finish.
Unit tests are usually ~2 minutes long, while FOSS tests are usually ~4 minutes long.
This means that while the current CI setup will stay 6 minutes long, even with Bazel 8, the sequential run will be ~12 minutes in length. (Expected increase in billed minutes: current: +18, optimized: +12, saved: 19 minutes)
What:
Addresses:
none