| Filename | Latest commit message | Latest commit date |
|---|---|---|
a3d46b352a
All checks were successful
standards workspaces build + test / which workspaces this change touches (pull_request) Successful in 7s
standards workspaces build + test / macOS energy backends (pull_request) Has been skipped
WAI energy receipts / does this change touch it (pull_request) Successful in 6s
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (pull_request) Successful in 2m36s
WAI energy receipts / energy receipts · macos (pull_request) Successful in 8m27s
WAI energy receipts / energy receipts · linux (pull_request) Successful in 9m9s
WAI energy receipts / energy receipts · linux-arm64 (pull_request) Successful in 9m23s
engine::sets' rerun test compares each item between two runs, less its elapsed_ms and receipt, but with its Merkle path. A path holds the other items' leaves, and with them their elapsed_ms, so on the slower x86_64 runners (jetson-hub, the iMac VM) two runs differ there: three failures in three runs on #540 and #541, none of them in code those PRs touch. #538 holds the fix (the path left out) and waits on the Windows runner, which is offline; any change under wai/wai-quantum waits with it. So the energy-receipts linux leg skips that one test while sets.rs still compares the path, and runs it whole again by itself once the file leaves the path out. linux-arm64 and macOS run it whole throughout. Co-Authored-By: Claude Opus 5.5 <[email protected]> |
||
| .. | ||
| workflows | ||