unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 47071@debbugs.gnu.org, Julian Scheid <jscheid@protonmail.com>
Subject: bug#47071: 28.0.50; Show ERT failure reason in batch mode
Date: Tue, 15 Jun 2021 17:03:00 +0200	[thread overview]
Message-ID: <87bl87tbkr.fsf@gnus.org> (raw)
In-Reply-To: <87mtssf9at.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 18 May 2021 15:42:02 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

>> On CI systems, you only have the logs written in batch mode. The more
>> complete they are, the better, since you can always filter out
>> information you don't need later, but not add missing information
>> after the fact. So printing lots of information is fine IMO.
>
> Yeah, that's true -- on CI systems the added information would be useful
> indeed. 
>
>> A middle ground would be to support some kind of 'verbosity'
>> command-line option so that the environment could decide how much to
>> print.
>
> Yup.

I went with an environment variable to control this -- that seemed the
most flexible way here.  Feel free to tweak or change the name of the
variable.

Julian -- I pushed your patch to Emacs 28 with those small changes.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2021-06-15 15:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 10:42 bug#47071: 28.0.50; Show ERT failure reason in batch mode Julian Scheid via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-17 15:34 ` Lars Ingebrigtsen
2021-05-17 15:52   ` Philipp Stephani
2021-05-18 13:42     ` Lars Ingebrigtsen
2021-06-15 15:03       ` Lars Ingebrigtsen [this message]

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=87bl87tbkr.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=47071@debbugs.gnu.org \
    --cc=jscheid@protonmail.com \
    --cc=p.stephani2@gmail.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://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).