From: Eli Zaretskii <eliz@gnu.org>
To: phillip.lord@russet.org.uk (Phillip Lord)
Cc: 22471@debbugs.gnu.org
Subject: bug#22471: ert batch should print compile parsable error messages
Date: Wed, 27 Jan 2016 18:06:04 +0200 [thread overview]
Message-ID: <83pownyplf.fsf@gnu.org> (raw)
In-Reply-To: <87bn878jsv.fsf@russet.org.uk> (phillip.lord@russet.org.uk)
> From: phillip.lord@russet.org.uk (Phillip Lord)
> Date: Wed, 27 Jan 2016 09:15:44 +0000
>
>
> Currently, when running in batch, ert prints out messages like so:
>
>
> Running 24 tests (2016-01-27 09:05:17+0000)
> passed 1/24 buffer-string=
> passed 2/24 buffer=
> ...
> passed 22/24 sisyphus-test-with-find-file
> passed 23/24 to-string
> passed 24/24 with-temp-buffers
>
> Ran 24 tests, 23 results as expected, 1 unexpected (2016-01-27 09:05:18+0000)
>
> 1 unexpected results:
> FAILED crash-out
>
> It would be nice to add some compilation-mode parsable data to this. So,
> something like
>
>
> passed 1/24 buffer-string= (in ./test.sisyphus-test.el:22:)
FWIW, I have never seen a test suite that displayed in
compilation-mode compatible format. If we do that (and I'm
necessarily opposed to that), we'd be the odd one out, I think.
next prev parent reply other threads:[~2016-01-27 16:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 9:15 bug#22471: ert batch should print compile parsable error messages Phillip Lord
2016-01-27 16:06 ` Eli Zaretskii [this message]
2016-01-27 21:53 ` Phillip Lord
2016-01-28 1:28 ` Glenn Morris
2016-01-28 17:14 ` Phillip Lord
2020-08-20 16:39 ` Lars Ingebrigtsen
2020-08-20 16:51 ` Philipp Stephani
2021-10-23 0:15 ` Stefan Kangas
2021-10-24 12:57 ` Lars Ingebrigtsen
2021-10-24 14:27 ` Stefan Kangas
2021-10-24 20:01 ` Lars Ingebrigtsen
2022-01-24 12:54 ` 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=83pownyplf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22471@debbugs.gnu.org \
--cc=phillip.lord@russet.org.uk \
/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).