[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#22471: ert batch should print compile parsable error messages
From: |
Philipp Stephani |
Subject: |
bug#22471: ert batch should print compile parsable error messages |
Date: |
Thu, 20 Aug 2020 18:51:32 +0200 |
Am Do., 20. Aug. 2020 um 18:41 Uhr schrieb Lars Ingebrigtsen <larsi@gnus.org>:
>
> phillip.lord@russet.org.uk (Phillip Lord) writes:
>
> > 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:)
>
> I think that would look rather cluttered for the "passed" lines, but it
> would indeed be helpful on the FAILED lines.
>
I'm doing something similar in my Bazel ruleset for Elisp
(https://github.com/phst/rules_elisp/blob/0b24aa1660af2f6c668899bdd78aaba383d7ac18/elisp/ert/runner.el#L446).
It would be nice to have an API for this as my code needs a few hacks
and subtleties.