zsh-workers
 help / color / mirror / code / Atom feed
From: Dagobert Michelsen <dam@blastwave.org>
To: zsh-workers@sunsite.dk
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	[thread overview]
Message-ID: <36DDE5D8-3712-4184-9EAE-61ED914C70C2@blastwave.org> (raw)
In-Reply-To: <3C810A28-FD80-4DE3-9E70-E48F35DB2525@blastwave.org>

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


  reply	other threads:[~2008-02-26 19:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26 13:18 Dagobert Michelsen
2008-02-26 14:14 ` Peter Stephenson
2008-02-26 14:42   ` Dagobert Michelsen
2008-02-26 14:57     ` Peter Stephenson
2008-02-26 15:18       ` Dagobert Michelsen
2008-02-26 16:10         ` * " Peter Stephenson
2008-02-26 17:37           ` Oliver Kiddle
2008-02-27 11:29             ` Peter Stephenson
2008-02-27 16:16               ` Bart Schaefer
2008-02-29  9:53               ` Oliver Kiddle
2008-03-03 12:08                 ` Peter Stephenson
2008-03-03 12:43                   ` Dagobert Michelsen
2008-03-03 12:59                     ` Peter Stephenson
2008-02-26 18:08           ` Peter Stephenson
2008-02-26 18:12             ` İsmail Dönmez
2008-02-26 19:19             ` Dagobert Michelsen
2008-02-26 19:47               ` Dagobert Michelsen [this message]
2008-02-26 20:42                 ` Peter Stephenson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=36DDE5D8-3712-4184-9EAE-61ED914C70C2@blastwave.org \
    --to=dam@blastwave.org \
    --cc=zsh-workers@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).