From: Jeff King <peff@peff.net>
To: Eric Wong <e@80x24.org>
Cc: "Jonathan Nieder" <jrnieder@gmail.com>,
"Randall S. Becker" <rsbecker@nexbridge.com>,
git@vger.kernel.org,
"'Joachim Schmitz'" <jojo@schmitz-digital.de>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: [Problem] test_must_fail makes possibly questionable assumptions about exit_code.
Date: Wed, 28 Feb 2018 02:49:18 -0500 [thread overview]
Message-ID: <20180228074918.GA32127@sigill.intra.peff.net> (raw)
In-Reply-To: <20180228074251.GA11673@dcvr>
On Wed, Feb 28, 2018 at 07:42:51AM +0000, Eric Wong wrote:
> > > > a) We could override the meaning of die() in Git.pm. This feels
> > > > ugly but if it works, it would be a very small patch.
> > >
> > > Unlikely to work since I think we use eval {} to trap exceptions
> > > from die.
> > >
> > > > b) We could forbid use of die() and use some git_die() instead (but
> > > > with a better name) for our own error handling.
> > >
> > > Call sites may be dual-use: "die" can either be caught by an
> > > eval or used to show an error message to the user.
>
> <snip>
>
> > > > d) We could wrap each command in an eval {...} block to convert the
> > > > result from die() to exit 128.
> > >
> > > I prefer option d)
> >
> > FWIW, I agree with all of that. You can do (d) without an enclosing eval
> > block by just hooking the __DIE__ handler, like:
> >
> > $SIG{__DIE__} = sub {
> > print STDERR "fatal: @_\n";
> > exit 128;
> > };
>
> Looks like it has the same problems I pointed out with a) and b).
You're right. I cut down my example too much and dropped the necessary
eval magic. Try this:
-- >8 --
SIG{__DIE__} = sub {
CORE::die @_ if $^S || !defined($^S);
print STDERR "fatal: @_";
exit 128;
};
eval {
die "inside eval";
};
print "eval status: $@" if $@;
die "outside eval";
-- 8< --
Running that should produce:
$ perl foo.pl; echo $?
eval status: inside eval at foo.pl line 8.
fatal: outside eval at foo.pl line 12.
128
It may be getting a little too black-magic, though. Embedding in an eval
is at least straightforward, if a bit more invasive.
-Peff
next prev parent reply other threads:[~2018-02-28 7:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 23:50 [Problem] test_must_fail makes possibly questionable assumptions about exit_code Randall S. Becker
2018-02-28 0:16 ` Jonathan Nieder
2018-02-28 4:07 ` Eric Wong
2018-02-28 5:00 ` Jeff King
2018-02-28 7:42 ` Eric Wong
2018-02-28 7:49 ` Jeff King [this message]
2018-02-28 14:55 ` Randall S. Becker
2018-02-28 16:51 ` demerphq
2018-03-01 7:36 ` Jeff King
2018-03-01 8:16 ` demerphq
2018-03-01 14:28 ` Randall S. Becker
2018-03-01 15:08 ` Jeff King
2018-03-01 15:30 ` demerphq
2018-02-28 16:22 ` Junio C Hamano
2018-02-28 16:46 ` demerphq
2018-02-28 17:10 ` Randall S. Becker
2018-02-28 17:19 ` demerphq
2018-02-28 17:20 ` demerphq
2018-02-28 17:32 ` Randall S. Becker
2018-02-28 17:44 ` Jonathan Nieder
2018-02-28 18:21 ` Randall S. Becker
2018-02-28 18:51 ` Jonathan Nieder
2018-02-28 20:04 ` Randall S. Becker
2018-02-28 22:02 ` Randall S. Becker
2018-02-28 23:16 ` Jonathan Nieder
2018-03-01 7:34 ` Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180228074918.GA32127@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=avarab@gmail.com \
--cc=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=jojo@schmitz-digital.de \
--cc=jrnieder@gmail.com \
--cc=rsbecker@nexbridge.com \
/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://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).