Closed sam0x17 closed 1 year ago
This also raises the question: do we not check that cargo test
with no arguments has no warnings in CI?
bot fmt
@gupnik https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3045422 was started for your command "$PIPELINE_SCRIPTS_DIR/commands/fmt/fmt.sh"
. Check out https://gitlab.parity.io/parity/mirrors/substrate/-/pipelines?page=1&scope=all&username=group_605_bot to know what else is being executed currently.
Comment bot cancel 1-ff4704ef-090b-4811-a343-3e7127216169
to cancel this command or bot cancel
to cancel all commands in this pull request.
@gupnik Command "$PIPELINE_SCRIPTS_DIR/commands/fmt/fmt.sh"
has finished. Result: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3045422 has finished. If any artifacts were generated, you can download them from https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3045422/artifacts/download.
This fixes the unused error fornew_test_ext()
in the kitchensink example when runningcargo test
with no argumentsHappy to address this some other way like with a cfg flag if appropriate.Fixes the unused error for
new_test_ext()
when compilingcargo test
by adding a test that uses it