Remove Windows CI from fbgemm_ci.yml to address OSS CI budget overage#5781
Closed
gchalump wants to merge 1 commit into
Closed
Remove Windows CI from fbgemm_ci.yml to address OSS CI budget overage#5781gchalump wants to merge 1 commit into
gchalump wants to merge 1 commit into
Conversation
Summary: X-link: facebookresearch/FBGEMM#2711 The `build-windows` job in `fbgemm_ci.yml` has been identified as the dominant remaining cost contributor to the FBGEMM OSS CI budget overage. Investigation summary (full details in T272989306): - Bisection by selective re-enable confirmed `fbgemm_ci.yml` is the bleed (fbgemm_gpu_ci_cuda.yml was never disabled and showed no spike). - `windows-2022` runners bill at ~10x Linux (~$3.84/hr vs ~$0.40/hr). - 2 windows jobs * ~40min * windows runner rate ≈ ~$5/PR. - macOS-13 jobs queue 24h and never run (deprecated runner pool) — not billing, tracked separately for follow-up. - D98427474 (Apr 3 GCC bump) added 2 ARM jobs/PR; small contribution (~$0.50/PR), not the visible driver. Decision: Remove the `build-windows` job entirely from both PR and main push triggers. Windows coverage was not validating critical functionality on PR. If needed later, re-add behind a label gate (e.g., `ci:windows`) or cron schedule. Differential Revision: D106405302
Contributor
|
@gchalump has exported this pull request. If you are a Meta employee, you can view the originating Diff in D106405302. |
Contributor
|
This pull request has been merged in 653d462. |
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
1 participant
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.
Summary:
X-link: https://github.com/facebookresearch/FBGEMM/pull/2711
The
build-windowsjob infbgemm_ci.ymlhas been identified as thedominant remaining cost contributor to the FBGEMM OSS CI budget overage.
Investigation summary (full details in T272989306):
fbgemm_ci.ymlis the bleed(fbgemm_gpu_ci_cuda.yml was never disabled and showed no spike).
windows-2022runners bill at10x Linux ($3.84/hr vs ~$0.40/hr).billing, tracked separately for follow-up.
(~$0.50/PR), not the visible driver.
Decision: Remove the
build-windowsjob entirely from both PR and mainpush triggers. Windows coverage was not validating critical functionality
on PR. If needed later, re-add behind a label gate (e.g.,
ci:windows)or cron schedule.
Differential Revision: D106405302