open-standards/.github/workflows/joule-code-conformance.yml
Transaction Science 23d8d31f65
Some checks failed
smart-byte conformance gate / Validate conformance JSON files (pull_request) Has been cancelled
smart-byte conformance gate / Second implementation reproduces every vector (pull_request) Has been cancelled
smart-byte conformance gate / Spec changes require vector-pack updates (pull_request) Has been cancelled
smart-byte conformance gate / VERSIONS.md and README.md must exist (pull_request) Has been cancelled
joule-code conformance gate / Build + round-trip C1-C4 vectors (pull_request) Has been cancelled
jouleclaw public surface must stay documented / Public-surface audit (jouleclaw-rs) (pull_request) Has been cancelled
no-vanity-metrics / Scan committed Markdown for vanity metrics (pull_request) Has been cancelled
no-vanity-metrics / WAI public text names no comparison (pull_request) Has been cancelled
no-vanity-metrics / WAI public text names no company or product (pull_request) Has been cancelled
standards workspaces build + test / jouleclaw-rs (pull_request) Has been cancelled
standards workspaces build + test / aac-rs (pull_request) Has been cancelled
standards workspaces build + test / arl-rs (pull_request) Has been cancelled
standards workspaces build + test / eoc-rs (pull_request) Has been cancelled
standards workspaces build + test / jcp-rs (pull_request) Has been cancelled
standards workspaces build + test / joule-code-rs (pull_request) Has been cancelled
standards workspaces build + test / joule-ui-rs (pull_request) Has been cancelled
standards workspaces build + test / joulecontract-rs (pull_request) Has been cancelled
standards workspaces build + test / jouledesk-rs (pull_request) Has been cancelled
standards workspaces build + test / joulehook-rs (pull_request) Has been cancelled
standards workspaces build + test / map-rs (pull_request) Has been cancelled
standards workspaces build + test / mesh-rs (pull_request) Has been cancelled
standards workspaces build + test / openpay (pull_request) Has been cancelled
standards workspaces build + test / proof-rs (pull_request) Has been cancelled
standards workspaces build + test / sandbox-rs (pull_request) Has been cancelled
standards workspaces build + test / sense-rs (pull_request) Has been cancelled
standards workspaces build + test / smart-byte-rs (pull_request) Has been cancelled
standards workspaces build + test / macOS energy backends (pull_request) Has been cancelled
wai cross-architecture byte-equality / linux-aarch64 (pull_request) Has been cancelled
wai cross-architecture byte-equality / linux-x86_64 (pull_request) Has been cancelled
wai cross-architecture byte-equality / macos-arm64 (reference) (pull_request) Has been cancelled
WAI conformance / cargo-class corpora · linux (pull_request) Has been cancelled
WAI conformance / cargo-class corpora · linux-arm64 (pull_request) Has been cancelled
WAI conformance / cargo-class corpora · macos (pull_request) Has been cancelled
WAI conformance / v2 vocabulary · manifests validate as stated (pull_request) Has been cancelled
WAI conformance / independent verifiers · claims, JWP, key discovery and integer payloads (Python) (pull_request) Has been cancelled
WAI conformance / cross-arch byte-equality · linux (pull_request) Has been cancelled
WAI conformance / cross-arch byte-equality · linux-arm64 (pull_request) Has been cancelled
WAI conformance / cross-arch byte-equality · macos (pull_request) Has been cancelled
WAI conformance / C2PA manifest emission · signed, read back, validated (pull_request) Has been cancelled
WAI energy receipts / energy receipts · linux (pull_request) Has been cancelled
WAI energy receipts / energy receipts · linux-arm64 (pull_request) Has been cancelled
WAI energy receipts / energy receipts · macos (pull_request) Has been cancelled
wai formal verification (integer core) / kani (pull_request) Has been cancelled
WAI JPEG-AI whole decode (pinned inputs, required) / fetch pinned JPEG-AI inputs → whole decode + pixel hash, required (pull_request) Has been cancelled
WAI neural decoders end-to-end / synthetic fixtures → Rust decode → reference (±4) (pull_request) Has been cancelled
WAI neural sink gates / model-free refusals of the neural sink (pull_request) Has been cancelled
WAI section references / cited sections exist (pull_request) Has been cancelled
WAI mbt2018_mean integer decode (regenerated vectors) / regenerate mbt2018_mean integer vectors → Rust decode, required (pull_request) Has been cancelled
wai-web wasm32 / wai-web wasm32 build · corpus, menu and writers (pull_request) Has been cancelled
ci: one run per branch at a time — no workflow declared a concurrency group
Not one of this repo's 15 workflows declared `concurrency:`, so every push
queued a complete set of runs and nothing superseded anything. A session
pushing four versions of a branch queued four complete sets, and all of them
had to drain. On 2026-10-05 a PR's 21 contexts settled **none in 70 minutes**
behind a backlog of 25 runs, and the backlog grew faster than it cleared —
0.3.31 through 0.3.34 of one branch, four full sets, when only the newest
commit's verdict was wanted.

Every workflow now groups on `${{ github.workflow }}-${{ github.ref }}` with
`cancel-in-progress: true`.

**Verified before being added here, not assumed.** An unparseable workflow
would mean no CI at all, which is a worse failure than a slow queue, and none
of the fleet's existing `concurrency:` users are on this forge — they are
GitHub-hosted, so they prove GitHub parses the key, not Forgejo. Pushed a probe
to `ci-test` on this forge (Forgejo 16.0.5) instead: runs were created, so the
key parses; and a newer push moved two older runs to `cancelled` **while they
were still queued**, which is exactly the case that matters here.

`cancel-in-progress: true` applies to `main` too. That is deliberate: main
advances by merge commits whose tree contains the commits before them, so a
newer run covers an older one's changes.

## The queue's real shape, which is worse than one busy runner

Worth recording because it decides where the next fix goes. The workspace
matrix asks for three labels:

  - **`linux` — 5 workspaces** (jcp-rs, sandbox-rs, smart-byte-rs, proof-rs,
    eoc-rs) → jetson-hub, which the forge reports idle and connected.
  - **`linux-arm64` — 7 workspaces** (openpay, joule-code-rs, map-rs, aac-rs,
    joulecontract-rs, mesh-rs, jouleclaw-rs) → the colima `txarm` VM, **on the
    dev Mac**.
  - **`macos` — 5 workspaces** plus the dedicated `macOS energy backends` job
    → **the dev Mac**.

So **13 of 21 contexts land on the dev Mac** through two runners, while that
same machine was carrying another session's VVC/VTM encodes at load average
132 on 18 CPUs. That is why `jcp-rs` and `eoc-rs` returned quickly — they are
the two on jetson-hub — while `mesh-rs` (linux-arm64) took 25 minutes and the
macOS job never ran at all.

Concurrency groups cut the number of queued runs, which helps every label. They
do not change the fact that one host serves 13 of 21 contexts. The structural
options are to move some `linux-arm64` workspaces onto jetson-hub's `linux`, or
to stand up a second arm64/macOS host — the Mac Studio M3 Ultra is online and
idle — and that is a fleet change rather than a repo one, so it is flagged here
rather than attempted.

No regression guard is added. A check that every workflow declares the key
would itself need a CI job on the runner this change exists to unblock, and an
unwired check is worse than none.

Co-Authored-By: Claude Opus 5 <[email protected]>
2026-10-05 12:01:57 -04:00

113 lines
4.7 KiB
YAML
Raw Permalink Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

name: joule-code conformance gate
# Enforces the Joule Code conformance contract on every change: the reference
# library must build and pass its tests, and the published C1–C4 wire vectors
# must round-trip (SPEC §8). "Conformant = round-trips the vectors" — checked,
# not asserted.
# 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. With no concurrency group, a session pushing four versions
# of a branch queued four complete sets of runs and every one of them had to
# drain: on 2026-10-05 a PR's 21 contexts settled none in 70 minutes behind a
# backlog of 25 runs, and the queue grew faster than it cleared. Only the newest
# commit's verdict is wanted, so the older runs are cancelled.
#
# Verified on this forge (Forgejo 16.0.5) in `ci-test` before being added here:
# the key parses, and a newer push moves an older run to `cancelled` even while
# it is still queued, which is the case that matters.
#
# `cancel-in-progress: true` also applies to `main`. That is deliberate and
# safe here: main advances by merge commits whose tree contains the commits
# before them, so the newer run covers the older one's changes.
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
on:
pull_request:
paths:
- 'joule-code/**'
# joule-moq's receipt tests pin leaves, roots and signatures copied from WAI's
# jwp-conformance corpus, and run every leaf, group and object vector in it:
# a change there must re-run them.
- 'wai/jwp-conformance/**'
- '.github/workflows/joule-code-conformance.yml'
push:
branches:
- main
paths:
- 'joule-code/**'
# joule-moq's receipt tests pin leaves, roots and signatures copied from WAI's
# jwp-conformance corpus, and run every leaf, group and object vector in it:
# a change there must re-run them.
- 'wai/jwp-conformance/**'
- '.github/workflows/joule-code-conformance.yml'
jobs:
conformance:
name: Build + round-trip C1-C4 vectors
runs-on: linux
steps:
- name: Checkout
uses: actions/checkout@v4
# Bootstrap rustup: the docker runner image ships no Rust, and
# dtolnay/rust-toolchain cannot help — it calls `rustup`, which is absent.
- name: Install Rust 1.98.0
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.98.0
rustup toolchain install 1.98.0 --profile minimal
rustup default 1.98.0
echo "$HOME/.cargo/bin" >> "$GITHUB_PATH"
- name: Cache cargo
uses: actions/cache@v4
with:
path: |
~/.cargo/registry
~/.cargo/git
joule-code/joule-code-rs/target
key: joule-code-${{ runner.os }}-${{ hashFiles('joule-code/joule-code-rs/Cargo.lock') }}
# joule-code-remediate's formal gate shells out to `z3`, and the runner
# image has no solver. Its tests assert in both branches. With a solver
# installed here, JOULE_FIX_EXPECT_Z3=1 makes its absence a failure, so
# this gate runs the real-solver branch rather than the fail-closed one.
- name: Install z3
shell: bash
run: |
SUDO=""; [ "$(id -u)" -ne 0 ] && SUDO="sudo"
$SUDO apt-get update -qq
$SUDO apt-get install -y -qq z3
z3 --version
- name: Reference library tests
working-directory: joule-code/joule-code-rs
env:
JOULE_FIX_EXPECT_Z3: '1'
run: cargo test --workspace
# joule-moq's QUIC transport and its example compile only with `quic`. Named
# here so they stay built and tested whatever the workspace's other members
# happen to enable; this also runs tests/wai_jwp_corpus.rs, every leaf, group
# and object vector of wai/jwp-conformance through the crate.
- name: joule-moq with the QUIC transport, every target
working-directory: joule-code/joule-code-rs
run: cargo test -p joule-moq --features quic --all-targets
- name: Round-trip the v1 conformance pack (C1-C4)
working-directory: joule-code/joule-code-rs
run: |
set -e
out="$(cargo run -q -p joule-code-conformance -- verify ../conformance/v1)"
echo "$out"
# The pack must pass with zero failures.
echo "$out" | grep -Eq '0 failed' || { echo "::error::conformance pack reported failures"; exit 1; }
- name: L3 JouleClaw binding example builds + tests
working-directory: joule-code/examples/l3-jouleclaw
run: cargo test