From: Philipp Stephani <p.stephani2@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 47071@debbugs.gnu.org, Julian Scheid <jscheid@protonmail.com>
Subject: bug#47071: 28.0.50; Show ERT failure reason in batch mode
Date: Mon, 17 May 2021 17:52:46 +0200 [thread overview]
Message-ID: <CAArVCkTqA79fSoS=GaAAh5N5SSftzLJ7-EOLi2P0H5bLBHQYwQ@mail.gmail.com> (raw)
In-Reply-To: <87eee5idcd.fsf@gnus.org>
Am Mo., 17. Mai 2021 um 17:36 Uhr schrieb Lars Ingebrigtsen <larsi@gnus.org>:
>
> Julian Scheid <jscheid@protonmail.com> writes:
>
> > The data is only displayed in interactive mode as a side-effect
> > however, not in batch mode. I think it's useful to see the failure or
> > skip reason in batch mode as well, which is why I would like to
> > suggest the following change.
>
> Thanks, but I'm not sure this level of detail is helpful in batch mode.
>
> For instance, in python-tests, you get the wall of text included below,
> which I think would be excessive.
>
> Does anybody else have an opinion here?
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.
A middle ground would be to support some kind of 'verbosity'
command-line option so that the environment could decide how much to
print.
next prev parent reply other threads:[~2021-05-17 15:52 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 [this message]
2021-05-18 13:42 ` Lars Ingebrigtsen
2021-06-15 15:03 ` Lars Ingebrigtsen
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='CAArVCkTqA79fSoS=GaAAh5N5SSftzLJ7-EOLi2P0H5bLBHQYwQ@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=47071@debbugs.gnu.org \
--cc=jscheid@protonmail.com \
--cc=larsi@gnus.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.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).