From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-3.3 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_HI,T_RP_MATCHES_RCVD shortcircuit=no autolearn=ham autolearn_force=no version=3.4.0 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by dcvr.yhbt.net (Postfix) with ESMTP id 2938D1FAE2 for ; Wed, 28 Feb 2018 07:42:55 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751682AbeB1Hmw (ORCPT ); Wed, 28 Feb 2018 02:42:52 -0500 Received: from dcvr.yhbt.net ([64.71.152.64]:34684 "EHLO dcvr.yhbt.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751464AbeB1Hmw (ORCPT ); Wed, 28 Feb 2018 02:42:52 -0500 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id B99511F576; Wed, 28 Feb 2018 07:42:51 +0000 (UTC) Date: Wed, 28 Feb 2018 07:42:51 +0000 From: Eric Wong To: Jeff King Cc: Jonathan Nieder , "Randall S. Becker" , git@vger.kernel.org, 'Joachim Schmitz' , =?utf-8?B?w4Z2YXIgQXJuZmrDtnLDsA==?= Bjarmason Subject: Re: [Problem] test_must_fail makes possibly questionable assumptions about exit_code. Message-ID: <20180228074251.GA11673@dcvr> References: <005501d3b025$c0057ce0$401076a0$@nexbridge.com> <20180228001616.GJ174036@aiede.svl.corp.google.com> <20180228040718.GA9043@whir> <20180228050034.GA373@sigill.intra.peff.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20180228050034.GA373@sigill.intra.peff.net> Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Jeff King wrote: > On Wed, Feb 28, 2018 at 04:07:18AM +0000, Eric Wong wrote: > > > > In the rest of git, die() makes a command exit with status 128. The > > > trouble here is that our code in Perl is assuming the same meaning for > > > die() but using perl's die builtin instead. That suggests a few > > > options: > > > > > > 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. > > > 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).