dd/sparse test failure on Solaris (zfs-backed?) NFS

2012-03-23 Thread Jim Meyering
Investigating a dd/sparse test failure on Solaris 10 with a (zfs-backed?) NFS partition, I did this: $ rm file.in; dd if=/dev/urandom of=file.in iflag=fullblock bs=1M count=3; \ n_old=0; while :; do n=$(du -k file.in|cut -f1); test $n = $n_old && continue;\ n_old=$n; printf '%04d ' $n; date +%T.%N

Re: dd/sparse test failure on Solaris (zfs-backed?) NFS

2012-03-23 Thread Pádraig Brady
Maybe just require_local_dir_ ? Offline for a few hours now. cheers, Pádraig.

Re: dd/sparse test failure on Solaris (zfs-backed?) NFS

2012-03-23 Thread Bernhard Voelker
On 03/23/2012 10:56 AM, Jim Meyering wrote: > +# Setup for block size tests: create a 3MiB file with a 1MiB > +# stretch of NUL bytes in the middle. > +rm -f file.in > +dd if=/dev/urandom of=file.in iflag=fullblock bs=1M count=3 || fail=1 > +dd if=/dev/zero of=file.in conv=notrunc bs=1M count=1 ||

Re: dd/sparse test failure on Solaris (zfs-backed?) NFS

2012-03-23 Thread Jim Meyering
Bernhard Voelker wrote: > On 03/23/2012 10:56 AM, Jim Meyering wrote: > >> +# Setup for block size tests: create a 3MiB file with a 1MiB >> +# stretch of NUL bytes in the middle. >> +rm -f file.in >> +dd if=/dev/urandom of=file.in iflag=fullblock bs=1M count=3 || fail=1 >> +dd if=/dev/zero of=file.

Re: dd/sparse test failure on Solaris (zfs-backed?) NFS

2012-03-23 Thread Jim Meyering
Pádraig Brady wrote: > Maybe just require_local_dir_ ? Tempting, but that would make us skip the whole test on all non-local file system types. I'd rather not.

new snapshot available: coreutils-8.15.89-4b101

2012-03-23 Thread Jim Meyering
This snapshot adds the ln --relative (-r) option, changes a bunch of tests not to fail, and makes ./configure take about 10% less time. Notably, this snapshot does not address the many MacOS-X-specific test failures that arise due to the fact that with the new quoting mechanism, the tools output d

[PATCH] tests: skip ls/stat-free-color on XFS, rather than always failing

2012-03-23 Thread Jim Meyering
FYI, without the following patch, the ls/stat-free-color test would always fail when run on an XFS file system. That happened because the d_type-check script would mistakenly report that XFS has d_type support, when in fact it does not, and thus the stat syscall count in that ls-testing script wou

ls, pathchk, shred, stty, wc: warning: missing initializer [-Wmissing-field-initializers]

2012-03-23 Thread Bernhard Voelker
According to the comment of commit v8.12-20-g73fd918: maint: remove -Wmissing-field-initializers workarounds * configure.ac: Rather than disabling -Wmissing-field-initializers, use the fact that gnulib now disables it automatically when required (on versions of GCC older than 4.7)

Re: ls, pathchk, shred, stty, wc: warning: missing initializer [-Wmissing-field-initializers]

2012-03-23 Thread Jim Meyering
Bernhard Voelker wrote: > According to the comment of commit v8.12-20-g73fd918: > > maint: remove -Wmissing-field-initializers workarounds > > * configure.ac: Rather than disabling -Wmissing-field-initializers, > use the fact that gnulib now disables it automatically when required >