| Filename | Latest commit message | Latest commit date |
|---|---|---|
4c66741c77
All checks were successful
wai-quantum qudit jobs / does this change touch it (push) Successful in 8s
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (push) Successful in 5m9s
WAI breaking changes and the conformance runner / WAI breaking · does this change touch WAI (push) Successful in 8s
wai-quantum qudit jobs / the module and the conformance set under wasm32-wasip2 (wasmtime) (push) Successful in 1m37s
wai-quantum qudit jobs / the module, the job, the conformance set, the referee and the verb · linux (push) Successful in 5m32s
WAI breaking changes and the conformance runner / WAI breaking · wire, record and API against main · linux (push) Successful in 1m13s
WAI breaking changes and the conformance runner / WAI breaking and conform · their tests, and the independent verifiers through wai conform · linux (push) Successful in 7m58s
wai-quantum qudit jobs / the same bits · macos (push) Successful in 2m36s
The clippy step stopped at exit 101 on the crate's own deny-level lints, far from the qudit files, before its grep for them ran: every lint is now capped at a warning, so clippy reads all of the crate and the step fails only where a lint names a qudit file (none does). Every other step of the leg had passed, the conformance set to results_blake3 a84eb125, as on arm64 macOS and wasm32-wasip2. quantum-sim.md §9.8 states the native figures of two runs on the shared build host (the largest job 9.6 s and 10.1 s) and says why the cheapest gates' times are noise. Co-Authored-By: Claude Opus 5.5 <[email protected]> |
||
| .. | ||
| wai-conformance | ||
| workflows | ||