5996b03abb
Some checks failed
wai-det-jpegai WAISM float-level module of record / does this change touch it (push) Successful in 38s
wai-det-jpegai WAISM float-level module of record / linux · both checkers, F1, F2 on wasmtime (Cranelift, Winch, Pulley) and Wasmi, the planted faults (push) Has been cancelled
wai-det-jpegai WAISM float-level module of record / linux-arm64 · both checkers, F1, F2 on wasmtime (Cranelift, Winch, Pulley) and Wasmi, the planted faults (push) Has been cancelled
WAI breaking changes and the conformance runner / WAI breaking · does this change touch WAI (push) Has been cancelled
WAI breaking changes and the conformance runner / WAI breaking · wire, record and API against main · linux (push) Has been cancelled
WAI breaking changes and the conformance runner / WAI breaking and conform · their tests, and the independent verifiers through wai conform · linux (push) Has been cancelled
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (push) Has been cancelled
The JPEG AI exact decoder at WAISM's float level follows the decoder's new scope (D74): the module corpus (corpus.py) adds every configuration vector over the jpegai/v1 bundle, each in scope to the native exact decoder's pinned RGB8, the two the reference leaves to the machine to the refusal configuration_undetermined, and each the decoder does not implement to the sink's module_trap, which the host now lets a case expect. The module of record (record/) is rebuilt from this tree on Linux x86_64 (673,221 bytes, fdef6d19...); both checkers hold it at the float level and refuse it R3 at the integer level. The workflow runs every case on Cranelift and Winch and the jpegai/v1 cases on the two interpreters, which take minutes a configuration vector; the README records every case on all four. Co-Authored-By: Claude Opus 5.5 <[email protected]>
657 KiB
Executable file
657 KiB
Executable file