From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: Strange function/pipestatus behavior, maybe a scope bug?
Date: Thu, 24 Oct 2013 17:25:50 +0100 [thread overview]
Message-ID: <20131024172550.1baffa15@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <8D69ECD8-E5BD-4319-8352-7BDFDA49FF27@kba.biglobe.ne.jp>
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
prev parent reply other threads:[~2013-10-24 16:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 18:03 Ian F
2013-10-23 8:21 ` Peter Stephenson
2013-10-23 19:49 ` Ian F
2013-10-23 21:14 ` Peter Stephenson
2013-10-24 5:15 ` Bart Schaefer
2013-10-24 8:57 ` Peter Stephenson
2013-10-24 15:48 ` Peter Stephenson
2013-10-24 16:03 ` Peter Stephenson
2013-10-24 16:44 ` Bart Schaefer
2013-10-24 16:39 ` Bart Schaefer
2013-10-24 16:26 ` Bart Schaefer
2013-10-24 16:46 ` Peter Stephenson
2013-10-25 0:38 ` Bart Schaefer
2013-10-24 15:17 ` Jun T.
2013-10-24 16:25 ` Peter Stephenson [this message]
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=20131024172550.1baffa15@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.com \
--cc=zsh-workers@zsh.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 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).