Transaction Science
ebe9985a82
wai formal verification (integer core) / does this change touch it (pull_request) Successful in 9s
wai formal verification (integer core) / every harness in one shard (pull_request) Successful in 26s
wai formal verification (integer core) / kani (stage) (pull_request) Successful in 2m30s
wai formal verification (integer core) / kani (plan) (pull_request) Successful in 8m7s
wai formal verification (integer core) / kani (integer-core) (pull_request) Successful in 6m0s
wai formal verification (integer core) / kani (sound) (pull_request) Successful in 9m22s
wai formal verification (integer core) / kani (arith) (pull_request) Successful in 9m53s
wai formal verification (integer core) / kani (stage-long) (pull_request) Successful in 18m18s
wai formal verification (integer core) / kani (isqrt512) (pull_request) Successful in 29m45s
wai formal verification (integer core) / kani (rans64-t2) (pull_request) Successful in 13m41s
standards workspaces build + test / which workspaces this change touches (pull_request) Successful in 10s
standards workspaces build + test / macOS energy backends (pull_request) Has been skipped
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (pull_request) Successful in 3m42s
wai-formal-verification: the Kani cache would have overwritten the second macOS host's install ...
The move to `macos-proofs` left a condition behind. `Cache Kani toolchain` was
skipped by `matrix.os != 'macos'`, and the comment above it gives the reason:
those runners execute on the host, so `~` is the host's own home, where Kani is
already installed, and a restore writes over a live install.
`macos-proofs` is a second such host, and `!= 'macos'` is false for it, so the
step would have run there -- and `runner.os` is `macOS` on both, so the two hosts
would also have been sharing one cache key, each saving its own install over the
other's.
The test is now a prefix, `!startsWith(matrix.os, 'macos')`, which is what the
comment always meant.
Kani 0.67.0 is installed on that host: `cargo-kani 0.67.0`, with
`~/.kani/kani-0.67.0/bin/kani-driver`, `bin/cbmc` and `toolchain/bin/rustc` all
present, which is exactly the three-way test the `Install Kani` step skips on. So
the shards find a prover and do not fetch one.
Two things this run will also test that the last one could not, because it never
reached a step: the proofs host's own provisioning, and whether these harnesses
fit its 96 GB.
Co-Authored-By: Claude Opus 5 <[email protected] >
2026-11-03 11:20:39 -05:00
ci: thirteen WAI workflows run only when the pull request's own diff touches them
2026-10-14 03:41:49 -04:00
joule-moq-room: a bound on the clock's record store of a remote session, which ends the session
2026-10-26 10:43:13 -04:00
Bring wai mcp, wai setup-agent, Create and the room service's API into the catalogue, renamed to N3
2026-10-27 05:54:20 -04:00
Merge #493 (wai/messaging-calls @ 01f3aac1): wai.live.message and wai.live.call, conversations and calls on live rooms
2026-10-26 12:23:34 -04:00
ci: one run per branch at a time — no workflow declared a concurrency group
2026-10-05 12:01:57 -04:00
ci: gate on cargo-audit, so an advisory has to be read rather than accumulated
2026-10-22 12:49:04 -04:00
joulespec: applied to a standard that is not its own, which found a mis-aimed mutation
2026-11-02 04:27:13 -05:00
CI, the browser end-to-end and docs: Create under wai-app, wai create --from and wai dev
2026-10-27 05:14:19 -04:00
conformance-results: conform-result/1 in the standard, its corpus and a second verifier
2026-10-27 11:17:05 -04:00
int_mlicpp gate 2: the bundle decodes through wmb1/1 to its goldens
2026-10-15 21:44:10 -04:00
wai upscale and wai tonemap: an exact derivation from the command line, with its record and its check
2026-11-02 08:43:49 -05:00
wai upscale and wai tonemap: an exact derivation from the command line, with its record and its check
2026-11-02 08:43:49 -05:00
CI: the quantum set rerun test skipped on the linux leg until its path is left out
2026-10-30 00:33:34 -04:00
wai-examples.yml: the browser's path marked as the file path it is (allow-name)
2026-10-28 05:34:30 -04:00
wai.delivery.fleet in the registry, SPEC §5 and the changelog; the fleet's steps in CI
2026-10-27 15:39:52 -04:00
wai-formal-verification: the Kani cache would have overwritten the second macOS host's install
2026-11-03 11:20:39 -05:00
ci: run each suite for what can affect it; re-runs after a merge become nightly
2026-10-19 02:49:11 -04:00
wai: register key release, its CI steps, SPEC §5 and the changelog
2026-10-25 21:45:41 -04:00
receipt-ledger: tariff version 3 prices media jobs per operation and bills the work
2026-10-30 12:17:07 -04:00
ci: run each suite for what can affect it; re-runs after a merge become nightly
2026-10-19 02:49:11 -04:00
wai: D2c M7b gate 4: the networks against the direct networks, on random networks
2026-10-18 01:07:07 -04:00
ci: thirteen WAI workflows run only when the pull request's own diff touches them
2026-10-14 03:41:49 -04:00
route-record: second implementation, registration, CI; the catalogue's route.verify and package doors
2026-10-29 19:20:03 -04:00
wai-quantum: a model scored by the engine on a task set, and each answer counted in tokens four ways
2026-10-28 08:42:54 -04:00
wai-quantum-contract.yml: the baselines are the versions just published
2026-11-01 22:22:03 -05:00
wai-quantum CI: the CUDA and OpenCL hardware jobs on a second host, an aarch64 board (linux-arm64-hw)
2026-10-31 22:05:01 -04:00
wai-quantum-dataflow.yml: the instruction table's line matched anywhere in a line
2026-10-28 10:58:27 -04:00
wai-quantum-desktop: the update manifest served by the website, not a standing pre-release
2026-10-30 10:49:03 -04:00
wai-quantum: documentation that runs in CI, its drift fixed, an index of every page, and a changelog entry
2026-10-28 08:43:06 -04:00
CI: the editors' job in an image with glibc 2.39, the processor's library tests on their own features, the service smoke on the reader's table
2026-10-27 21:30:57 -04:00
wai/tools/wai-quantum-editor: the debugger, in the extension and the other editors
2026-10-27 23:44:27 -04:00
wai-quantum: resource estimation from programs, calibrated from the crate's own decoders
2026-10-27 23:44:27 -04:00
wai-quantum: other formats bounded against hostile input, in CI
2026-10-31 07:16:32 -04:00
wai-quantum: sparse Pauli dynamics on the GPU, with the CPU's term set, order and bits
2026-10-31 22:05:00 -04:00
wai-quantum for JavaScript: the engine as the npm package @transaction-science/wai-quantum 0.1.0
2026-10-29 08:14:24 -04:00
wai-quantum for JavaScript: the engine as the npm package @transaction-science/wai-quantum 0.1.0
2026-10-29 08:14:24 -04:00
wai quantum-conformance/qasm3: the OpenQASM 3 corpus, run natively, under wasm32-wasip2 and in the browser
2026-10-27 19:51:34 -04:00
wai-quantum: the members certified on the Mac Studio run on the Studio
2026-10-29 14:31:18 -04:00
ci: run each suite for what can affect it; re-runs after a merge become nightly
2026-10-19 02:49:11 -04:00
wai-quantum CI: the CUDA and OpenCL hardware jobs on a second host, an aarch64 board (linux-arm64-hw)
2026-10-31 22:05:01 -04:00
ci: run each suite for what can affect it; re-runs after a merge become nightly
2026-10-19 02:49:11 -04:00
wai-web, CI: pulse calls in the page, and the pulse layer's bits held on every platform
2026-10-30 12:05:14 -04:00
wai and wai-quantum release workflows: the x86_64 macOS legs on the Intel Mac (macos-x86_64)
2026-10-29 11:50:15 -04:00
wai-quantum-py: WAI Quantum in Python and notebooks, in-process
2026-10-27 19:51:08 -04:00
ci: error correction and mitigation, each new test required by name
2026-10-28 08:42:54 -04:00
wai-quantum-qpu.yml: the library has 46 tests, and the record's promises are named
2026-11-02 22:18:51 -05:00
wai-quantum engine::registry: methods, passes, noise channels and formats behind traits, the built-ins registered through them
2026-10-31 23:30:48 -04:00
wai-quantum-service smoke: paced within the client's window; the agent docs for pulse and other formats together
2026-10-31 07:16:32 -04:00
wai-quantum: the members certified on the Mac Studio run on the Studio
2026-10-29 14:31:18 -04:00
Quantum Studio: a job on your own hardware outlives the window
2026-11-02 22:19:02 -05:00
ci: run each suite for what can affect it; re-runs after a merge become nightly
2026-10-19 02:49:11 -04:00
ci: run each suite for what can affect it; re-runs after a merge become nightly
2026-10-19 02:49:11 -04:00
wai-quantum: the library's CI leg, its smoke checks, and an adder's reference with its inputs prepared
2026-10-31 09:48:42 -04:00
CI: the avx2 leg declares the units the runner's processor has
2026-10-26 11:36:49 -04:00
wai-quantum: the answer view layer, its codes and conformance set, and correctness records
2026-10-28 08:42:54 -04:00
wai-quantum: answers drawn as they arrive in the Studio, and a correctness record kept only when asked
2026-10-28 08:42:54 -04:00
wai-quantum CI: the WebGPU hardware job on the aarch64 board too (linux-arm64-hw)
2026-10-31 22:05:01 -04:00
wai and wai-quantum release workflows: the x86_64 macOS legs on the Intel Mac (macos-x86_64)
2026-10-29 11:50:15 -04:00
wai-sink-android: read a tool's output whole before searching it ( #488 )
2026-10-26 18:43:13 -04:00
wai-sink-swift: simulator tests hosted in TestHost, in a fresh simulator, every step bounded
2026-10-26 15:35:48 -04:00
wai-studio.yml: the macOS job named for the browsers it runs
2026-10-28 02:13:20 -04:00
wai-quantum: gradients, optimisation, VQE, QAOA and the algorithm builders on every surface
2026-10-31 09:48:42 -04:00
ebe9985a82