codecov-commenter
commented
1 month ago Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 94.78%. Comparing base (
1020ea2) to head (406ddd7).
Additional details and impacted files
```diff @@ Coverage Diff @@ ## master #719 +/- ## ======================================= Coverage 94.77% 94.78% ======================================= Files 298 298 Lines 22194 22210 +16 ======================================= + Hits 21035 21052 +17 + Misses 1159 1158 -1 ```:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Pull Request Template
Description
In order to avoid new problems after a clippy update, I suggest to run the build cyclically for example each Thursday.
Related to #718, but I wanted to keep its scope as small as possible, to have it merged as quick as possible.
The CI will pass with having #718.
Checklist:
cargo clippy --all -- -D warningsjust before my last commit and fixed any issue that was found.cargo fmtjust before my last commit.cargo testjust before my last commit and all tests passed.mod.rsfile within its own folder, and in any parent folder(s).DIRECTORY.mdwith the correct link.COUNTRIBUTING.mdand my code follows its guidelines.Please make sure that if there is a test that takes too long to run ( > 300ms), you
#[ignore]that or try to optimize your code or make the test easier to run. We have this rule because we have hundreds of tests to run; If each one of them took 300ms, we would have to wait for a long time.