ci: remove serde_core/wasm32v1-none workarounds, re-enable 35+ disabled jobs
The serde_core + Rust 1.88 issue only affects wasm32v1-none target. wasm32-unknown-unknown works fine, and wasm-builder falls back to it automatically when wasm32v1-none is not installed. - Remove all `rustup target add wasm32v1-none` steps (12 files) - Remove SKIP_WASM_BUILD=1 env vars added as workaround (28 occurrences) - Re-enable quick-benchmarks job (tests.yml) - Re-enable check-core-crypto-features job (checks.yml) - Re-enable 15 build/zombienet jobs (build-publish-images.yml) - Re-enable test-pezframe-examples-compile-to-wasm and test-deterministic-wasm jobs (tests-misc.yml) Tracking: #355, #357, #358 Upstream: https://github.com/serde-rs/serde/issues/3021 (still open)
This commit is contained in:
@@ -19,11 +19,9 @@ jobs:
|
||||
uses: ./.github/workflows/reusable-preflight.yml
|
||||
|
||||
# This job runs all benchmarks defined in the `/bin/node/runtime` once to check that there are no errors.
|
||||
# TEMPORARILY DISABLED: Requires WASM but serde_core + Rust 1.88 + wasm32 bug prevents WASM build
|
||||
# Tracking: https://github.com/pezkuwichain/pezkuwi-sdk/issues/358
|
||||
quick-benchmarks:
|
||||
needs: [preflight]
|
||||
if: false # Disabled until serde_core upstream fix
|
||||
if: ${{ needs.preflight.outputs.changes_rust }}
|
||||
runs-on: ${{ needs.preflight.outputs.RUNNER }}
|
||||
timeout-minutes: 45
|
||||
container:
|
||||
@@ -56,8 +54,6 @@ jobs:
|
||||
container:
|
||||
image: ${{ needs.preflight.outputs.IMAGE }}
|
||||
continue-on-error: true # this rarely triggers in practice
|
||||
env:
|
||||
SKIP_WASM_BUILD: 1
|
||||
steps:
|
||||
- name: Checkout
|
||||
uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
|
||||
@@ -81,7 +77,6 @@ jobs:
|
||||
container:
|
||||
image: ${{ needs.preflight.outputs.IMAGE }}
|
||||
env:
|
||||
SKIP_WASM_BUILD: 1
|
||||
CARGO_INCREMENTAL: 0
|
||||
steps:
|
||||
- name: Checkout
|
||||
|
||||
Reference in New Issue
Block a user