[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: truncate-fail-diag failure on Solaris
From: |
Pádraig Brady |
Subject: |
Re: truncate-fail-diag failure on Solaris |
Date: |
Wed, 11 Jun 2008 01:30:04 +0100 |
User-agent: |
Thunderbird 2.0.0.6 (X11/20071008) |
Bruno Haible wrote:
> Building coreutils 6.12.29-a16be on Solaris 7, with gcc 3.2.2. It fails
> like this:
>
> =======================================================
> GNU coreutils 6.12.29-a16be: tests/test-suite.log
> =======================================================
>
> 1 of 344 tests failed. (42 tests were not run).
>
> FAIL: misc/truncate-fail-diag.log (exit: 1)
> ===========================================
> The problem is that "truncate -s0 no/" creates a zero-sized file named 'no'
> and returns with exit code 0, but the test expects a failure.
eek. I'm surprised that solaris 7 creates a file when one specifies the
trailing /
Solaris 10 gives an ENOTDIR error, while linux gives an EISDIR error.
I'm not sure what to do in this case. Probably just remove the second
truncate test in that file altogether.
thanks,
Pádraig.
- truncate-fail-diag failure on Solaris, Bruno Haible, 2008/06/10
- Re: truncate-fail-diag failure on Solaris,
Pádraig Brady <=
- Re: truncate-fail-diag failure on Solaris, Bruno Haible, 2008/06/10
- Re: truncate-fail-diag failure on Solaris, Jim Meyering, 2008/06/11
- Re: truncate-fail-diag failure on Solaris, Bruno Haible, 2008/06/11
- Re: truncate-fail-diag failure on Solaris, Jim Meyering, 2008/06/12
- Re: truncate-fail-diag failure on Solaris, Bruno Haible, 2008/06/12
- Re: truncate-fail-diag failure on Solaris, Jim Meyering, 2008/06/12