Repository navigation
Conversation
dblock
force-pushed
the
dblock/ci-setup
branch
2 times, most recently
from
November 18, 2026 13:02
fd81d86 to
8ad76c5
Compare
Plan explicit matrix entries from the PR or merge-group base commit before allocating test runners. Preserve regular platform coverage and full expensive suites on relevant changes, schedules, and manual runs. Fail the required gate if planning fails. Install formatting, CI, and scheduled-check tools only for suites that use them. Consolidate Rustup updates while retaining common toolchain preinstallation and disk cleanup. Test event selection, deleted and renamed paths, and invalid bases. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
dblock
force-pushed
the
dblock/ci-setup
branch
from
November 19, 2026 15:09
8ad76c5 to
0d3cedf
Compare
This branch has not been deployed
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.
Summary
Select CI suites before allocating test runners. Ordinary PRs retain all ten regular matrix entries without starting the twelve expensive jobs that previously installed tools, cleaned disks, and fetched dependencies before exiting without running tests. Changes under
expensive/, scheduled runs, and manual runs retain the full expensive matrix. Merge-queue selection uses the merge group's base SHA.Restrict setup to the suites that need it: install cargo-hack, cargo-udeps, Prettier, and the cargo-rdme compatibility toolchain only for the CI suite; install nightly rustfmt for CI and example-formatting tests; install supply-chain tools only when scheduled checks will run. Replace the broad Rustup update with a stable-only update and leave nightly installation to the existing toolchain-preinstallation helper.
Keep the actual test commands, all three host platforms, dependency caches, disk cleanup, and preinstallation needed to avoid concurrent Rustup operations. Include planner failures in the final required-check gate.
Validation
Passed locally: actionlint, the existing ShellCheck test, formatting, workspace custom lints with all features/tests, and planner regressions covering PRs, merge groups, scheduled/manual runs, deleted/renamed paths, and invalid or unavailable base commits.
Timing Comparison
Both runs completed successfully: before, unchanged workflow, and after, this PR at
8ad76c5.Observed reductions: 107m 10s (24.1%) in summed job elapsed time, 3m 04s (4.1%) in retained-job setup, and 4m 54s (6.5%) in workflow elapsed time. The new planner took seven seconds. The twelve removed jobs previously spent only six seconds combined in their final
Teststeps; the rest was setup and job overhead.Summed job times are elapsed durations, not OS-weighted billing minutes. Setup is the sum of completed step durations preceding
Test; workflow elapsed time runs from workflow creation through the last job's completion. The overall job and workflow totals include the new planner.This is one observational pair, not a controlled benchmark: the baseline is #2179, which also adds four integration tests absent from this independent, master-based PR, and runner/cache conditions vary. Do not attribute all test-runtime differences to these workflow changes. The structural saving is avoiding twelve testless jobs. Long-running tests remain the critical path: the after-run Windows CLI job took 69m 46s, including 59m 51s in its unchanged
Teststep.Hosted CI passed all ten selected platform/suite jobs, the planner, and the final gate.
AI-authored on behalf of @dblock.