forks/toybox/tests, branch 0.6.1Toybox with POSIX patches from E5ten
https://git.carbslinux.org/forks/toybox/atom?h=0.6.12015-11-01T08:33:51+00:00Change grep -w to checking matches after the fact rather than modifing regex.2015-11-01T08:33:51+00:00Rob Landleyrob@landley.net2015-11-01T08:33:51+00:00urn:sha1:73e3a644c1af8e28ca45c3b5169dee8acc06b179
This lets '(x)\1' match, as reported by Isabella Parakiss.
Fix sed bug reported by Isabella Parakiss, where sed -e "/x/c\" -e "y" added2015-10-29T06:30:58+00:00Rob Landleyrob@landley.net2015-10-29T06:30:58+00:00urn:sha1:8132ad2f4ec9b463ed954a302e9e490b549b106a
an extra newline because the test for whether we have an existing string to
append a newline to was checking if struct step had data appended to it,
and the /x/ regex is data appended to it. Change test to check for null
terminator at ->arg1 offset.
Add find tests.2015-09-14T21:16:36+00:00Daniel K. Levyalliedenvy@gmail.com2015-09-14T21:16:36+00:00urn:sha1:59cd560200942a063c217e327fc7941ffb70abe9Fix a find segfault.2015-09-12T20:46:46+00:00Rob Landleyrob@landley.net2015-09-12T20:46:46+00:00urn:sha1:edae0b07db841e3bf8449d591971f04c9957ecbc
Elliott Hughes found a bug https://android-review.googlesource.com/#/c/170020/
and Daniel K. Levy worked out the problem: the user/group/newer arguments
to find weren't consuming their arguments when not checking the results of
their comparison (because an earlier test had already caused their
parenthetical group to fail). This confused the argument parsing logic
and could lead to segfaults.
I applied a different fix that reorganized the existing tests instead of
adding a new test. (Looks like a big commit but it's mostly whitespace
due to extra curly brackets changing indendentation levels.)
Switch HR_SI to HR_1000, make binary the default, make HR_B only affect bytes,2015-09-07T01:10:04+00:00Rob Landleyrob@landley.net2015-09-07T01:10:04+00:00urn:sha1:960100aa9cb588a73125d43ec0b0a7152a95b43f
and update the tests.
Add seq -f tests, tweak help text, and catch one more error case.2015-09-05T10:46:35+00:00Rob Landleyrob@landley.net2015-09-05T10:46:35+00:00urn:sha1:73eca9182dfd7c2d52775ca24da6a7a0d55b3ceeMake human_readable() handle base 1024 units without floating point.2015-09-04T01:36:44+00:00Rob Landleyrob@landley.net2015-09-04T01:36:44+00:00urn:sha1:d06ea3708d12e3e87fa26441715ac47f6dc63032
Rounds correctly via brute force, displayed digits are decimal even when
working with powers of 2, shows at most 3 significant (decimal) digits.
(So no "1023M" nonsense, that's 1.0G.)
Fix mv on overwrite.2015-08-30T11:35:30+00:00Elliott Hughesenh@google.com2015-08-30T11:35:30+00:00urn:sha1:f1f20b9306ed3658e9433e00e78f2ac640d0160d
We need to remove the destination, not the source, to be able to overwrite.
Fix more date bugs.2015-08-11T21:06:06+00:00Elliott Hughesenh@google.com2015-08-11T21:06:06+00:00urn:sha1:05499787ca89fa4b017c2441e89020799f02e4c1
Correctly and portably check for non-normal dates, and explicitly show
the "before" and "after" dates (in the format of the user's choosing).
Clear the struct tm in date_main rather than parse_default because on
one path the struct tm is actually initialized. Explicitly clear the
tm_sec field in parse_default because -- experiment shows -- that
should not be preserved. Only do the "what does this 2-digit year
mean?" dance if we actually parsed a 2-digit year. Show the right
string in the error message if strptime fails.
Also add more tests, and use UTC in the tests to avoid flakiness.
Reject invalid dates in date(1).2015-08-08T18:39:01+00:00Elliott Hughesenh@google.com2015-08-08T18:39:01+00:00urn:sha1:400dacdeb69bc13868a625fc2ce8b49b6acd5ae3
Humans get upset when date(1) lets mktime(3) work out what the 99th day
of the 99th month would be rather than rejecting the invalid date. For
the subtly wrong cases, rather than get into the leap year business,
let's rely on localtime_r(3).