From: Stefan Kangas <stefankangas@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>,
Matt Armstrong <matt@rfc20.org>
Cc: 59317@debbugs.gnu.org
Subject: bug#59317: 29.0.50; Feature idea: suppress `message' output in ert batch test output
Date: Thu, 17 Nov 2022 02:49:10 -0800 [thread overview]
Message-ID: <CADwFkmk+FEJ_k_UBQ6RLztyEAMsdMd5cNamrEOYK-g4DLjos1A@mail.gmail.com> (raw)
In-Reply-To: <871qq1yijz.fsf@gmx.de>
Michael Albinus <michael.albinus@gmx.de> writes:
> Besides the other arguments already given in this thread, I'd like to
> emphasize that messages are useful even in batch mode, for successful
> tests. This is the only way to study ert tests in batch mode, for
> example on our CI/CD machines hydra and emba.
It would be less than useful in CI, indeed.
But in interactive sessions, and when running tests manually with
e.g. M-x compile, it helps to have less noise, to find the relevant
failures faster.
> If messages shall be suppressed, this must be controlled by a user
> option. However, I'm not in favor to do it at all.
Agreed. Perhaps an environment variable could also be provided, so that
it is easier to control from the command line?
next prev parent reply other threads:[~2022-11-17 10:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 18:52 bug#59317: 29.0.50; Feature idea: suppress `message' output in ert batch test output Matt Armstrong
2022-11-16 19:54 ` Eli Zaretskii
2022-11-17 0:12 ` Stefan Kangas
2022-11-17 6:06 ` Matt Armstrong
2022-11-17 6:39 ` Eli Zaretskii
2022-11-17 7:28 ` Stefan Kangas
2022-11-17 5:51 ` Matt Armstrong
2022-11-17 7:13 ` Eli Zaretskii
2022-11-17 10:36 ` Michael Albinus
2022-11-17 10:49 ` Stefan Kangas [this message]
2022-11-17 12:35 ` Michael Albinus
2022-11-18 0:12 ` Matt Armstrong
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=CADwFkmk+FEJ_k_UBQ6RLztyEAMsdMd5cNamrEOYK-g4DLjos1A@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=59317@debbugs.gnu.org \
--cc=matt@rfc20.org \
--cc=michael.albinus@gmx.de \
/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).