Skip to content
Snippets Groups Projects
Commit bd2aa791 authored by João Paulo Silva de Souza's avatar João Paulo Silva de Souza Committed by GitHub
Browse files

disable unleash-check (#9705)

the last successful run of this check was on b14d4f07 and it had been failing even before that

should be re-enabled lated
parent 0a8b3dde
No related merge requests found
......@@ -365,20 +365,20 @@ test-linux-stable: &test-linux
- SUBSTRATE_TEST_TIMEOUT=1 time cargo test -p substrate-test-utils --release --verbose --locked -- --ignored timeout
- sccache -s
unleash-check:
stage: test
<<: *docker-env
<<: *test-refs-no-trigger
script:
- cargo install cargo-unleash ${CARGO_UNLEASH_INSTALL_PARAMS}
- cargo unleash de-dev-deps
#unleash-check:
#stage: test
#<<: *docker-env
#<<: *test-refs-no-trigger
#script:
#- cargo install cargo-unleash ${CARGO_UNLEASH_INSTALL_PARAMS}
#- cargo unleash de-dev-deps
# Reuse build artifacts when running checks (cuts down check time by 3x)
# TODO: Implement this optimization in cargo-unleash rather than here
- mkdir -p target/unleash
- export CARGO_TARGET_DIR=target/unleash
- cargo unleash check ${CARGO_UNLEASH_PKG_DEF}
#- mkdir -p target/unleash
#- export CARGO_TARGET_DIR=target/unleash
#- cargo unleash check ${CARGO_UNLEASH_PKG_DEF}
# FIXME: this job must not fail, or unleash-to-crates-io will publish broken stuff
allow_failure: true
#allow_failure: true
test-frame-examples-compile-to-wasm:
# into one job
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment