[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Test Failures in coreutils-5.3.0 on SunOS-5.5.1
From: |
Vin Shelton |
Subject: |
Re: Test Failures in coreutils-5.3.0 on SunOS-5.5.1 |
Date: |
Mon, 10 Jan 2005 18:59:58 -0500 |
Jim Meyering <address@hidden> writes:
> Vin Shelton <address@hidden> wrote:
>> To whom it may concern:
>
> Thanks for the quick testing and report!
> What compiler did you use?
>
>> On a SunOS-5.5.1 system (uname -a reports:
>> SunOS boise 5.5.1 Generic_103640-40 sun4u sparc SUNW,Ultra-5_10 Solaris)
>> I'm getting the following test failures:
>>
>> FAIL: basic
>> FAIL: time-1
>
> The first two (above) are due to the fact that you
> built and ran the tests on a file system of type tmpfs
> that is particularly deficient. Please try to avoid it.
> Here's a relevant comment from the test output:
>
> failed ls ctime test -- this failure is expected at least for SunOS4.1.4
> and for tmpfs file systems on Solaris 5.5.1.
>
>> FAIL: nl
>
> I don't know about the above.
> Can you debug it to see where/how nl is getting the segfault?
>
>> FAIL: printf
>
> It looks like the above is failing because this command
> ./printf '5 % +d\n' 234
> outputs this:
> 5 +0
> rather than the expected:
> 5 +234
>
> Can you find out why?
>
>> FAIL: x8
>
> This od test failure is probably due to trouble involving
> the PRI*MAX macros or to the values of ULONG_MAX or ULLONG_MAX.
> It is probably using %l rather than %ll as the LONGEST_MODIFIER.
> You can investigate further by checking config.h for ULLONG_MAX.
> If that shows nothing defined, then please preprocess od.c with cpp
> and look for definitions there. E.g., do this:
>
> cd src && rm -f od.o
> make AM_CFLAGS='-E -dD' od.o && mv od.o od.i
>
> Then search od.i for those symbols:
>
> grep -E 'PRI.MAX|ULLONG_MAX' od.i
>
> I'll look at the following later.
>
>> FAIL: pr-tests
>> FAIL: ignore
>> FAIL: uniq-tests
Hi Jim!
Oddly enough, on the SunOS-5.8 system, I ran into problems with using
the NFS-mounted NetApp (or whatever the fileserve is), so I used /tmp
and got clean test results. I observed some failures under 5.5.1
using a NetApp-based filesystem, so I switched over to /tmp. On that
system, /tmp is a tmpfs filesystem.
Sorry for missing the warning about using tmpfs.
I was using the Solaris C compiler, version 4.2 if memory serves.
I'll check tomorrow.
- Vin
PS. Unfortunately, I do not control the system and thus cannot grant
you ssh access to the systems. I'll do what I can to debug the
problems, though.