From: Bart Schaefer <schaefer@brasslantern.com>
To: "Zsh Users" <zsh-users@zsh.org>
Subject: Re: 5.0.2-test-2 is available
Date: Mon, 02 Dec 2013 07:21:13 -0800 [thread overview]
Message-ID: <131202072113.ZM3133@torch.brasslantern.com> (raw)
In-Reply-To: <20131202151557.1636@binki>
On Dec 2, 3:15pm, d.henman wrote:
}
} These failures commonly occur on Cygwin, but I still use zsh. I guess
} I don't use the features relavent to the failed tests. But, I would
} like to remove as many failures as possible. If you can spot anything
} in the below that can be fixed in a manner that works on Cygwin would
} be good,
Well ...
} Test ./X02zlevi.ztst failed: non-zero status from preparation code:
} Test ./Y01completion.ztst failed: non-zero status from preparation code:
} Test ./Y01completion.ztst failed: bad status 1, expected 0 from:
} Test ./Y02compmatch.ztst failed: non-zero status from preparation code:
My best guess is that this means "comptestinit" is failing, because
later ...
} (eval):1: command not found: test_code
} (eval):1: command not found: tst_arguments
... and both of those are functions defined only when comptestinit has
succeeded.
So you could try to figure out why comptestinit fails, perhaps by adding
a "setopt xtrace" into Test/comptest, but really those tests should be
skipped if their environment can't be initialized.
--
Barton E. Schaefer
next prev parent reply other threads:[~2013-12-02 15:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-01 19:46 Peter Stephenson
2013-12-02 6:15 ` d.henman
2013-12-02 9:34 ` Peter Stephenson
2013-12-02 15:21 ` Bart Schaefer [this message]
2013-12-02 15:15 ` Axel Beckert
2013-12-02 15:51 ` Test suite failures on static build (was: 5.0.2-test-2 is available) Axel Beckert
2013-12-02 16:01 ` Peter Stephenson
2013-12-09 9:51 ` 5.0.2-test-2 is available İsmail Dönmez
2013-12-09 9:53 ` İsmail Dönmez
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=131202072113.ZM3133@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-users@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).