From: Matt Corallo Date: Thu, 6 Oct 2022 15:41:58 +0000 (+0000) Subject: Test `rapid-gossip-sync` in `no-std` in CI X-Git-Tag: v0.0.112~17^2~2 X-Git-Url: http://git.bitcoin.ninja/index.cgi?a=commitdiff_plain;h=e2e884725444e772140b47f0a4e36632dec3a261;p=rust-lightning Test `rapid-gossip-sync` in `no-std` in CI --- diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml index 49b857c39..a48ecc743 100644 --- a/.github/workflows/build.yml +++ b/.github/workflows/build.yml @@ -113,24 +113,19 @@ jobs: if: "matrix.build-no-std && !matrix.coverage" shell: bash # Default on Winblows is powershell run: | - cd lightning - cargo test --verbose --color always --no-default-features --features no-std - # check if there is a conflict between no-std and the default std feature - cargo test --verbose --color always --features no-std - # check that things still pass without grind_signatures - # note that outbound_commitment_test only runs in this mode, because of hardcoded signature values - cargo test --verbose --color always --no-default-features --features std - # check if there is a conflict between no-std and the c_bindings cfg - RUSTFLAGS="--cfg=c_bindings" cargo test --verbose --color always --no-default-features --features=no-std - cd .. - cd lightning-invoice - cargo test --verbose --color always --no-default-features --features no-std - # check if there is a conflict between no-std and the default std feature - cargo test --verbose --color always --features no-std - # check if there is a conflict between no-std and the c_bindings cfg - RUSTFLAGS="--cfg=c_bindings" cargo test --verbose --color always --no-default-features --features=no-std + for DIR in lightning lightning-invoice lightning-rapid-gossip-sync; do + cd $DIR + cargo test --verbose --color always --no-default-features --features no-std + # check if there is a conflict between no-std and the default std feature + cargo test --verbose --color always --features no-std + # check that things still pass without grind_signatures + # note that outbound_commitment_test only runs in this mode, because of hardcoded signature values + cargo test --verbose --color always --no-default-features --features std + # check if there is a conflict between no-std and the c_bindings cfg + RUSTFLAGS="--cfg=c_bindings" cargo test --verbose --color always --no-default-features --features=no-std + cd .. + done # check no-std compatibility across dependencies - cd .. cd no-std-check cargo check --verbose --color always cd ..