ci: reduce repeated validation spend - #342
Merged
Merged
Conversation
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
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.
Repeated pushes and merge events currently rerun the full paid WarpBuild matrix, including work already validated on the pull request. This change keeps cross-platform PR coverage while making post-merge validation substantially cheaper and cancelling superseded work.
The workflow now selects paid coverage by event: code PRs retain Ubuntu, macOS, and Windows; documentation-only PRs skip paid tests; pushes use one Ubuntu 8x smoke runner; and manual runs can request either scope. A stable
CI Gatevalidates the expected success or skip result for every terminal job. Clippy is reduced to one Ubuntu job on code PRs and manual runs, with post-merge and docs-only Clippy skipped.The PR also adds a confirmation-gated runner-sizing benchmark, an importable
mainruleset recipe, policy regression tests, and a rollout runbook covering WarpBuild budgets and monitoring.How to Test
Plan validationon this PR and confirm it selectsfull; verify one Ubuntu 8x, one macOS 12x, and one Windows 32x test job run andCI Gatepasses.python3 -m unittest tests.test_ci_policy tests.test_doctest_packages tests.test_test_performance; expect all policy and helper tests to pass, including docs-only and post-merge skip behavior..github/workflows/ci.ymland.github/workflows/runner-sizing.yml; expect both workflows to validate.gate_errorstest from its expected success or skip value and confirm the aggregate gate test fails.