Depends on GH#40 (cargo profiles for dev/test/release/bench). Once [profile.dev/test/release/bench] are defined in Cargo.toml, wire CI to actually exercise them so a profile regression (e.g. someone reverting a setting, or a profile silently falling back to defaults) is caught automatically instead of only surfacing locally.
Scope
- CI job builds with
cargo build (dev) and cargo build --release (release) and confirms both succeed.
- CI job runs
cargo test under the test profile and cargo bench --no-run (or full cargo bench if fast enough) under the bench profile.
- Fail CI if a profile is removed/misconfigured (e.g. assert expected
opt-level/lto via a lightweight check, or just rely on the build/bench commands succeeding under the intended profile).
Exit criteria
- New/updated CI workflow step(s) covering all four profiles.
- CI green on the branch that introduces this.
Depends on GH#40 (cargo profiles for dev/test/release/bench). Once
[profile.dev/test/release/bench]are defined inCargo.toml, wire CI to actually exercise them so a profile regression (e.g. someone reverting a setting, or a profile silently falling back to defaults) is caught automatically instead of only surfacing locally.Scope
cargo build(dev) andcargo build --release(release) and confirms both succeed.cargo testunder thetestprofile andcargo bench --no-run(or fullcargo benchif fast enough) under thebenchprofile.opt-level/ltovia a lightweight check, or just rely on the build/bench commands succeeding under the intended profile).Exit criteria