tornadocontrib/web3-proxy
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

add --locked to nextest

Browse Source
This commit is contained in:
Bryan Stitt 2023-06-25 21:47:18 -07:00
parent 4396cbb759
commit e47eccb893
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Dockerfile
View File

@ -40,7 +40,7 @@ RUN --mount=type=cache,target=/usr/local/cargo/registry \
# TODO: more mount type cache? # TODO: more mount type cache?
RUN --mount=type=cache,target=/usr/local/cargo/registry \ RUN --mount=type=cache,target=/usr/local/cargo/registry \
\ \
cargo install cargo-nextest cargo install --locked cargo-nextest
# foundry is needed to run tests # foundry is needed to run tests
# TODO: do this in a seperate FROM and COPY it in # TODO: do this in a seperate FROM and COPY it in
@ -57,7 +57,7 @@ RUN --mount=type=bind,target=.,rw \
--mount=type=cache,target=/usr/local/cargo/registry \ --mount=type=cache,target=/usr/local/cargo/registry \
--mount=type=cache,target=/app/target \ --mount=type=cache,target=/app/target \
\ \
RUST_LOG=web3_proxy=trace,info cargo nextest run --features "$WEB3_PROXY_FEATURES" --no-default-features && \ RUST_LOG=web3_proxy=trace,info cargo --locked nextest run --features "$WEB3_PROXY_FEATURES" --no-default-features && \
touch /test_success touch /test_success
# TODO: does this split of build_tests and build_app actually do anything if they both mount the same cache? # TODO: does this split of build_tests and build_app actually do anything if they both mount the same cache?