open-standards/wai/wai-int-module/browser
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Transaction Science cb453c3d50
Some checks failed
WAI breaking changes and the conformance runner / WAI breaking · does this change touch WAI (push) Successful in 6s
wai-int-module WAISM module of record / does this change touch it (push) Successful in 11s
wai-int-module WAISM module of record / the module of record in Chromium (push) Successful in 18s
WAI breaking changes and the conformance runner / WAI breaking · wire, record and API against main · linux (push) Successful in 1m56s
WAI breaking changes and the conformance runner / WAI breaking and conform · their tests, and the independent verifiers through wai conform · linux (push) Successful in 5m15s
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (push) Failing after 2m17s
wai-int-module WAISM module of record / linux · both checkers, wasmtime (Cranelift, Winch), Wasmi and Node (push) Successful in 7m36s
wai-int-module WAISM module of record / linux-arm64 · both checkers, wasmtime (Cranelift, Winch), Wasmi and Node (push) Successful in 6m59s
wai-int-module: the browser run ends when the page goes silent, with the browser's last words
On f5bb6842a the module of record in Chromium sat silent for 30 minutes after the browser's
--version line, and the job's timeout ended it with nothing said; the same commit's scheduled run,
on the same runner, passed in 3 seconds, and the run as CI makes it (the job's container, its
first process tail, each step through docker exec, /dev/shm 64 MB) passes in 6 to 7 seconds on
that host, so the stall is not the code's and was not reproduced. run-browser.mjs waited for the
overall bound (the limit for every case of every module, 20 hours here) and printed nothing
before it. The page holds each case to the limit and then sends it as timed out, so a page that
asks for nothing and sends nothing for longer than the limit and a minute has stopped: the run
now ends there, exit 1, saying how many results came back, with the browser's stderr.

Checked in the job's image on the Linux x86_64 runner's host: every case of both modules of
record, 120 of 120 each, one run digest; and a planted page that never starts its job, with
--limit 5, ended by the watchdog at 67 s, its stderr printed.

Changelog: none
Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-11-09 00:20:50 -05:00
..
page.html wai-int-module: the first WA²ISM module of record, the operator-set module held at the integer level on every engine 2026-11-08 16:45:56 -05:00
run-browser.mjs wai-int-module: the browser run ends when the page goes silent, with the browser's last words 2026-11-09 00:20:50 -05:00
worker.mjs wai-int-module: the first WA²ISM module of record, the operator-set module held at the integer level on every engine 2026-11-08 16:45:56 -05:00