Files
vectorcraft/crates/pdf
dotCooCoo 49be5fb875 CI: the gate builds and runs the tests in five shards
The gate's one job builds all 106 test binaries on a 4-CPU, 16 GB runner,
and it is often stopped with exit code 143 ("The runner has received a
shutdown signal") during that build. ci.yml now runs the gate as five
legs:

- Shards 1 to 4 run `cargo xtask ci shard`, which builds and runs the
  tests and doctests of its own crates: ui-egui, engine, the apps with
  mcp and xtask, and every other crate.
- Shard 5 runs the other `cargo xtask ci` steps.
- On pushes to main, a `cache warm` leg runs `cargo xtask ci warm`,
  which builds what every shard builds and saves the dependency cache.

`gate (ubuntu-24.04)` passes only when all five legs passed.
`cargo xtask ci` with no argument runs every step, as before.

`cargo xtask shards` lists each shard's crates. It fails when a crate
named in xtask/src/shards.rs is not a workspace member or is named
twice, and when a crate builds with other features in its shard than in
`cargo test --workspace`. Every shard runs it first. vectorcraft-affinity
and vectorcraft-pdf now turn on `synth` and `read-count` in their own
dev-dependencies, which vectorcraft-engine's dev-dependencies turned on
before. Without that, 39 tests of affinity's `it` binary do not build in
a shard without the engine.

The gate also sets dev-debug "0" and dev-strip: true, so the workspace
crates build without line tables and the test binaries without debug
info or symbols.
2026-11-20 01:56:01 -08:00
..
2026-11-19 06:08:29 -08:00