ci: add wasm32v1-none target and SKIP_WASM_BUILD to fix serde_core duplicate alloc error

The paritytech CI container lacks the wasm32v1-none target, causing
wasm-builder to fall back to wasm32-unknown-unknown with -Z build-std.
Combined with our serde_core fork, this creates a duplicate lang item
error for alloc crate.

Fix: Add rustup target add wasm32v1-none to all WASM-building jobs.
For check-only jobs (bench checks, docs, each-crate), add SKIP_WASM_BUILD=1.

Also fixes test-deterministic-wasm wasm blob path to work with either target.
This commit is contained in:
2026-02-23 02:52:20 +03:00
parent 15dff1ad0a
commit 41ea3148ec
5 changed files with 49 additions and 3 deletions
+2
View File
@@ -28,6 +28,7 @@ jobs:
volumes:
- /cache/cargo-target/pezkuwi-sdk-docs:/cache/target
env:
SKIP_WASM_BUILD: 1
RUSTFLAGS: "-Cdebug-assertions=y -Dwarnings"
CARGO_INCREMENTAL: 0
CARGO_TARGET_DIR: /cache/target
@@ -67,6 +68,7 @@ jobs:
volumes:
- /cache/cargo-target/pezkuwi-sdk-docs:/cache/target
env:
SKIP_WASM_BUILD: 1
CARGO_INCREMENTAL: 0
CARGO_TARGET_DIR: /cache/target
RUSTDOCFLAGS: "-Dwarnings --default-theme=ayu --html-in-header ./docs/sdk/assets/header.html --extend-css ./docs/sdk/assets/theme.css --html-after-content ./docs/sdk/assets/after-content.html"