ci: run the Rust gates and tool self-tests through just #478

Merged

natsukium merged 1 commit from ci/gates-through-just into main 2026-09-26 11:47:17 +09:00

Conversation 0 Commits 1 Files changed 7 +40 -42

natsukium commented 2026-09-26 10:46:13 +09:00

Owner

Copy link

• pr.yml / release.yml build jobs and windows.yml windows-cross call just lint, just test, just deny, just check-portable, just check-windows instead of repeating the commands. The copies had drifted: just test carried --all-targets, CI did not.
• just test drops --all-targets so local and CI agree. The alternative, CI gaining it, would add bench/example links to the capacity-one nix runner; clippy already compiles every target and the nightly snapshot runs every bench. Say the word if you'd rather flip it the other way.
• New just selftest (prose_check, proto compat, release verify, both bench orchestrators) runs once in the build job; bench.yml's two copies of the orchestrator self-tests and proto-compat's own self-test step go. just check uses it, so the bench suites now run locally too.
• Required check names are unchanged.

- `pr.yml` / `release.yml` build jobs and `windows.yml` windows-cross call `just lint`, `just test`, `just deny`, `just check-portable`, `just check-windows` instead of repeating the commands. The copies had drifted: `just test` carried `--all-targets`, CI did not. - `just test` drops `--all-targets` so local and CI agree. The alternative, CI gaining it, would add bench/example links to the capacity-one nix runner; clippy already compiles every target and the nightly snapshot runs every bench. Say the word if you'd rather flip it the other way. - New `just selftest` (prose_check, proto compat, release verify, both bench orchestrators) runs once in the `build` job; bench.yml's two copies of the orchestrator self-tests and proto-compat's own self-test step go. `just check` uses it, so the bench suites now run locally too. - Required check names are unchanged.

natsukium added 1 commit 2026-09-26 10:46:13 +09:00

ci: run the Rust gates and tool self-tests through just ... bd3d69728e

pr.yml and release.yml spelled out the clippy, nextest, deny and wasm32
commands that the justfile also carries as `lint`, `test`, `deny` and
`check-portable`, with "(mirrors pr.yml)" comments as the only link
between the copies, and they had drifted: `just test` added
`--all-targets`, so the local gate ran the benches in test mode and CI
did not. CI now calls the recipes, as fuzz.yml, kani.yml and `just
test-gpu` already did. `just test` drops `--all-targets` rather than CI
gaining it: clippy already compiles every target, the nightly snapshot
runs every bench, and the extra link work would land on the
capacity-one nix runner that dominates PR latency.

The Python tools' self-tests were spread over three workflows: bench.yml
ran the bench orchestrators' suites twice and only on bench-relevant
paths, pr.yml ran compat's and verify's in two different jobs, and
`just check` ran neither bench suite. `just selftest` collects all five
and runs once in the build job.

Assisted-by: Claude Code

natsukium scheduled this pull request to auto merge when all checks succeed 2026-09-26 10:53:58 +09:00

natsukium merged commit a2a21373cd into main 2026-09-26 11:47:17 +09:00

natsukium deleted branch ci/gates-through-just 2026-09-26 11:47:17 +09:00

natsukium referenced this pull request from a commit 2026-09-26 11:47:18 +09:00

ci: run the Rust gates and tool self-tests through just (#478)

Commenting is not possible because the repository is archived.

Reviewers

No reviewers

Labels

Clear labels   

priority/P0

Must be resolved before the v0.1.0 tag

  

priority/P1

Must be settled before the first public contract freezes

  

priority/P2

Explicitly deferred until after v0.1.0

  

release/v0.1.0

Work tracked for the first tagged release

  

status/blocked

Cannot start now: waits on an upstream release, another issue, or a recorded revisit trigger

  

status/planned

Triaged with a source-grounded plan and a passed pi review; ready to implement

  

type/bug

Shipped behavior that contradicts the docs or the code's own intent; needs a product code change

  

type/design

An open scope or trade-off question; needs a recorded decision in the owning explanation doc before code

  

type/test-gap

Documented or reviewed behavior that no test pins; usually split from a review finding, needs no product code change

  

type/tracker

Parent issue that tracks child work

No labels

priority/P0

priority/P1

priority/P2

release/v0.1.0

status/blocked

status/planned

type/bug

type/design

type/test-gap

type/tracker

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

natsukium/felis!478

No description provided.