Exocet92andGitHub df13224efc bench: run on Linux only, and name the jobs for what they measure (#8) ...

Windows and macOS were carried on an argument that does not survive
examination. They were the only place in the whole chain that installed the
published wheel and ran it, which made this benchmark an install smoke test by
accident. That check is worth having, and worth forty seconds next to the build
in release.yml rather than thirteen minutes inside a performance measurement:
nobody reads a benchmark to find out whether a package imports. release.yml
already builds on all four targets, it just never executes what it built.

What is lost is a per-platform timing that was never quoted; the numbers that
get published are the Linux ones. Adding a platform back is one matrix entry.

The jobs are also named for what they measure rather than for the runner they
landed on, which the row already says: `backtests (ubuntu-latest)` and `grids
(ubuntu-latest)` instead of a raw label next to a hand-written one.

2026-08-20 17:08:43 +02:00

..

bench-vs-vectorbt.yml

bench: run on Linux only, and name the jobs for what they measure (#8)

2026-08-20 17:08:43 +02:00

ci.yml

ci: verify published package layout

2026-07-04 05:42:54 +02:00