unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Herring, Davis" <herring@lanl.gov>
To: "Clément Pit-Claudel" <cpitclaudel@gmail.com>,
	"Noam Postavsky" <npostavs@users.sourceforge.net>
Cc: Eli Zaretskii <eliz@gnu.org>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: Bisecting display bugs
Date: Mon, 17 Apr 2017 13:13:39 +0000	[thread overview]
Message-ID: <1492434819178.56131@lanl.gov> (raw)
In-Reply-To: <cce243fc-28ac-48e3-c1c5-f9c13ffdcbc9@gmail.com>

>> +    src/emacs -Q -l "../reproduce-the-bug.el" || exit 125
>>
>> Wouldn't this exit with status 125 if "../reproduce-the-bug.el" exits
>> with status 1?
> 
> You're right, thanks; it seems this || exit 125 is superfluous.

The status 125 means "cannot be tested" (due to unrelated build failure or similar).  If you have a script that produces a meaningful exit code, then of course you don't want it.  It might be good to have the reproducer exit with some value other than EXIT_FAILURE==1 and have the script do something like

src/emacs -Q -l ../reproduce.el
if [ $? -eq 1 ]; then exit 125; else exit $?; done

so that other Emacs failures do register as "skip".

Davis



  reply	other threads:[~2017-04-17 13:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-10 23:55 Bisecting display bugs Clément Pit--Claudel
2016-07-11  1:40 ` Óscar Fuentes
2016-07-11 14:22 ` Eli Zaretskii
2016-07-11 17:46   ` Óscar Fuentes
2016-07-11 17:54     ` Eli Zaretskii
2016-07-11 18:05       ` Óscar Fuentes
2016-07-22 18:55   ` Clément Pit--Claudel
2016-07-23  8:51     ` Eli Zaretskii
2016-07-23 13:22       ` Clément Pit--Claudel
2017-04-16 15:04         ` Clément Pit--Claudel
2017-04-16 15:32           ` Noam Postavsky
2017-04-16 20:57             ` Clément Pit-Claudel
2017-04-17 13:13               ` Herring, Davis [this message]
2017-04-17 13:43                 ` Teemu Likonen

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: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1492434819178.56131@lanl.gov \
    --to=herring@lanl.gov \
    --cc=cpitclaudel@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=npostavs@users.sourceforge.net \
    /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.savannah.gnu.org/cgit/emacs.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).