[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#7325: new test failure due to non-portability of printf formats like
From: |
Jim Meyering |
Subject: |
bug#7325: new test failure due to non-portability of printf formats like %05.3s |
Date: |
Fri, 12 Nov 2010 12:22:53 +0100 |
Pádraig Brady wrote:
> On 11/11/10 17:54, Paul Eggert wrote:
...
>> It's
>> not a big deal, but I still mildly prefer the * notation.
Same here.
However, here's an argument for using a different method, perhaps
with a hard-coded mapping from common FS types to known precision:
Running these two commands with different ordering prints
different results. When the file with NS%10 == 0 comes first,
stat suppresses the trailing 0(s):
$ stat -c '%4n %.*Z' 3 9
3 1289555520.29981438
9 1289555520.300814502
After the first non-multiple-of-10 nanoseconds value,
stat prints all trailing 0's:
$ stat -c '%4n %.*Z' 9 3
9 1289555520.300814502
3 1289555520.299814380
It's easy to create files like that via e.g.,
seq 10000|xargs touch -d '1970-01-01 18:43:33.5000000000'
- bug#7325: new test failure due to non-portability of printf formats like %05.3s, (continued)
- bug#7325: new test failure due to non-portability of printf formats like %05.3s, Jim Meyering, 2010/11/11
- bug#7325: new test failure due to non-portability of printf formats like %05.3s, Pádraig Brady, 2010/11/11
- bug#7325: new test failure due to non-portability of printf formats like %05.3s, Jim Meyering, 2010/11/11
- bug#7325: new test failure due to non-portability of printf formats like %05.3s, Jim Meyering, 2010/11/11
- bug#7325: new test failure due to non-portability of printf formats like %05.3s, Pádraig Brady, 2010/11/11
- bug#7325: new test failure due to non-portability of printf formats like %05.3s, Jim Meyering, 2010/11/12
- bug#7325: new test failure due to non-portability of printf formats like %05.3s, Pádraig Brady, 2010/11/11
- bug#7325: new test failure due to non-portability of printf formats like %05.3s, Eric Blake, 2010/11/11
- bug#7325: new test failure due to non-portability of printf formats like %05.3s, Paul Eggert, 2010/11/11
- bug#7325: new test failure due to non-portability of printf formats like %05.3s, Pádraig Brady, 2010/11/11
- bug#7325: new test failure due to non-portability of printf formats like %05.3s,
Jim Meyering <=
- bug#7325: new test failure due to non-portability of printf formats like %05.3s, Pádraig Brady, 2010/11/12
- bug#7325: new test failure due to non-portability of printf formats like %05.3s, Jim Meyering, 2010/11/12
- bug#7325: new test failure due to non-portability of printf formats like %05.3s, Paul Eggert, 2010/11/12
- bug#7325: new test failure due to non-portability of printf formats like %05.3s, Jim Meyering, 2010/11/13
- bug#7325: new test failure due to non-portability of printf formats like %05.3s, Paul Eggert, 2010/11/13
- bug#7325: new test failure due to non-portability of printf formats like %05.3s, Jim Meyering, 2010/11/13
- bug#7325: new test failure due to non-portability of printf formats like %05.3s, Jim Meyering, 2010/11/13
- bug#7325: new test failure due to non-portability of printf formats like %05.3s, Paul Eggert, 2010/11/13
bug#7325: new test failure due to non-portability of printf formats like %05.3s, Pádraig Brady, 2010/11/03