open-standards/.github/workflows/wai-vector.yml
Transaction Science ec45aaaca9 toolchain: Rust 1.98.0 -> 1.99.1 (change-controlled pin)
Approved by the owner on 2026-10-22. Procedure: change `channel`, run
`rustup show`, then run the pipeline.

What changed
- rust-toolchain.toml and eoc/eoc-rs/rust-toolchain.toml: channel "1.98.0"
  becomes "1.99.1". These are the only two pins in the tree, and the root one
  governs every other cargo root.
- 64 workflows under .github/workflows (the forge's CI): every `Install Rust
  1.98.0`, `rustup toolchain install / default / component add / target add
  --toolchain 1.98.0` and `--default-toolchain 1.98.0` now names 1.99.1
  (409 lines). Two of those lines are in build steps rather than install
  steps (wai-conformance.yml's two `wasm32 (unix)` steps each
  `rustup target add --toolchain`), and they move with the rest: a target
  added to a toolchain that is not installed is an error.
- Left as they are, because they record what was measured on 1.98.0:
  standards-build.yml's "Verified on a native arm64 Linux container (rustc
  1.98.0)", wai-conformance.yml's note on Rust 1.98's LLD 22, and the
  "rustc 1.98.0 (example)" strings in receipts, vectors and docs. The
  one-codegen-unit workaround that note explains also stays. 1.99.1 ships
  LLD 23.1.1, which the note says links those inputs, but removing the
  workaround should wait for a run at the CI path on x86_64.

Why
- 1.98.0 has a P-critical miscompile, rust-lang/rust#161441 (I-miscompile,
  regression-from-stable-to-stable). rustc emits a vacant (null) method slot
  in a trait-object vtable, so a safe dynamic call jumps to address zero
  (undefined behaviour). RELEASES.md records the fix in 1.98.1 ("rustc: fix
  miscompilation in generating vtables").
- 1.99.1 is the current stable (channel manifest dated 2026-10-15; rustc
  58cf8f9c3 2026-10-13). It also fixes 1.99.0's own regressions: wcslen on
  UEFI and embedded targets, x86_64 FFI `bool` returns, and the rust-lld rpath
  on macOS.

Evidence
All of it ran on the build host ([email protected], aarch64-apple-darwin)
through ~/kani-logs/remote/rb. Nothing was built on the dev Mac.

- `rustup show`: the active toolchain is 1.99.1-aarch64-apple-darwin,
  "overridden by .../rust-toolchain.toml" (and by eoc/eoc-rs's own file
  there). rustc 1.99.1 (58cf8f9c3 2026-10-13), LLVM 23.1.1, clippy 0.1.99,
  rustfmt 1.10.0. The baseline is rustc 1.98.0 (88d9e12ae 2026-08-18).
- Scope: every cargo root the pin governs, which is 46 of the 49 tracked
  lockfiles. The other three: two are vendored crates that resolve inside
  their parents, and wai/wai-rs/fuzz builds on its own pinned nightly.
- Trees. The final tree is main at 96117c570 plus these two commits. Main
  moved four times while this ran, and each root's evidence comes from the
  newest tree it was run on:
  - 13 roots on the final tree: every root main changed after 1a465f23d,
    and every root that consumes such a crate by path.
  - 12 roots on 1a465f23d plus these two commits.
  - 7 roots on b16816671 plus these two commits.
  - 14 roots on aa61ab3b9 plus the pin change.
  For each root in the last three groups, checked with git diff and the
  lockfiles' path packages: none of its files, and no crate it reaches by
  path, differs on the final tree.
- Each root got:
  (a) `cargo fmt --all -- --check` on the pin and on 1.98.0. The output is
      byte-identical in all 46. CI gates no root on rustfmt, and none is
      rustfmt-clean on main.
  (b) `cargo clippy --locked --keep-going --workspace --all-targets` on both
      toolchains, with the diagnostics compared line by line. After the
      previous commit, no root has a diagnostic that only 1.99.1 reports.
      openpay's one differing line is the same lint at the same site,
      reworded.
  (c) `cargo test --workspace --locked`.
  (d) the root's other CI steps that can run on this host: feature-gated
      tests, conformance suites, release-profile tests, the aac page-set
      checks, and every clippy -D warnings gate. The gates are
      standards-build's macOS meter and omni lints (jouleclaw-energy x2,
      jouleclaw-omni metal, jouleclaw-loader-gguf, jcp, proof, eoc, sandbox),
      wai-pack, wai-quantum-cli (default, no-default and metal),
      wai-quantum-service, wai-quantum-qpu and wai-quantum-desktop.
- Totals: `cargo test --workspace` ran in 43 roots: 12,532 passed, 1 failed,
  101 ignored. The other 3 roots are wasm32-only, and their
  `cargo build --release --target wasm32-unknown-unknown` passed. Every
  other CI step passed (62 of 62).
- On the final tree: scripts/check-lockfiles.sh (cargo 1.99.1) found all 47
  lockfiles current, and scripts/check-advisories.py passes.
- tokio is 1.54.1 in every lockfile cargo reads. That is patched for both
  RUSTSEC-2026-0386 (>= 1.53.3) and RUSTSEC-2026-0384 (>= 1.54.1). The 1.53.1
  in vendor/wtransport/Cargo.lock is the upstream file kept with the vendored
  source; cargo resolves wtransport inside its parents, and both gates skip
  that file.
- What is not green, each one reproduced on 1.98.0:
  - wai-ops-gpu: under the debug profile, `corpus` trips the debug_assert at
    exec.rs:187 on both toolchains. CI runs it in release only, and that
    passes (6/6).
  - wai-ops: clippy::derived_hash_with_manual_eq (deny-by-default) on both
    toolchains. No CI job runs clippy there.
  - wai-vector/wasm: `--all-targets` cannot build the lib-test target (its
    own `panic_impl`) on either toolchain. `clippy --lib` for wasm32 reports
    0 diagnostics on both.
  - eoc-cascade's hit_calibration_process_energy test reads real energy
    counters, and it fails some of the time on the loaded shared host. In
    interleaved runs each toolchain passed 18 of 20. The full eoc-rs suite
    passed on the final tree (741 passed).
- Environment, not code:
  - wai-quantum-desktop embeds the Studio's build, so wai/quantum-studio was
    built first (`npm ci`, `node build.mjs`), as CI does.
- Not covered here: the x86_64 and arm64 Linux and Windows legs; the GPU,
  NPU, FPGA, emulator and hardware-meter legs; wasm32 tests under Node,
  wasmtime and wasip2; and the fuzz job.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-11-03 17:42:20 -05:00

392 lines
17 KiB
YAML

name: wai-vector vector graphics
# The vector graphics capability (wai/extensions/graphics-vector.md), checked on every
# fabric leg the corpus has today. Every leg recomputes every expected file of
# wai/vector-conformance/ from its vector and the committed sets, and requires the
# committed bytes:
#
# - Linux x86_64, Linux arm64 and macOS arm64, natively, debug and release: the unit
# tests, the refusal-order, canonical, clock, track, geometry, cost, held-set and
# raster tests, the corpus tests (every frame of the rendering groups recomputed
# to its SHA-256, and every text record of the a11y group recomputed byte for
# byte), the in-house sets' tests (the default stroke set's SHA-256 is Annex B's,
# Annex A's table is the expansion's, and both sets re-derive from their WSF1
# sources), the text layer's tests (the projection and the transcript of section
# 5.4 against JSON written out by hand, and the worked example read from the
# extension), and `wai-vector vectors verify`, which also regenerates the whole
# corpus and converts every payload's authoring form back to its bytes; and the
# sink's build, without the feature `author`, so with no stroker;
# - WASI (wasm32-wasip2) under wasmtime, a 32-bit target: the same tests and the same
# `vectors verify`;
# - a browser's engine (wasm32-unknown-unknown) under Node: the recomputation of
# every expected file and every authoring form, in a sink's build (an a11y
# payload's expected file states the SHA-256 of its text record, so the projection
# and the transcript are recomputed here too), and the default stroke set's
# SHA-256 against Annex B;
# - three browser engines (chromium, webkit and firefox, as Playwright 1.60.0 names
# the engines it drives), in that version's container image, pinned by digest. The
# package a site serves (the sink's exports alone, built for wasm32v1-none and read
# back as WebAssembly 1.0 by wasm/check-mvp.mjs) loads every payload to its code,
# states each listed size's cost, and renders the frames through the page's hook:
# each is hashed by the module and by the platform, and the sampled ones are sent
# to Node and hashed there. For each a11y payload the sink's transcript and its
# projection at every frame of every listed rate, written out as the text
# record's lines, must be the committed record byte for byte. The recomputation
# module then recomputes every expected file and authoring form in each engine.
# A missing engine fails the job;
# - the fuzz leg: the corpus-seeded fuzz of the WOS1 and WVG1 parsers at depth, each
# accepted payload of small cost rendered and each accepted payload's text layer
# held (its transcript is JSON, and its projections list the blocks the frame
# procedure draws), the peak-allocation test and the duplicate-detection
# comparison count;
# - the independent checker, tools/wai_vector_check.py: Python standard library only,
# written from the extension text alone and sharing no code with wai-vector, which
# recomputes every expected file byte for byte (every frame by the closed-form
# crossings in big integers), rewrites every payload and set to its own bytes, and
# recomputes every digest of sha256.json.
#
# There is no Windows leg: the Windows runner has been offline since 2026-08-28.
# One run per branch at a time. A push supersedes the run before it.
#
# There is one `macos` runner and it is the dev Mac, so every macOS job in this repo
# queues on it; only the newest commit's verdict is wanted, so older runs are
# cancelled. `cancel-in-progress: true` also applies to `main`, which advances by
# merge commits whose tree contains the commits before them.
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
on:
pull_request:
paths:
- 'wai/wai-vector/**'
# SHA-256 is wai-ops's, included by #[path].
- 'wai/wai-ops/src/sha256.rs'
- 'wai/vector-conformance/**'
- 'wai/tools/wai_vector_*.py'
# The text the crate and the corpus are held to.
- 'wai/extensions/graphics-vector.md'
# The licence text the in-house sets carry in their notes.
- 'LICENSE'
- '.github/workflows/wai-vector.yml'
push:
branches:
- main
paths:
- 'wai/wai-vector/**'
- 'wai/wai-ops/src/sha256.rs'
- 'wai/vector-conformance/**'
- 'wai/tools/wai_vector_*.py'
- 'wai/extensions/graphics-vector.md'
- 'LICENSE'
- '.github/workflows/wai-vector.yml'
jobs:
# Does this pull request's own diff touch the paths below? This forge matches a
# workflow's `paths:` against the push, so a merge of main into a branch fires the
# workflow whatever the pull request changes; every job here waits on this answer.
# A push to main, a schedule, or anything the script cannot determine answers
# `true` (scripts/pr-touches-paths.py).
relevant:
name: does this change touch it
runs-on: linux
outputs:
run: ${{ steps.gate.outputs.run }}
steps:
- uses: actions/checkout@v5
with:
fetch-depth: 0
- id: gate
run: |
set -euo pipefail
r=$(python3 scripts/pr-touches-paths.py .github/workflows/wai-vector.yml \
"${{ github.event.pull_request.base.sha }}" \
"${{ github.event.pull_request.head.sha }}")
echo "this change touches wai-vector: $r"
echo "run=$r" >> "$GITHUB_OUTPUT"
native:
needs: relevant
if: needs.relevant.outputs.run == 'true'
name: ${{ matrix.label }}
runs-on: ${{ matrix.os }}
timeout-minutes: 40
strategy:
fail-fast: false
matrix:
include:
- { os: linux, label: linux-x86_64 }
- { os: linux-arm64, label: linux-aarch64 }
- { os: macos, label: macos-arm64 }
steps:
- uses: actions/checkout@v4
# The docker images ship no Rust; the macOS host has it, but launchd's PATH omits
# ~/.cargo/bin.
- name: Install Rust 1.99.1
shell: bash
run: |
export PATH="$HOME/.cargo/bin:$PATH"
command -v rustup >/dev/null 2>&1 || \
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y --profile minimal --default-toolchain 1.99.1
rustup toolchain install 1.99.1 --profile minimal
rustup default 1.99.1
echo "$HOME/.cargo/bin" >> "$GITHUB_PATH"
# Debug builds check every arithmetic operation for overflow, so a bound the
# text states that the code exceeds panics here.
- name: Every test, debug
working-directory: wai/wai-vector
shell: bash
run: cargo test --locked
- name: Every test, release
working-directory: wai/wai-vector
shell: bash
run: cargo test --locked --release
- name: The corpus regenerated, every expected file recomputed
working-directory: wai/wai-vector
shell: bash
run: cargo run --locked --release --features std --bin wai-vector -- vectors verify ..
# A sink has no stroker (graphics-vector.md §3.14): the library builds without
# the authoring code.
- name: The sink's build, without the feature author
working-directory: wai/wai-vector
shell: bash
run: cargo build --locked --no-default-features --lib
wasip2:
needs: relevant
if: needs.relevant.outputs.run == 'true'
name: wasm32-wasip2 (wasmtime)
runs-on: linux
timeout-minutes: 30
steps:
- uses: actions/checkout@v4
- name: Install Rust 1.99.1 with the wasm32-wasip2 target
shell: bash
run: |
export PATH="$HOME/.cargo/bin:$PATH"
command -v rustup >/dev/null 2>&1 || \
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y --profile minimal --default-toolchain 1.99.1
rustup toolchain install 1.99.1 --profile minimal
rustup default 1.99.1
rustup target add wasm32-wasip2
echo "$HOME/.cargo/bin" >> "$GITHUB_PATH"
- name: Install wasmtime 38.0.3
shell: bash
run: |
set -euo pipefail
v=38.0.3
curl --proto '=https' --tlsv1.2 -sSfL -o "$RUNNER_TEMP/wasmtime.tar.xz" \
"https://github.com/bytecodealliance/wasmtime/releases/download/v$v/wasmtime-v$v-x86_64-linux.tar.xz"
tar -C "$RUNNER_TEMP" -xf "$RUNNER_TEMP/wasmtime.tar.xz"
echo "$RUNNER_TEMP/wasmtime-v$v-x86_64-linux" >> "$GITHUB_PATH"
# The tests read committed files through CARGO_MANIFEST_DIR/.., so the wai
# directory is preopened at its own absolute path.
- name: Every test, under WASI
working-directory: wai/wai-vector
shell: bash
run: |
set -euo pipefail
W=$(cd .. && pwd)
CARGO_TARGET_WASM32_WASIP2_RUNNER="wasmtime run --dir $W::$W" \
cargo test --locked --release --target wasm32-wasip2
- name: Build the tool for wasm32-wasip2
working-directory: wai/wai-vector
shell: bash
run: cargo build --locked --release --features std --target wasm32-wasip2 --bin wai-vector
- name: The corpus regenerated, every expected file recomputed, under WASI
working-directory: wai
shell: bash
run: |
set -euo pipefail
wasmtime --version
wasmtime run --dir .::/wai wai-vector/target/wasm32-wasip2/release/wai-vector.wasm vectors verify /wai
node:
needs: relevant
if: needs.relevant.outputs.run == 'true'
name: wasm32 under Node
runs-on: linux
timeout-minutes: 30
steps:
- uses: actions/checkout@v4
- name: Install Rust 1.99.1 with the wasm32 target
shell: bash
run: |
export PATH="$HOME/.cargo/bin:$PATH"
command -v rustup >/dev/null 2>&1 || \
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y --profile minimal --default-toolchain 1.99.1
rustup toolchain install 1.99.1 --profile minimal
rustup default 1.99.1
rustup target add wasm32-unknown-unknown
echo "$HOME/.cargo/bin" >> "$GITHUB_PATH"
- uses: actions/setup-node@v4
with:
node-version: '22'
- name: Build the recomputation for wasm32-unknown-unknown
working-directory: wai/wai-vector/wasm
shell: bash
run: cargo build --locked --release --target wasm32-unknown-unknown
- name: Every expected file and authoring form recomputed under Node
working-directory: wai/wai-vector/wasm
shell: bash
run: node verify.mjs target/wasm32-unknown-unknown/release/wai_vector_wasm.wasm ../../vector-conformance
browser:
needs: relevant
if: needs.relevant.outputs.run == 'true'
name: wasm32 in three browser engines
runs-on: linux
timeout-minutes: 45
# Playwright 1.60.0's own image: Node and the three engines that version drives,
# already installed. Pinned by the digest of its linux/amd64 manifest (the linux
# runner is x86_64), so the engines' builds cannot move under the tag.
container:
image: mcr.microsoft.com/playwright:v1.60.0-noble@sha256:83192064c7510f7ee73dd63dc5f22a5e01a92c81a2e6a9c715d9e3fe55471fd9
env:
# The image runs as root, and an engine that finds HOME owned by another user
# refuses to start.
HOME: /root
steps:
- uses: actions/checkout@v4
# The image ships no Rust. wasm32v1-none is the package's target: its
# precompiled core and alloc are WebAssembly 1.0, which those of
# wasm32-unknown-unknown are not (wasm/build-pkg.sh says why that decides it).
- name: Install Rust 1.99.1 with the wasm32v1-none and wasm32-unknown-unknown targets
shell: bash
run: |
export PATH="$HOME/.cargo/bin:$PATH"
command -v rustup >/dev/null 2>&1 || \
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y --profile minimal --default-toolchain 1.99.1
rustup toolchain install 1.99.1 --profile minimal
rustup default 1.99.1
rustup target add wasm32v1-none wasm32-unknown-unknown
echo "$HOME/.cargo/bin" >> "$GITHUB_PATH"
# The sink's exports alone, built and then read back: every section, type,
# segment and instruction WebAssembly 1.0's, no imports, no 64-bit integer at an
# exported function, no floating point, and the exported functions the script
# lists. The build fails otherwise.
- name: The package, built for wasm32v1-none and read back as WebAssembly 1.0
shell: bash
run: bash wai/wai-vector/wasm/build-pkg.sh
- name: Build the recomputation for wasm32-unknown-unknown
working-directory: wai/wai-vector/wasm
shell: bash
run: cargo build --locked --release --target wasm32-unknown-unknown
# The check must be able to fail. The recomputation module is the default
# target's build, whose precompiled core and alloc use bulk memory: the reader
# must refuse it, and for that reason.
- name: The reader refuses a module that is not WebAssembly 1.0
working-directory: wai/wai-vector/wasm
shell: bash
run: |
set -euo pipefail
if node check-mvp.mjs target/wasm32-unknown-unknown/release/wai_vector_wasm.wasm > "$RUNNER_TEMP/check-default.log" 2>&1; then
cat "$RUNNER_TEMP/check-default.log"
echo "::error::check-mvp.mjs passed the default target's build"
exit 1
fi
cat "$RUNNER_TEMP/check-default.log"
grep -q 'NOT 1.0: bulk-memory (memory.copy)' "$RUNNER_TEMP/check-default.log" \
|| { echo "::error::check-mvp.mjs did not report bulk memory in the default target's build"; exit 1; }
# The image's engines are the ones this Playwright drives; the package comes
# from the lockfile, with its integrity hash.
- name: Playwright 1.60.0, from the lockfile
working-directory: wai/wai-vector/browser
shell: bash
run: |
set -euo pipefail
node --version
npm ci --no-audit --no-fund
# A missing engine is a failure: run.mjs passes only when all three ran.
- name: Every payload, frame, text record and vector in chromium, webkit and firefox
working-directory: wai/wai-vector/browser
shell: bash
run: |
set -euo pipefail
node run.mjs --engines chromium,webkit,firefox \
--pkg ../wasm/dist/pkg-vector \
--recompute ../wasm/target/wasm32-unknown-unknown/release/wai_vector_wasm.wasm \
../../vector-conformance
fuzz:
needs: relevant
if: needs.relevant.outputs.run == 'true'
name: fuzz, peak allocation, comparison count
runs-on: linux
timeout-minutes: 30
steps:
- uses: actions/checkout@v4
- name: Install Rust 1.99.1
shell: bash
run: |
export PATH="$HOME/.cargo/bin:$PATH"
command -v rustup >/dev/null 2>&1 || \
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y --profile minimal --default-toolchain 1.99.1
rustup toolchain install 1.99.1 --profile minimal
rustup default 1.99.1
echo "$HOME/.cargo/bin" >> "$GITHUB_PATH"
# Every corpus vector and every file under fuzz/seeds/ as a seed, 2,000
# mutations each: no input panics, and every accepted input writes back to
# its own bytes.
- name: Corpus-seeded fuzz at depth
working-directory: wai/wai-vector
shell: bash
env:
WAI_VECTOR_FUZZ_ITERS: '2000'
run: cargo test --locked --release --test fuzz_smoke -- --nocapture
- name: Peak allocation and the duplicate-detection comparison count
working-directory: wai/wai-vector
shell: bash
run: cargo test --locked --release --test peak_alloc --test canonical -- --nocapture
- name: Every workflow declares a concurrency group
shell: bash
run: bash scripts/check-workflow-concurrency.sh
checker:
needs: relevant
if: needs.relevant.outputs.run == 'true'
name: independent checker (Python)
runs-on: linux
timeout-minutes: 30
steps:
- uses: actions/checkout@v4
- uses: actions/setup-python@v5
with:
python-version: '3.11'
# Standard library only, so it needs nothing installed. Every frame of every
# rendering vector is rendered, the clock vector's 3840 x 2160 frames included.
- name: wai_vector_check.py recomputes every expected file of the corpus
working-directory: wai
shell: bash
run: python3 -I tools/wai_vector_check.py corpus vector-conformance --quiet
- name: Every workflow declares a concurrency group
shell: bash
run: bash scripts/check-workflow-concurrency.sh