From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: zsh-workers@zsh.org
Subject: Re: Skipping gdbm test
Date: Fri, 3 Mar 2017 09:55:15 +0000 [thread overview]
Message-ID: <20170303095515.GA3953@fujitsu.shahaf.local2> (raw)
In-Reply-To: <20170303091902.6fb98763@pwslap01u.europe.root.pri>
Peter Stephenson wrote on Fri, Mar 03, 2017 at 09:19:02 +0000:
> On Thu, 02 Mar 2017 08:17:44 -0800
> Sebastian Gniazdowski <psprint3@fastmail.com> wrote:
> > Maybe the skip could be done more quiet? I've followed V10private.tst,
> > but that module is easily built. Checked that in %prep path to gdbm
> > module file is: Modules/zsh/db/gdbm.so
>
> I don't think it's a problem. Skipping is common within tests, too,
> depending on system features. It's just when something changes that
> people notice.
I think the proposal was to removal lines 2,3 but keep lines 1,4:
>>>> 1 /opt/src/zsh-2017-03-01/Test/V11db_gdbm.ztst: starting.
>>>> 2 (eval):3: failed to load module `zsh/db/gdbm':
>>>> 3 /opt/build/zsh-2017-03-01/Test/Modules/zsh/db/gdbm.so: cannot open shared object file: No such file or directory
>>>> 4 /opt/src/zsh-2017-03-01/Test/V11db_gdbm.ztst: skipped (can't load zsh/db/gdbm module for testing)
Personally I think it'd be good to hide that particular
error message; line 4 tells the user what he needs to know.
CHeers,
Daniel
next prev parent reply other threads:[~2017-03-03 10:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170302145932epcas5p18f7477866f38d8bbc75a640afffa04cd@epcas5p1.samsung.com>
2017-03-01 19:41 ` Vin Shelton
2017-03-02 15:05 ` Peter Stephenson
2017-03-02 16:17 ` Sebastian Gniazdowski
2017-03-03 9:19 ` Peter Stephenson
2017-03-03 9:55 ` Daniel Shahaf [this message]
2017-03-03 10:14 ` Peter Stephenson
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=20170303095515.GA3953@fujitsu.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--cc=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).