Fix bridge E2E CI by downgrading Rust to 1.88 to avoid wasmer probestack breakage#5583
Merged
deuszx merged 2 commits intotestnet_conwayfrom Mar 3, 2026
Merged
Conversation
deuszx
reviewed
Mar 3, 2026
| # Prefer crate versions compatible with our rust-version (1.88). | ||
| # This prevents alloy sub-crates from resolving to 1.7+ (MSRV 1.91), | ||
| # which would pull in Rust 1.91 and break linera-wasmer-vm's probestack. | ||
| incompatible-rust-versions = "fallback" |
deuszx
approved these changes
Mar 3, 2026
ndr-ds
added a commit
that referenced
this pull request
Mar 4, 2026
## Motivation PR #5583 added a `pull_request` trigger to `.github/workflows/bridge-e2e.yml` targeting `testnet_conway` so the bridge E2E test would run on that PR. The PR description explicitly noted this should be removed before merge, but it was merged with the trigger still in place. ## Proposal Remove the two-line `pull_request` trigger that was left behind. No other changes. ## Test Plan - Visual inspection — this only removes a CI trigger.
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
2 participants
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.
Motivation
The bridge E2E CI has been failing on every
testnet_conwaypush since at least Feb 28with a linker error:
rust-lld: error: undefined symbol: __rust_probestack
referenced by linera_wasmer_vm
PR #5582 pinned the bridge e2e toolchain to Rust 1.91 to satisfy alloy's MSRV, but Rust
1.89+ removed
__rust_probestackas a linkable extern symbol(rust-lang/rust#141992), which breaks
the linera wasmer fork (v4.4.0-linera.7) that still references it in
probestack.rs.Proposal
Use Rust 1.88 (the last version before the probestack removal) and cap alloy to
<1.7(since alloy 1.7+ requires Rust 1.91):
rust-toolchain.toml: 1.91 → 1.88Cargo.toml: Setrust-version = "1.88", cap alloy to>=1.0.42, <1.7.cargo/config.toml(new): Enable MSRV-aware resolver(
incompatible-rust-versions = "fallback") so alloy sub-crates also resolve to 1.6.xCargo.lock: Regenerated (alloy 1.3 → 1.6.3 across all sub-crates)bridge-e2e.yml: Addedpull_requesttrigger targetingtestnet_conwayso thetest runs on this PR
The proper long-term fix is updating the linera wasmer fork with the upstream probestack
fix (wasmerio/wasmer#5690). The alloy
cap comment documents this.
Test Plan
cargo checkpasses locally with Rust 1.88pull_requesttrigger on this PR will run the bridge E2E test in CI (remove thetrigger before merge)
Release Plan
Links
https://github.com/linera-io/linera-protocol/actions/runs/22633609986/job/65590305218
rust-lang/rust#141992
wasmerio/wasmer#5690
#5582