Transaction-Science/open-standards
Watch
1
0
Fork
You've already forked open-standards
 0
Code Issues Pull requests Projects Releases 17 Packages Wiki Activity Actions 142
open-standards/.github/wai-conformance
History
Exact
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Transaction Science 504890ad19 wai-conformance: run the deterministic module profile's checkers, and its changelog entry 
A verifier step of its own (.github/wai-conformance/verifiers/module-check.sh)
rebuilds the planted corpus and checks it is what build.py writes, runs the Rust
checker's tests and both checkers on the corpus and on the validation limits'
corpus, which it generates, then runs the differential on the committed seed.
The step's paths name the crate's directory, which is under none of the
workflow's trigger paths, so the trigger gains that one line.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-11-05 08:12:34 -05:00
..
corpora Changelog entries and the conformance workflow's lists move into files a change adds 2026-11-05 01:41:29 -05:00
verifiers wai-conformance: run the deterministic module profile's checkers, and its changelog entry 2026-11-05 08:12:34 -05:00
baseline.json Changelog entries and the conformance workflow's lists move into files a change adds 2026-11-05 01:41:29 -05:00
README.md Changelog entries and the conformance workflow's lists move into files a change adds 2026-11-05 01:41:29 -05:00

README.md

What wai-conformance.yml runs, one file a step

wai-conformance.yml keeps no hand list of its verifier steps, corpora or kernel tests. Its lists are derived, when it runs, from the files here and from tags in the test files, by scripts/wai-conformance-lists.py, whose docstring states every key; its gate reads the steps' paths: through scripts/pr-touches-paths.py. A change that adds a verifier, a corpus or a kernel test adds a file, or a line to a file of its own, and edits no line of the workflow, unless a step's paths: names a file under none of the trigger's paths (check names it). Its features and [[test]] entries in wai/wai-rs/Cargo.toml stay shared (wai/CONTRIBUTING.md).

  • verifiers/<name>.sh: one step of the independent-verifiers job. Its body is the step's shell, run in wai/ (or working-directory:) with bash -eo pipefail, as a workflow step runs. Its header, the leading # key: value lines, gives step: (its name), order: (steps run in ascending order, a tie by file name), features: (each list compiles alone in features-alone, and every feature joins WAI_FEATURES), and where it needs them alone:, build: pq, release-features:, bins:, pq-bins:, paths: (the extension texts it reads, which the workflow's gate then runs on) and working-directory:. Prose comments follow the header, after a # line.
  • corpora/<name>.txt: one cargo-class corpus, verified by its own tool on every leg of cargo-classes (corpus:, order:, bin:, dir:).
  • A test file of wai/wai-rs/tests/ whose first line is // wai-conformance: int-kernels runs in the fast integer kernels' steps of both profiles (int-kernels-release: the release step only; int-kernels-amd: the AVX-512 host too). The steps' features are the tagged tests' required-features.
  • baseline.json: the lists the workflow kept by hand before they were derived. The repository checks require every derived list to hold every entry of it, and every step it names to run.

To see what the workflow runs: python3 scripts/wai-conformance-lists.py dry-run (of another commit: --ref <commit>; two of them diff line by line). To run one step as CI does: python3 scripts/wai-conformance-lists.py run --only <name>. To check the files: python3 scripts/wai-conformance-lists.py check.