From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-31884-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 11126 invoked by alias); 24 Oct 2013 16:25:59 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 31884
Received: (qmail 5932 invoked from network); 24 Oct 2013 16:25:54 -0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI,
	SPF_HELO_PASS autolearn=ham version=3.3.2
X-AuditID: cbfec7f5-b7ef66d00000795a-21-52694a0f8ecc
Date: Thu, 24 Oct 2013 17:25:50 +0100
From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: Strange function/pipestatus behavior, maybe a scope bug?
Message-id: <20131024172550.1baffa15@pwslap01u.europe.root.pri>
In-reply-to: <8D69ECD8-E5BD-4319-8352-7BDFDA49FF27@kba.biglobe.ne.jp>
References:
 <CAMeu-1WYhBr-hbcgXQy3gEGOSSpS2FFmxDa+QDFyN1m+7Z1kQA@mail.gmail.com>
 <20131023092155.5ba8a54b@pwslap01u.europe.root.pri>
 <CAMeu-1WsKO71YfJ+aO9uy=_oGLJEsKh-yL8HJ_rMicqmCj2FQw@mail.gmail.com>
 <20131023221412.5cdecd76@pws-pc.ntlworld.com>
 <131023221548.ZM2352@torch.brasslantern.com>
 <8D69ECD8-E5BD-4319-8352-7BDFDA49FF27@kba.biglobe.ne.jp>
Organization: Samsung Cambridge Solution Centre
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu)
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
X-Brightmail-Tracker:
 H4sIAAAAAAAAA+NgFuphluLIzCtJLcpLzFFi42I5/e/4VV1+r8wgg1uXTSwONj9kcmD0WHXw
	A1MAYxSXTUpqTmZZapG+XQJXxuIjLxgLmjkrZp5fytTAuIiti5GTQ0LAROLylXssELaYxIV7
	64HiXBxCAksZJQ49mc0K4Sxnknh2ppGxi5GDg0VAVaJ5UzZIA5uAocTUTbMZQWwRAXGJs2vP
	gw0SFnCVOHtnJlicV8BeYsbxm+wgNidQfP8ZkJmcQDNfMkk0XdUGsfkF9CWu/v3EBHGEvcTM
	K2egegUlfkyGOI5ZQEti87YmVghbXmLzmrfMExgFZiEpm4WkbBaSsgWMzKsYRVNLkwuKk9Jz
	jfSKE3OLS/PS9ZLzczcxQkLw6w7GpcesDjEKcDAq8fB+fJURJMSaWFZcmXuIUYKDWUmEd5pe
	ZpAQb0piZVVqUX58UWlOavEhRiYOTqkGxpkTrCtENtR1TG43dFxft+H+22ge9Ud9zWLfv6ev
	W5pvu6FBUmrfN1HhK58jmH7M37D5jHtw7ZNDO3/8NkoJm5tgfcP0+hF5lxD57fdPyKRKLjMx
	s2933yHR9C9nxdJLedMvpck2Se/5lCoh4J08p1MnUeugS/qUu9WHZuvdWzRHeQ1bg9yvdCWW
	4oxEQy3mouJEABtc7UUfAgAA

On Fri, 25 Oct 2013 00:17:38 +0900
"Jun T." <takimoto-j@kba.biglobe.ne.jp> wrote:
> On Mac OS X, A05execution.ztst fails as
> 
> *** 1 ****
> !    2048 0 0 0
> --- 1 ----
> ! 2048 0 0 0
> Test ./A05execution.ztst failed: output differs from expected as shown above for:
>   repeat 2048; do (: | : | while false; do
>                              break
>                            done;
>                    print "${pipestatus[@]}")
>     ZTST_hashmark
>   done | sort | uniq -c
> 
> i.e., number of spaces output by 'uniq -c' before the count is different.

diff --git a/Test/A05execution.ztst b/Test/A05execution.ztst
index c42e454..fd13e91 100644
--- a/Test/A05execution.ztst
+++ b/Test/A05execution.ztst
@@ -184,8 +184,8 @@
                            done;
                    print "${pipestatus[@]}")
 	ZTST_hashmark
-  done | sort | uniq -c
+  done | sort | uniq -c | sed 's/^ *//'
 0:Check whether `$pipestatus[]' behaves.
->   2048 0 0 0
+>2048 0 0 0
 F:This test checks for a bug in `$pipestatus[]' handling.  If it breaks then
 F:the bug is still there or it reappeared. See workers-29973 for details.

pws