emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#11424: closed (coreutils: split tests hang on /dev


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#11424: closed (coreutils: split tests hang on /dev/zero on GNU/Hurd)
Date: Tue, 08 May 2012 09:22:02 +0000

Your message dated Tue, 08 May 2012 11:19:50 +0200
with message-id <address@hidden>
and subject line Re: bug#11424: coreutils: split tests hang on /dev/zero on 
GNU/Hurd
has caused the debbugs.gnu.org bug report #11424,
regarding coreutils: split tests hang on /dev/zero on GNU/Hurd
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
11424: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=11424
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: coreutils: split tests hang on /dev/zero on GNU/Hurd Date: Mon, 7 May 2012 02:55:51 +0200 User-agent: Mutt/1.5.21+34 (58baf7c9f32f) (2010-12-30)
Hello,

Since some time, coreutils fails in split tests on GNU/Hurd. More
precisely, these two:

split/filter:55
split --filter="head -c1 >/dev/null" -n 1 /dev/zero

split/l-chunk:39
split -n l/2 /dev/zero

It seems that these two tests assume that split will stop by itself when
given /dev/zero as input.  It does so on Linux, because /dev/zero there
has stat_buf.st_size equal to 0, and thus split does just one loop, but
on GNU/Hurd /dev/zero has stat_buf.st_size equal to LONG_MAX, and thus
split just loops for a very long time.  Posix doesn't seem to talk much
about what should be done here, but it seems to me that coreutils tests
should not assume size being zero, and for instance use dd to fetch only
the required bytes from /dev/zero.

Samuel



--- End Message ---
--- Begin Message --- Subject: Re: bug#11424: coreutils: split tests hang on /dev/zero on GNU/Hurd Date: Tue, 08 May 2012 11:19:50 +0200
Jim Meyering wrote:
>> Paul Eggert wrote:
...
> I went ahead and pushed the less-invasive fix.
> Your behavior-changing one is more than welcome, too.

Samuel confirmed that the fix solved his problem, so
I've marked this as closed.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]