Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Failed tests of zsh 4.3.5 in Solaris 10 w/Sun Studio 12 CC
- X-seq: zsh-workers 24601
- From: Dagobert Michelsen <dam@xxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: Failed tests of zsh 4.3.5 in Solaris 10 w/Sun Studio 12 CC
- Date: Tue, 26 Feb 2008 20:47:23 +0100
- In-reply-to: <3C810A28-FD80-4DE3-9E70-E48F35DB2525@xxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <8AABEECB-A9A6-43EA-BED2-4BE376CBE349@xxxxxxxxxxxxx> <20080226141459.76dc362c@news01> <BD1EA7D6-C784-4ED9-9558-5B655CBC5096@xxxxxxxxxxxxx> <20080226145741.6e74fc22@news01> <656429B3-438B-4ECF-85C4-04E38D837D1A@xxxxxxxxxxxxx> <200802261610.m1QGAwJ3008939@xxxxxxxxxxxxxx> <20080226180807.10cd1476@news01> <3C810A28-FD80-4DE3-9E70-E48F35DB2525@xxxxxxxxxxxxx>
Hi all,
Am 26.02.2008 um 20:19 schrieb Dagobert Michelsen:
Do you have a clue about the other failing tests?
The testsuite now runs fine with my fix for the last fix
with the exception of one remaining failing test:
thor% ZTST_verbose=1 gmake TESTNUM=C02 check
if test -n "cc"; then \
cd .. && DESTDIR= \
gmake MODDIR=`pwd`/Test/Modules install.modules > /dev/
null; \
fi
if ZTST_testlist="`for f in ./C02*.ztst; \
do echo $f; done`" \
ZTST_srcdir="." \
ZTST_exe=../Src/zsh \
../Src/zsh +Z -f ./runtests.zsh; then \
stat=0; \
else \
stat=1; \
fi; \
rm -rf Modules .zcompdump; \
exit $stat
./C02cond.ztst: starting.
Running test: -a cond
Test successful.
Running test: -b cond
Test successful.
Running test: -c cond
Test successful.
Running test: -d cond
Test successful.
Running test: -e cond
Test successful.
Running test: -f cond
Test successful.
Running test: -g cond
Test successful.
Running test: -h cond
Test successful.
Running test: -k cond
Test successful.
Running test: -n cond
Test successful.
Running test: -o cond
Test successful.
Running test: -p cond
Test successful.
Running test: -r cond
Test successful.
Running test: -s cond
Test successful.
Running test: -u cond
Test successful.
Running test: -x cond
Test successful.
Running test: -z cond
Test successful.
Running test: -L cond
Test successful.
Running test: -O cond
Test successful.
Running test: -G cond
Test successful.
Running test: -N cond
Warning: not testing [[ -N file ]] (not supported with NFS)
Test successful.
Running test: -nt cond
Test ./C02cond.ztst failed: bad status 1, expected 0 from:
[[ newnewnew -nt zerolength && ! (unmodified -nt zerolength) ]]
Was testing: -nt cond
./C02cond.ztst: test failed.
**************************************
0 successful test scripts, 1 failure, 0 skipped
**************************************
gmake: *** [check] Error 1
I suspect this part here from C02cond.ztst:
# can't be bothered with -S
if [[ $OSTYPE == "cygwin" ]]; then
print -u$ZTST_fd "Warning: not testing [[ -N file ]] (not
supported on Cygwin)"
true
elif [[ "$(find . -prune -fstype nfs 2>/dev/null)" == "." ]]; then
print -u$ZTST_fd "Warning: not testing [[ -N file ]] (not
supported with NFS)"
true
else
print -u $ZTST_fd 'This test takes two seconds...'
sleep 2
cat unmodified
touch newnewnew
[[ -N newnewnew && ! -N unmodified ]]
fi
0:-N cond
F:This test can fail on NFS-mounted filesystems as the access and
F:modification times are not updated separately. The test will fail
F:on HFS+ (Apple Mac OS X default) filesystems because access times
F:are not recorded. Also, Linux ext3 filesystems may be mounted
F:with the noatime option which does not update access times.
F:Failures in these cases do not indicate a problem in the shell.
[[ newnewnew -nt zerolength && ! (unmodified -nt zerolength) ]]
0:-nt cond
If this is on NFS (which it is in my build environment) the
file 'newnewnew' is not generated and the following tests fail
instead of being skipped on NFS.
Best regards
-- Dagobert
Messages sorted by:
Reverse Date,
Date,
Thread,
Author