<feed xmlns='http://www.w3.org/2005/Atom'>
<title>coreutils/tests, branch v8.22</title>
<subtitle>Mirror of https://https.git.savannah.gnu.org/git/coreutils.git/
</subtitle>
<id>https://git.shady.money/coreutils/atom?h=v8.22</id>
<link rel='self' href='https://git.shady.money/coreutils/atom?h=v8.22'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/'/>
<updated>2013-12-13T02:29:03Z</updated>
<entry>
<title>tests: avoid unlikely deadlock in dd/no-allocate on some shells</title>
<updated>2013-12-13T02:29:03Z</updated>
<author>
<name>Pádraig Brady</name>
<email>P@draigBrady.com</email>
</author>
<published>2013-12-11T04:36:08Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=41e9a094ad1fd49c8887da24f0fabf222272bfbe'/>
<id>urn:sha1:41e9a094ad1fd49c8887da24f0fabf222272bfbe</id>
<content type='text'>
* test/dd/no-allocate.sh: Use 'wait' to ensure we don't have
multiple writers to the fifo, which was seen to trigger
a very hard to reproduce deadlock with make -j20 on solaris.
Also avoid writing to the fifo with the shell; instead using dd.
(check_dd_seek_alloc): A new function refactored from the various
cases, which are now constructed from function parameters.
</content>
</entry>
<entry>
<title>tests: restrict cp --link inode comparisons to compatible systems</title>
<updated>2013-12-13T02:28:47Z</updated>
<author>
<name>Pádraig Brady</name>
<email>P@draigBrady.com</email>
</author>
<published>2013-12-12T22:43:05Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=10ffe43d68f085995de5b95a8b301a9b7170eac2'/>
<id>urn:sha1:10ffe43d68f085995de5b95a8b301a9b7170eac2</id>
<content type='text'>
* tests/cp/link-deref.sh: On systems were cp can't determine if
gnulib linkat() emulation might create a symlink instead of a hardlink
to a symlink, copy.c will create a symlink to the symlink so that
it has more control over its metadata.  Also even if the system
supports this operation, the particular file system under test may not.
So avoid the hardlinked symlink verification in these cases.
This fixes a false failure on aix, solaris and freebsd.
</content>
</entry>
<entry>
<title>tests: df/total-unprocessed: fix false failure with lofs</title>
<updated>2013-12-11T14:15:33Z</updated>
<author>
<name>Pádraig Brady</name>
<email>P@draigBrady.com</email>
</author>
<published>2013-12-10T16:29:11Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=77a24724f6172af157b09fdfb870a8f526f39424'/>
<id>urn:sha1:77a24724f6172af157b09fdfb870a8f526f39424</id>
<content type='text'>
* tests/df/total-unprocessed.sh: Skip the test when we can't
determine the file system type as the exclusion filter is not
applied in that case.  "lofs" being ignored is effectively
an unknown file system type.
</content>
</entry>
<entry>
<title>tests: avoid warnings due to new filefrag -v format</title>
<updated>2013-12-11T04:42:59Z</updated>
<author>
<name>Pádraig Brady</name>
<email>P@draigBrady.com</email>
</author>
<published>2013-12-11T04:42:59Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=b95aac31803e64c766f4f0a097938366c7e3cee1'/>
<id>urn:sha1:b95aac31803e64c766f4f0a097938366c7e3cee1</id>
<content type='text'>
* tests/cp/sparse-fiemap.sh: Newer versions of filefrag output
more fields, in different orders, so handle that to avoid warnings.
</content>
</entry>
<entry>
<title>tests: fix false failure due to xargs usage</title>
<updated>2013-12-09T13:37:21Z</updated>
<author>
<name>Pádraig Brady</name>
<email>P@draigBrady.com</email>
</author>
<published>2013-12-09T13:34:03Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=b6d1e842c10bd0fe6d7e6937207c44c753caa7dd'/>
<id>urn:sha1:b6d1e842c10bd0fe6d7e6937207c44c753caa7dd</id>
<content type='text'>
* tests/readlink/multi.sh: Ensure there is a trailing delimeter
or xargs may (on AIX 7 at least) suppress the last argument.
</content>
</entry>
<entry>
<title>tests: fix false failure on systems without /dev/stdin</title>
<updated>2013-12-09T13:14:38Z</updated>
<author>
<name>Pádraig Brady</name>
<email>P@draigBrady.com</email>
</author>
<published>2013-12-09T13:10:40Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=b1fb185db87d9e173a2e1eacd1d58e9a1bdbeb40'/>
<id>urn:sha1:b1fb185db87d9e173a2e1eacd1d58e9a1bdbeb40</id>
<content type='text'>
* tests/rm/interactive-once.sh: Ensure the expected output
matches with the output on systems without /dev/stdin (like AIX 7).
Also change some fail=1 to a more appropriate framework_failure_.
</content>
</entry>
<entry>
<title>tests: fix false failure due to gdb inline function handling</title>
<updated>2013-12-09T09:28:29Z</updated>
<author>
<name>Pádraig Brady</name>
<email>P@draigBrady.com</email>
</author>
<published>2013-12-08T21:43:49Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=042780801c9ca765b633acc9dc7aebfa649fdbb1'/>
<id>urn:sha1:042780801c9ca765b633acc9dc7aebfa649fdbb1</id>
<content type='text'>
Inline functions are awkward to breakpoint as mentioned at:
https://sourceware.org/bugzilla/show_bug.cgi?id=10738
The normal case here was for the breakpoint on the inline function
to fail, resulting in a 10s delay before skipping the test.
However on GCC 4.7.2 on ppc64 at least it was seen that
the test failed erroneously due to the breakpoint being successfully
set on an "out of line" function, but an inline function was
actually being called.

* tests/tail-2/inotify-race.sh: Switch to a line based breakpoint,
rather than a symbol base one, which avoids issues with breakpoints
on inline functions.  Also skip_ on the initial breakpoint check
in case the breakpoint is not traversed which would be the case
on remote file systems for example.
</content>
</entry>
<entry>
<title>tail: use consistent diagnostics with and without inotify</title>
<updated>2013-12-09T09:26:17Z</updated>
<author>
<name>Pádraig Brady</name>
<email>P@draigBrady.com</email>
</author>
<published>2013-12-09T01:58:25Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=402e8ecbc4bf3b3fe866338e77e21feceac910f0'/>
<id>urn:sha1:402e8ecbc4bf3b3fe866338e77e21feceac910f0</id>
<content type='text'>
* src/tail.c: With inotify, when a file is initially absent,
we fstat(-1) for that file spec, thus recording an errnum of EBADF,
which caused the "has become accessible" diagnostic to be issued,
when the file first appears.  Instead we avoid the fstat(-1) and
thus emit the more natural and consistent "has appeared" diagnostic.
* tests/tail-2/retry.sh: Use the new diagnostic which also causes
this test to pass on systems without inotify.
</content>
</entry>
<entry>
<title>tests: avoid false df failure with nfs and lofs</title>
<updated>2013-12-09T09:24:24Z</updated>
<author>
<name>Bernhard Voelker</name>
<email>mail@bernhard-voelker.de</email>
</author>
<published>2013-12-09T01:03:56Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=4a6189a0ea0e49b542eb10ff3c9032145683ed63'/>
<id>urn:sha1:4a6189a0ea0e49b542eb10ff3c9032145683ed63</id>
<content type='text'>
* tests/df/total-unprocessed.sh: -t nfs and --local are
_not_ mutually exclusive on solaris, with lofs mounts.
</content>
</entry>
<entry>
<title>tests: avoid problematic $(&lt; file) shell construct</title>
<updated>2013-12-07T19:41:55Z</updated>
<author>
<name>Pádraig Brady</name>
<email>P@draigBrady.com</email>
</author>
<published>2013-12-07T15:36:33Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=0917c0c345f5e3c8856e3f59177b58608c21c6ea'/>
<id>urn:sha1:0917c0c345f5e3c8856e3f59177b58608c21c6ea</id>
<content type='text'>
* tests/cp/link-deref.sh: This was seen to cause an issue
with dash v0.5.6 at least, so change to a simpler expression.
</content>
</entry>
</feed>
