Skip to content

docs: fix stale collect.rs module summary for in-shim extraction #48

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
cargo-affected-bot wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs: fix stale collect.rs module summary for in-shim extraction #48

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ee336a6
docs: fix stale collect.rs module summary for in-shim extraction
cargo-affected-bot Jun 5, 2026
2ffb4ab
Merge remote-tracking branch 'origin/main' into docs/collect-module-d…
cargo-affected-bot Jul 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions src/collect.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,11 +3,14 @@
//! Delegates build and test execution to `cargo nextest run`. We insert a
//! small runner shim (`cargo-affected runner-shim`) via
//! `--config target.<triple>.runner=[…]` that points `LLVM_PROFILE_FILE` at a
//! per-test subdirectory, runs the real test binary, and turns its profile
//! into line ranges on the spot. Each binary's function map — the expensive,
//! per-test subdirectory, then spawns and waits for the real test binary and
//! turns its profile into line ranges on the spot — merging profraws, joining
//! them against the binary's function map, and writing a small per-test result
//! file — before exiting. Each binary's function map — the expensive,
//! test-invariant half of that translation — is exported once, before the run.
//! After nextest finishes we read the per-test results back and write
//! per-(test, file) line ranges to SQLite.
//! After nextest finishes we read those per-test result files back and write
//! per-(test, file) line ranges to SQLite. See the Approach section below and
//! [`crate::shim`] for the in-shim extraction details.
//!
//! We use the `--config` array form rather than the
//! `CARGO_TARGET_<TRIPLE>_RUNNER` env var because cargo only
Expand Down
Loading