From: Peter Stephenson <p.stephenson@samsung.com>
To: <zsh-workers@zsh.org>
Subject: Re: A05 test failure: bad interpreter: x*xn
Date: Fri, 14 Sep 2018 09:10:03 +0100 [thread overview]
Message-ID: <20180914081005eucas1p16fcae70c03fe677d424edddd06c2250e~UNd8jFAPy1658516585eucas1p1Q@eucas1p1.samsung.com> (raw)
In-Reply-To: <20180914040412.GA50246@CptOrmolo.darkstar>
On Thu, 13 Sep 2018 23:04:13 -0500
Matthew Martin <phy1729@gmail.com> wrote:
> When running tests on OpenBSD A05 fails with the below message. It seems
> to be testing for an OS dependant error string and exit code.
Yes, that's not going to work. I missed that.
Let's just stick with non-zero status.
pws
diff --git a/Test/A05execution.ztst b/Test/A05execution.ztst
index 567bd25..5d3d460 100644
--- a/Test/A05execution.ztst
+++ b/Test/A05execution.ztst
@@ -52,12 +52,17 @@
0:path (4)
*>foo */command.tmp/tstcmd-arg
- path=($shpath $echopath ${ZTST_testdir}/command.tmp/)
- tstcmd-interp-too-long 2>&1; echo "status $?"
- path=($storepath)
-0:path (5)
-*>*tstcmd-interp-too-long: bad interpreter: x*xn: no such file or directory
->status 127
+ # Just check this exits with non-zero status,
+ # as output and status code can differ.
+ (
+ path=($shpath $echopath ${ZTST_testdir}/command.tmp/)
+ if tstcmd-interp-too-long >/dev/null 2>&1; then
+ exit 0
+ else
+ exit 1
+ fi
+ )
+1:path (5)
functst() { print $# arguments:; print -l $*; }
functst "Eines Morgens" "als Gregor Samsa"
prev parent reply other threads:[~2018-09-14 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180914040455epcas3p388a45a226343370c8e41c7161fa841a9@epcas3p3.samsung.com>
2018-09-14 4:04 ` Matthew Martin
2018-09-14 8:10 ` 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='20180914081005eucas1p16fcae70c03fe677d424edddd06c2250e~UNd8jFAPy1658516585eucas1p1Q@eucas1p1.samsung.com' \
--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).