Conversation
The repository had no PR CI — only the scheduled timing lab — so the justfile gates ran on developer machines alone, and the branch ruleset had no checks to require. Three jobs, split by environment weight, each running the recipes the AGENTS.md check table names: - rust-checks: `just check` (fmt, clippy all-features, workspace tests, wasm build) plus `just audit` (no table-based AES in the release wasm artifact). - smoke: `just smoke` (the loopback rigs under Wasmtime) and `just smoke-tls-virt` (both tls-virt deliveries against openssl over real TCP). - interop: `just interop` (the composed component against OpenSSL and Go peers over TCP, and the quinn leg against quic-go over UDP, both directions). The job bodies live in the justfile; the workflow only provisions the environment (rustup per rust-toolchain.toml, taiki-e/install-action for just/wasmtime/wasm-tools/wac, setup-go pinned by the interop peer's go.mod, Swatinem cache with main-only saves). `just bench` and the timing lab stay non-gating by design.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The repository had no PR CI — only the scheduled timing lab — so the justfile gates ran on developer machines alone and the branch ruleset had nothing to require, leaving auto-merge inert here (the follow-up flagged when the org rulesets landed).
Three jobs, split by environment weight, each running the recipes the AGENTS.md check table names: rust-checks (
just check+just audit), smoke (just smoke+just smoke-tls-virt), interop (just interop). The job bodies live in the justfile; the workflow only provisions the environment — rustup per rust-toolchain.toml, taiki-e/install-action for just/wasmtime/wasm-tools/wac (wac-cli rides the action's cargo-binstall fallback, token-authenticated), setup-go pinned by the interop peer's go.mod, Swatinem cache with main-only saves.just benchand the timing lab stay non-gating by design (statistical; see timing-lab.yml's header).The Main ruleset now requires these three contexts plus PR flow, so this PR is itself the first exercise of the gate: it merges only by passing the CI it adds.