wasm-gc: route raw-i64 String.fromInt to the lean i64 formatter #2243
Workflow file for this run
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| name: CI | |
| on: | |
| push: | |
| branches: [main] | |
| pull_request: | |
| branches: [main] | |
| # Nightly deep sweep against main with the heavy proptest budget: the | |
| # WASM job's cross-backend differential runs 2000 cases nightly but a | |
| # 64-case smoke per-PR (see its `PROPTEST_CASES` below). Mirrors the | |
| # fuzz / proof / rust-codegen nightlies (cron 03:00 UTC). Manual runs | |
| # via workflow_dispatch also get the full 2000-case sweep. | |
| schedule: | |
| - cron: '0 3 * * *' | |
| workflow_dispatch: | |
| env: | |
| CARGO_TERM_COLOR: always | |
| jobs: | |
| check: | |
| name: Check & Test | |
| runs-on: ubuntu-latest | |
| steps: | |
| - uses: actions/checkout@v5 | |
| - uses: dtolnay/rust-toolchain@stable | |
| with: | |
| components: clippy, rustfmt | |
| - uses: Swatinem/rust-cache@v2 | |
| - name: Format | |
| run: cargo fmt --all -- --check | |
| - name: Clippy | |
| run: cargo clippy --workspace --all-targets --exclude aver-lang -- -D warnings && cargo clippy -p aver-lang --lib --bin aver -- -D warnings | |
| - name: Test | |
| # Iron — Stage 4: CI exercises proptest sweeps at 2 000 cases | |
| # per property instead of the 256-case default. The matcher | |
| # invariants (`types::checker::tests`) and replay-codec | |
| # round-trip (`tests/replay_proptest.rs`) each surfaced real | |
| # bugs inside 256 cases; bumping the budget here lets CI sweep | |
| # ~8× deeper input space than a developer's local cycle does, | |
| # surfacing shapes that only fire at low probability. Local | |
| # `cargo test` keeps the 256 default for fast iteration. 2 000 | |
| # is conservative — 10 000 was the first instinct but risked | |
| # tipping the Check & Test runtime past the rest of the gates; | |
| # the per-test runtime gap of 256 vs 2 000 is in the seconds, | |
| # 2 000 vs 10 000 is in the minutes for the heavier codec | |
| # roundtrip tests. Bump again if a class of bug slips at 2 000. | |
| env: | |
| PROPTEST_CASES: '2000' | |
| run: cargo test --workspace | |
| - name: Check shipped examples | |
| # Gate the shipped example corpus: a merge that breaks an | |
| # example under `aver check` must fail CI, not ship silently. | |
| # `cargo test --workspace` above already compiled the debug | |
| # `aver` binary (the CLI integration tests run it via | |
| # CARGO_BIN_EXE_aver), so `cargo run` here is a cache hit, not | |
| # a rebuild. Only `examples/core` and `examples/data` are | |
| # gated — `examples/diagnostics` contains deliberately broken | |
| # files (lint/error demos) and stays ungated. Bare exit codes: | |
| # each command's status fails the step directly, no pipes. | |
| run: | | |
| cargo run --bin aver -- check examples/core | |
| cargo run --bin aver -- check examples/data | |
| wasm: | |
| name: WASM | |
| runs-on: ubuntu-latest | |
| steps: | |
| - uses: actions/checkout@v5 | |
| - uses: dtolnay/rust-toolchain@stable | |
| with: | |
| components: clippy | |
| - uses: Swatinem/rust-cache@v2 | |
| - name: Install WASM tools | |
| env: | |
| BINARYEN_VERSION: version_129 | |
| run: | | |
| curl -fsSL "https://github.com/WebAssembly/binaryen/releases/download/${BINARYEN_VERSION}/binaryen-${BINARYEN_VERSION}-x86_64-linux.tar.gz" -o binaryen.tar.gz | |
| tar -xzf binaryen.tar.gz | |
| echo "$PWD/binaryen-${BINARYEN_VERSION}/bin" >> "$GITHUB_PATH" | |
| test -x "$PWD/binaryen-${BINARYEN_VERSION}/bin/wasm-merge" | |
| test -x "$PWD/binaryen-${BINARYEN_VERSION}/bin/wasm-opt" | |
| test -x "$PWD/binaryen-${BINARYEN_VERSION}/bin/wasm-metadce" | |
| - name: Clippy (wasm + wasip2) | |
| run: cargo clippy -p aver-lang --lib --bin aver --features wasm,wasip2 -- -D warnings | |
| - name: Test (wasm + wasip2) | |
| # `wasip2` is a separate feature; `wasm` alone leaves every | |
| # `#![cfg(feature = "wasip2")]` test file at 0 tests, so the | |
| # wasip2 codegen / component-model surface went unchecked by the | |
| # gate. Enable both (they share `wasm-compile`) so the wasip2_* | |
| # suites run. | |
| # | |
| # Proptest budget — split per-PR vs nightly. The wasm-feature | |
| # proptests include the cross-backend DIFFERENTIAL sweeps | |
| # (`tests/cross_backend_proptest.rs`), which spawn `aver run` twice | |
| # per case (VM + wasm-gc) and JIT each module in wasmtime — | |
| # ~0.5-1.5s/case, vs microseconds for the in-process proptests in | |
| # the Check & Test job. At 2000 cases that is ~30 min, too slow for | |
| # every PR. So: a 64-case SMOKE per-PR, and the full 2000-case | |
| # sweep NIGHTLY (and on workflow_dispatch). The deterministic | |
| # differentials (sign matrices, the Euclidean law, canonical-eq, | |
| # interpolation render) run at ANY case count, so they stay the | |
| # real per-PR net; the 2000-case sweep is the broad randomized | |
| # net, alongside the fuzz nightly's `fuzz_parity_vm_vs_wasm_gc` | |
| # in-process differential. | |
| env: | |
| PROPTEST_CASES: ${{ (github.event_name == 'schedule' || github.event_name == 'workflow_dispatch') && '2000' || '64' }} | |
| run: cargo test -p aver-lang --features wasm,wasip2 | |
| wasm_release_build: | |
| # Post-merge release-build verification under `--features wasm`. | |
| # PR-time CI runs `cargo test --features wasm` (debug profile) in | |
| # the `wasm` job above — that catches every logic regression. The | |
| # release build only matters when the artifact actually ships | |
| # (post-merge to `main`), and dragging it onto PR-time CI added | |
| # 3–5 min of wait without ever surfacing a release-only bug in | |
| # practice. If a release-mode regression slips in, a hot follow-up | |
| # PR fixes it from main; PR review unblocks immediately. | |
| name: WASM release build (main) | |
| if: github.event_name == 'push' && github.ref == 'refs/heads/main' | |
| runs-on: ubuntu-latest | |
| needs: [check, wasm] | |
| steps: | |
| - uses: actions/checkout@v5 | |
| - uses: dtolnay/rust-toolchain@stable | |
| - uses: Swatinem/rust-cache@v2 | |
| - name: Build (wasm release) | |
| run: cargo build -p aver-lang --features wasm --release | |
| bench: | |
| # Post-merge bench gate. PR-time CI doesn't run this — perf | |
| # regressions get caught when they hit `main`, then a follow-up | |
| # PR reverts or fixes them. Trade chosen deliberately: PR review | |
| # unblocks 3–5 min faster, and the fix-forward latency for a perf | |
| # regression on a pre-1.0 compiler is acceptable. Locally, | |
| # contributors can still run `aver bench bench/scenarios/ | |
| # --target=vm` against their branch before opening a PR if they | |
| # touched a perf-sensitive path. | |
| name: Bench Gate | |
| if: github.event_name == 'push' && github.ref == 'refs/heads/main' | |
| runs-on: ubuntu-latest | |
| steps: | |
| - uses: actions/checkout@v5 | |
| - uses: dtolnay/rust-toolchain@stable | |
| - uses: Swatinem/rust-cache@v2 | |
| - name: Build aver (release) | |
| run: cargo build --release --bin aver | |
| - name: Run bench scenarios | |
| # `--baseline-dir bench/baselines/` auto-picks the file matching | |
| # this runner's host (`<os>-<arch>-vm.json`). When no matching | |
| # baseline exists, the bench run still produces reports but the | |
| # gate is silently skipped — first run on a new host won't fail | |
| # the build, just won't gate. To pin a Linux baseline, run | |
| # `aver bench bench/scenarios/ --target=vm --json --save-baseline | |
| # bench/baselines/linux-x86_64-vm.json` on this runner and | |
| # commit the result. | |
| run: | | |
| ./target/release/aver bench bench/scenarios/ \ | |
| --target=vm \ | |
| --baseline-dir bench/baselines/ \ | |
| --fail-on-regression \ | |
| --json | tee bench-results.ndjson | |
| - name: Upload bench results | |
| if: always() | |
| uses: actions/upload-artifact@v6 | |
| with: | |
| name: bench-results | |
| path: bench-results.ndjson | |
| retention-days: 30 | |