WASM builds were failing with getrandom/serde_core error when using
wasm32v1-none target. By removing the 'rustup target add wasm32v1-none'
step, wasm-builder will automatically fallback to wasm32-unknown-unknown.
Jobs fixed:
- build-linux-stable
- build-linux-stable-pezcumulus
- build-test-teyrchain
- build-test-collators
- build-malus
- build-linux-bizinikiwi
- build-templates-node
- tests-evm differential and evm-tests
- test-node-metrics
Tracking: https://github.com/pezkuwichain/pezkuwi-sdk/issues/358
Changes:
- Add Rust caching (Swatinem/rust-cache) to all heavy build jobs
- Reduce cargo-check-each-crate from 7 to 4 parallel jobs
- Reduce tests-linux-stable matrix from 6 to 3 jobs
- Set CARGO_INCREMENTAL=0 for consistent caching
- Reduce timeouts from 60 to 45 minutes (cache makes builds faster)
- Remove redundant disk cleanup steps (cache handles this)
Expected improvements:
- 50-80% faster builds after cache is populated
- Lower VPS load (fewer parallel jobs)
- More consistent build times
Affected workflows:
- checks.yml (cargo-clippy, check-try-runtime)
- tests.yml (quick-benchmarks, cargo-check-all-benches)
- tests-misc.yml (test-pezframe-ui, cargo-check-each-crate)
- tests-linux-stable.yml (test-linux-stable)
- docs.yml (test-doc, build-rustdoc)
Root cause: CI Docker images don't have wasm32v1-none target installed.
wasm-builder falls back to wasm32-unknown-unknown with -Z build-std=core,alloc
which causes duplicate alloc crate and 'exchange_malloc' lang item error.
Solution: Add 'rustup target add wasm32v1-none' before cargo build steps
in all workflows that build WASM.
Affected workflows:
- checks.yml: cargo-clippy job
- build-publish-images.yml: 11 jobs
- tests-misc.yml: test-node-metrics, test-deterministic-wasm
serde 1.0.218+ introduces serde_core which causes duplicate panic_impl
when building wasm32 with --features=serde. alloy-consensus requires
serde >= 1.0.226 so we cannot pin to older serde.
Tracking issue: #355
pezkuwichain