ci: run the Rust codegen canary on PRs that touch the Rust backend - #1426
Merged
Merged
Conversation
The Rust codegen workflow ran only nightly and on dispatch, so a PR changing Rust codegen merged without the btc-listener downstream check. It now also runs on pull requests whose paths feed the Rust backend: the Rust emitter, shared codegen, MIR and its ownership passes, native providers and capability contracts, aver-rt, yield lowering and the self-hosted sources. The nightly schedule stays. A newer push to the same PR cancels the running canary. Neither job is a required check. The JS Work host test picked `node` from PATH and failed on Node 20. It now uses AVER_NODE when set, else `node` on PATH if it is Node 22 or newer, else the newest suitable nvm install. With none, it skips with a message naming what it tried; under CI, where the wasm-gc lane installs Node 24, it still fails. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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 Rust codegen workflow (corpus check and the btc-listener downstream canary) ran only nightly and on dispatch. #1424 needed a manual dispatch to get the downstream check.
rust-codegen.ymlnow also runs onpull_requestto main, limited bypaths:to what feeds the Rust backend:src/codegen/rust/**,src/codegen/common.rs,src/codegen/mod.rs,src/codegen/builtin*.rs,src/ir/mir/**(lowering and the own_param pass),src/ir/{alias,escape,last_use}.rs(ownership facts the Rust emitter reads),src/yield_lowering/**,src/provider/**,stdlib/capabilities/**,aver-rt/**,self_hosted/**,tests/rust_codegen_regression.rsand the workflow itself. The nightly cron and dispatch stay.Rust codegen regression,Rust codegen downstream (btc-listener)) are unchanged and do not collide with anyCIjob. main has no required status checks.wasm_host_work_spec::javascript_workers_run_the_coordinator_and_progress_independentlyusednodefrom PATH and failed on Node 20. It now takesAVER_NODEwhen set, elsenodeon PATH when it is Node 22+, else the newest Node 22+ under~/.nvm/versions/node. Without one it prints a SKIP line naming what it tried; whenCIis set (the wasm-gc lane installs Node 24 withactions/setup-node) a missing Node still fails.Checked locally: passes with Node 22, 25 and 26 (auto-picked from nvm with Node 20 on PATH); skips with
AVER_NODEon Node 20; fails with a clear message underCI=1and Node 20.