Repository navigation
docs: add the nextest fast profile and the dist-profile g07 bench note - #241
Merged
Merged
Conversation
The inner loop repeats the same slow suites; a nextest `fast` profile skips only the integration suites measured at ~40 s or more of serial time each, while the unfiltered default profile and CI keep running everything. docs/development.md documents the runner and the two-loop workflow, and the G07 note says how to reproduce its numbers now that packaged builds use the `dist` profile. Co-Authored-By: Claude Code <[email protected]>
axisrow
commented
Oct 25, 2026
axisrow
left a comment
axisrow
left a comment
Collaborator
Author
There was a problem hiding this comment.
PR #241 - nextest fast profile + dist-profile g07 note - APPROVED
Checked against base master (3a259c1):
- All 11 suite names in the fast profile
default-filterexist as integration-test targets at the head commit:export_ifc,numbering_approval,numbering,libraries,environments,pickunderapps/beamcraft-cli/tests;recovery,revision,compactionundercrates/host/tests;g09_budget_fuzz,g05_profile_extrusionundercrates/kernel/tests. .config/nextest.tomlis the documented nextest config location; the triple-quoted TOML literal and the filter DSL syntax are valid, and newlines/indentation inside the filter are fine.- CI (
.github/workflows/ci.yml) runs unfiltered nextest pluscargo test --workspace --doc, so the claims that the default profile and CI run everything, and that doctests are the one nextest exception, are accurate. - The g07 note matches the root
Cargo.toml:dist= opt-level 3, thin LTO, one codegen unit;--release= 16 codegen units, LTO off;crates/kernel/examples/g07_bench.rsexists, so the reproduce command is correct.
No change requested. Two optional notes, body only: (1) the doc says installing cargo-nextest gives the same version CI uses, but CI pins 0.9.149 while cargo install cargo-nextest fetches the latest - consider wording it as the same runner, not version; (2) README.md and CLAUDE.md still show cargo test --workspace as the canonical command - still true and docs/development.md bridges it explicitly, fine to keep this PR focused.
Blogbotana
approved these changes
Oct 25, 2026
axisrow
referenced
this pull request
in axisrow/BeamCraft
Oct 25, 2026
Upstream merged the placement rotation (#243) and the nextest profile (#241), so the placement commit this branch carried collapses into master and the branch's own diff is the auto-refresh feature alone. The app.rs add/add resolves to this branch's side: the same placement changes plus the watcher. Co-Authored-By: Claude Code <[email protected]>
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
Bring the nextest workflow and one documentation correction from the fork's daily-driver setup:
.config/nextest.toml: afastprofile for the local inner loop that skips only theintegration suites measured at ~40 s or more of serial time each (cli
export_ifc,numbering_approval,numbering,libraries,environments,pick; hostrecovery,revision,compaction; kernelg09_budget_fuzz,g05_profile_extrusion).The unfiltered
defaultprofile and CI keep running everything, so nothing is removedor permanently skipped.
docs/development.md: document cargo nextest as the local runner, the inner-loop vspre-merge-gate commands, and the doctest exception.
docs/design/g07-kernel-first-scope-acceptance.md: note that the recorded numbers are nowreproduced with
cargo run --profile dist -p beamcraft-kernel --example g07_bench, sincepackaged builds moved to the
distprofile.The suite baselines were measured on the reference Apple M5 (2026-10-25).
Tests
cargo fmt --checkpasses locally;the CI triple covers the rest.
Notes
were dropped for upstream context.
🤖 Generated with Claude Code
Issue tracking
Fixes #393