Closed hanbings closed 4 months ago
Attention: Patch coverage is 77.96610%
with 13 lines
in your changes are missing coverage. Please review.
Project coverage is 59.12%. Comparing base (
add14db
) to head (6579285
).
Files | Patch % | Lines |
---|---|---|
src/find/matchers/time.rs | 73.07% | 3 Missing and 4 partials :warning: |
src/find/matchers/mod.rs | 50.00% | 2 Missing and 4 partials :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
please add integrations tests in https://github.com/uutils/findutils/blob/main/tests/find_cmd_tests.rs and please tests with invalid values (like string for numerical values)
please add integrations tests in https://github.com/uutils/findutils/blob/main/tests/find_cmd_tests.rs and please tests with invalid values (like string for numerical values)
I've added tests for string type numbers.
But I found that it is able to recognize error parameters such as 1%2
and +-321
, which is different from the GNU find results.
This has to do with the way the convert_arg_to_comparable_value
function recognizes and converts numbers, meaning that this problem occurs with both the a/c/mtime
and a/c/mmin
arguments.
Should I fix them in a new PR?
$ find . -atime 1%2
find: invalid argument `1%2' to `-atime'
$ find . -amin 1%2
find: invalid argument `1%2' to `-amin'
$ ./target/debug/find . -atime 1%2
$ ./target/debug/find . -amin 1%2
./.git
./.git/objects/b1
./.git/objects/7f
./.git/objects/a8
./target/debug/deps
./target/debug/incremental/find_cmd_tests-8yeq2sf4g2ts
...
Thanks, the conflict has been resolved and the code modified in new commits.
it would be nice to work on https://github.com/uutils/findutils/issues/360 next it will be easier to detect improvement / regression wrt the GNU test suite
it would be nice to work on #360 next it will be easier to detect improvement / regression wrt the GNU test suite
Thanks! I will complete it as soon as I can.
implement: https://github.com/uutils/findutils/issues/221