zsh-workers
 help / color / mirror / code / Atom feed
From: Vin Shelton <shelton@icd.teradyne.com>
To: Peter Stephenson <pws@csr.com>
Cc: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: Test Failures
Date: Mon, 31 Mar 2003 16:59:10 -0500	[thread overview]
Message-ID: <545wuiffb9t.fsf@icd.teradyne.com> (raw)
In-Reply-To: <24740.1049106138@csr.com> (Peter Stephenson's message of "Mon, 31 Mar 2003 11:22:18 +0100")

Peter Stephenson <pws@csr.com> writes:
> Vin Shelton wrote:
>> > } ***************
>> > } *** 1,2 ****
>> > } - 1) one     2) two     3) three   
>> > }   input> input> 
>> > } --- 1 ----
>> > } Was testing: `select' loop
>> 
>> OK, FWIW, I see the failure on both Solaris 5.5 and 5.8 at work, and
>> on my linux box:
>
> Does normal select work?
Normal select works.  At least this script:

    #!/bin/sh
 
    # Execute this script under the Z shell
    [ ! -n "$ZSH_VERSION" ] && exec zsh -f "$0" ${1+"$@"}

    progname=${0:t}

    PROMPT3='Select prompt> '

    select choice in one two three
    do
      case $choice in
      (one|two|three)
        echo You chose $choice
        break
        ;;
      esac
    done

does the expected thing.

> If so, does it non-interactively send messages to stderr?
I'm not sure what you mean here.  When I run the script here is what
gets output to stderr:

    1) one    2) two    3) three  
    Select prompt> 


> Any sign of the missing message appearing on the terminal?
No.  I ran:
  ZTST_verbose=1 make TESTNUM=A01 check >out 2>err

Here is the contents of out:
    cd Test ; make check
    make[1]: Entering directory `/u/shelton2/software/build/SunOS-5.8/zsh-2003-03-31-1145/Test'
    if test -n "/opt/SUNWspro/bin/cc"; then \
      cd .. && DESTDIR= \
      make MODDIR=`pwd`/Test/Modules install.modules > /dev/null; \
    fi
    for f in /u/shelton2/software/src/zsh-2003-03-31-1145/Test/A01*.ztst; do \
      ../Src/zsh +Z -f /u/shelton2/software/src/zsh-2003-03-31-1145/Test/ztst.zsh $f; \
    done
    /u/shelton2/software/src/zsh-2003-03-31-1145/Test/A01grammar.ztst: starting.
    Running test: Basic pipeline handling
    Test successful.
    Running test: Exit status of pipeline with builtins (true)
    Test successful.
    Running test: Exit status of pipeline with builtins (false)
    Test successful.
    Running test: Basic coprocess handling
    Test successful.
    Running test: Basic sublist (i)
    Test successful.
    Running test: Basic sublist (ii)
    Test successful.
    Running test: Basic subshell list with error
    Test successful.
    Running test: Basic current shell list with error
    Test successful.
    Running test: `-' precommand modifier
    Test successful.
    Running test: `noglob' precommand modifier
    Test successful.
    Running test: `exec' precommand modifier
    Test successful.
    Running test: `command' precommand modifier
    Test successful.
    Running test: `builtin' precommand modifier
    Test successful.
    Running test: `if ...' (i)
    Test successful.
    Running test: `if ...' (ii)
    Test successful.
    Running test: `if ...' (iii)
    Test successful.
    Running test: `if ...' (iv)
    Test successful.
    Running test: `for' loop
    Test successful.
    Running test: `for' loop with newline before in keyword
    Test successful.
    Running test: arithmetic `for' loop
    Test successful.
    Running test: enhanced `for' syntax with two loop variables
    Test successful.
    Running test: enhanced `for' syntax with three loop variables
    Test successful.
    Running test: compatibility of enhanced `for' syntax with standard syntax
    Test successful.
    Running test: `while' loop
    Test successful.
    Running test: `until' loop
    Test successful.
    Running test: `repeat' loop
    Test successful.
    Running test: `case', old syntax
    Test successful.
    Running test: `case', new syntax
    Test successful.
    Running test: `case', new syntax, cascaded
    Test successful.
    Running test: `select' loop
    *** /tmp/zsh.ztst.err.5558	Mon Mar 31 16:33:24 2003
    --- /tmp/zsh.ztst.terr.5558	Mon Mar 31 16:33:24 2003
    ***************
    *** 1,2 ****
    ! 1) one     2) two     3) three   
      input> input> 
    --- 1,2 ----
    ! 1) one    2) two    3) three  
      input> input> 
    Test /u/shelton2/software/src/zsh-2003-03-31-1145/Test/A01grammar.ztst failed: error output differs from expected as shown above for:
      PS3="input> "
      select name in one two three; do
        print $name
      done
    Was testing: `select' loop
    /u/shelton2/software/src/zsh-2003-03-31-1145/Test/A01grammar.ztst: test failed.
    rm -rf Modules .zcompdump
    make[1]: Leaving directory `/u/shelton2/software/build/SunOS-5.8/zsh-2003-03-31-1145/Test'

Here is the contents of err:
    mkdir /u/shelton2/software/build/SunOS-5.8/zsh-2003-03-31-1145/Test/Modules
    mkdir /u/shelton2/software/build/SunOS-5.8/zsh-2003-03-31-1145/Test/Modules/zsh
    mkdir /u/shelton2/software/build/SunOS-5.8/zsh-2003-03-31-1145/Test/Modules/zsh/net
    make[1]: [check] Error 1 (ignored)

and nothing was printed on the terminal.  It looks to me that the only
difference is that there are extra spaces in the first line:
'one     ' vs. 'one    ',
'two     ' vs. 'two    ' and
'three   ' vs. 'three  '.


  - Vin


  reply	other threads:[~2003-03-31 21:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-28 20:24 Vin Shelton
2003-03-30 18:59 ` Bart Schaefer
2003-03-30 20:08   ` Vin Shelton
2003-03-31 10:22     ` Peter Stephenson
2003-03-31 21:59       ` Vin Shelton [this message]
2003-04-01  9:52         ` Peter Stephenson
2003-04-01 13:37           ` Vin Shelton
  -- strict thread matches above, loose matches on Subject: below --
2003-09-25  1:29 Vin Shelton
2003-09-25  4:06 ` Bart Schaefer
2003-09-25  7:38   ` Wayne Davison
2003-09-25  9:39     ` Peter Stephenson
2000-05-03  5:33 Test failures Felix Rosencrantz

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=545wuiffb9t.fsf@icd.teradyne.com \
    --to=shelton@icd.teradyne.com \
    --cc=pws@csr.com \
    --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).