all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 22420@debbugs.gnu.org
Subject: bug#22420: Zsh test failure
Date: Fri, 22 Jan 2016 14:33:44 -0500	[thread overview]
Message-ID: <20160122193344.GB20936@jasmine> (raw)
In-Reply-To: <87r3h933ri.fsf@gnu.org>

On Fri, Jan 22, 2016 at 06:47:29PM +0100, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
> 
> >> > I have confirmed the failure is in 'Test/B02typeset.ztst'.
> >> 
> >> Could you post the relevant part of the build log?
> >
> > Here is the verbose output of only the B02 test:
> > http://paste.debian.net/367077/
> 
> It finishes with:
> 
> --8<---------------cut here---------------start------------->8---
> 2221 Test successful.                                                                                                 
> 2222 ZTST_test: looking for new test                                                                                  
> 2223 ZTST_test: examining line:                                                                                       
> 2224                                                                                                                  
> 2225 ZTST_test: all tests successful                                                                                  
> 2226 ./ztst.zsh:550: unmatched "                                                                                      
> --8<---------------cut here---------------end--------------->8---
> 
> Could it be that the unmatched " is the root cause?  I don’t see any
> clear sign of an error or failure other than that.
> 
> Could you check what’s in that file on line 550?

It's only 543 lines long! :o

I guess I'll try tracing the script.

I thought that perhaps it was referring to B02typeset.ztst, but I don't
think there is anything related in that area of the file:
540   (
541   setopt glob
542   mkdir -p arrayglob
543   touch arrayglob/{one,two,three,four,five,six,seven}
544   fn() {
545     typeset array=(arrayglob/[tf]*)
546     print -l ${array:t}
547     #
548     typeset {first,second,third}=the_same_value array=(
549     extends
550     over
551     multiple
552     lines
553     )
554     print -l $first $second $third "$array"
555     #
556     integer i=$(echo 1 + 2 + 3 + 4)
557     print $i
558     #
559     # only noted by accident this was broken..
560     # we need to turn off special recognition
561     # of assignments within assignments...
562     typeset careful=( i=1 j=2 k=3 )
563     print -l $careful
564   }

> 
> My 2¢.
> 
> Ludo’.

  reply	other threads:[~2016-01-22 19:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-21  2:21 bug#22420: Zsh test failure Leo Famulari
2016-01-21 21:02 ` Ludovic Courtès
2016-01-21 23:05   ` Leo Famulari
2016-01-22 15:04     ` Ludovic Courtès
2016-01-22 16:30       ` Leo Famulari
2016-01-22 17:47         ` Ludovic Courtès
2016-01-22 19:33           ` Leo Famulari [this message]
2016-01-22 20:34             ` Ludovic Courtès
2016-01-22 20:38               ` Leo Famulari
2016-01-22 20:43                 ` Leo Famulari
2016-01-23 10:51                   ` Ludovic Courtès
2016-01-21 22:20 ` Leo Famulari
2016-01-21 23:14   ` Leo Famulari
2018-09-10  0:10 ` Leo Famulari

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=20160122193344.GB20936@jasmine \
    --to=leo@famulari.name \
    --cc=22420@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.