Repository navigation
Conversation
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>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
dblock
force-pushed
the
dblock/ci-no-debuginfo
branch
from
November 19, 2026 15:09
df71a25 to
794fac0
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.
Disable debug information in CI's development and test profiles, including nested fixture and driver builds. This adapts the debug-info reduction from dylint-spellcheck #35; Dylint already builds lint libraries in release mode, so that PR's exact coverage-library change is unnecessary here.
Optimization levels and debug assertions are unchanged.
opt-level=3is deliberately not copied: it increased fresh build time in the local comparison below. Developer builds outside CI and the separate coverage workflow are unchanged. The tradeoff is less source-line detail in CI backtraces; #2186's dependency cache automatically keys on these Cargo environment settings.Local Build Comparison
Real
dylint_driverlibrary builds on Apple Silicon usingnightly-2026-08-20, identical source, separate empty target directories, warm downloaded dependencies, andCARGO_INCREMENTAL=0. One observation per configuration; target-file sizes are logical file bytes, not compressed cache sizes or a full-CI benchmark.debug=0(this PR)debug=0,opt-level=3(not applied)Debug removal reduced build time by 18.7% and target-file bytes by 39.6% in this sample. Actual hosted-CI gains remain unmeasured.
Validation
With both profile settings enabled: four focused integration tests passed, including generated-library build/test variants, custom build directories/linker copying, direct driver execution, and source-change invalidation. The three planner/ShellCheck tests, strict workspace custom lints, actionlint, and Prettier also passed.
Based on #2186. This is a logical stack targeting upstream
master, as before; fork heads cannot use native GitHub stacks. This layer's diff.Authored by an AI acting on behalf of @dblock.