Skip to content
This repository was archived by the owner on Nov 15, 2023. It is now read-only.

Regression test to ensure we don't break deterministic builds in wasm #6597

Merged
6 commits merged into from
Jul 16, 2020
21 changes: 21 additions & 0 deletions .gitlab-ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -193,6 +193,27 @@ cargo-check-subkey:
- BUILD_DUMMY_WASM_BINARY=1 time cargo check --release
- sccache -s

test-deterministic-wasm:
stage: test
<<: *docker-env
variables:
<<: *default-vars
except:
variables:
- $DEPLOY_TAG
script:
# build runtime
- WASM_BUILD_NO_COLOR=1 cargo build --verbose --release -p node-runtime
# make checksum
- sha256sum target/release/wbuild/target/wasm32-unknown-unknown/release/node_runtime.wasm > checksum.sha256
# clean up – FIXME: can we reuse some of the artifacts?
- cargo clean
# build again
- WASM_BUILD_NO_COLOR=1 cargo build --verbose --release -p node-runtime
# confirm checksum
- sha256sum -c checksum.sha256
- sccache -s

test-linux-stable: &test-linux
stage: test
<<: *docker-env
Expand Down