You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Without the mod path manipulation, the warnings are gone.
Questions
Are these tests even executed in our CI? I don't see them mentioned in the logs.
Are there any other tests not executed?
Should we add an --all-targets check?
Mitigation
Sure we could just [allow(...)] the two warnings, but I'd prefer something better.
Perhaps we could just move the test_unique_auto_deletable_file module.
While googling, I found this recommendation on integration test organization, which could even reduce the testing time (hence the performance label I'm putting on this issue).
We could also remove the bench file, I don't think we've ever used it, and I don't think it's a part of our CI.
The text was updated successfully, but these errors were encountered:
Warning
For some time now, we've had the issue of two imports reported in
mod test_unique_auto_deletable_file
incrates/starknet-devnet/tests/common/utils.rs
:starknet-devnet-rs/crates/starknet-devnet/tests/common/utils.rs
Line 338 in eb8d800
Our check scripts don't consider this file; it's only reported by VS Code's rust-analyzer.
Reproduce
When I run
cargo check --all-targets
, I get this (omitted parts are replaced with[...]
):Cause
Notice how it reports the warnings as belonging to
mint_benches
inbenches
. This is due to apub mod common
annotation inmint_bench.rs
:starknet-devnet-rs/crates/starknet-devnet/benches/mint_bench.rs
Line 6 in eb8d800
Without the mod path manipulation, the warnings are gone.
Questions
--all-targets
check?Mitigation
[allow(...)]
the two warnings, but I'd prefer something better.test_unique_auto_deletable_file
module.performance
label I'm putting on this issue).The text was updated successfully, but these errors were encountered: