unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Julian Scheid <jscheid@protonmail.com>
Cc: 47071@debbugs.gnu.org
Subject: bug#47071: 28.0.50; Show ERT failure reason in batch mode
Date: Mon, 17 May 2021 17:34:10 +0200	[thread overview]
Message-ID: <87eee5idcd.fsf@gnus.org> (raw)
In-Reply-To: <m2a6rarmyi.fsf@julians-mbp-16.lan> (Julian Scheid's message of "Thu, 11 Mar 2021 10:42:19 +0000")

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?

14 skipped results:
  SKIPPED  python-shell-get-process-1  ((skip-unless (executable-find python-tests-shell-interpreter)) :form (executable-find "python") :value nil)
  SKIPPED  python-shell-internal-get-or-create-process-1  ((skip-unless (executable-find python-tests-shell-interpreter)) :form (executable-find "python") :value nil)
  SKIPPED  python-shell-make-comint-1  ((skip-unless (executable-find python-tests-shell-interpreter)) :form (executable-find "python") :value nil)
  SKIPPED  python-shell-make-comint-2  ((skip-unless (executable-find python-tests-shell-interpreter)) :form (executable-find "python") :value nil)
  SKIPPED  python-shell-make-comint-3  ((skip-unless (executable-find python-tests-shell-interpreter)) :form (executable-find "python") :value nil)
  SKIPPED  python-shell-make-comint-4  ((skip-unless (executable-find python-tests-shell-interpreter)) :form (executable-find "python") :value nil)
  SKIPPED  python-shell-prompt-detect-1  ((skip-unless (executable-find python-tests-shell-interpreter)) :form (executable-find "python") :value nil)
  SKIPPED  python-shell-prompt-detect-2  ((skip-unless (executable-find python-tests-shell-interpreter)) :form (executable-find "python") :value nil)
  SKIPPED  python-shell-prompt-detect-3  ((skip-unless (executable-find python-tests-shell-interpreter)) :form (executable-find "python") :value nil)
  SKIPPED  python-shell-prompt-detect-4  ((skip-unless (executable-find python-tests-shell-interpreter)) :form (executable-find "python") :value nil)
  SKIPPED  python-shell-prompt-detect-5  ((skip-unless (executable-find python-tests-shell-interpreter)) :form (executable-find "python") :value nil)
  SKIPPED  python-shell-prompt-detect-6  ((skip-unless (executable-find python-tests-shell-interpreter)) :form (executable-find "python") :value nil)
  SKIPPED  python-shell-prompt-set-calculated-regexps-6  ((skip-unless (executable-find python-tests-shell-interpreter)) :form (executable-find "python") :value nil)
  SKIPPED  python-tests--bug31398  ((skip-unless (executable-find python-tests-shell-interpreter)) :form (executable-find "python") :value nil)


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





  reply	other threads:[~2021-05-17 15:34 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 [this message]
2021-05-17 15:52   ` Philipp Stephani
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=87eee5idcd.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=47071@debbugs.gnu.org \
    --cc=jscheid@protonmail.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).