From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 22471@debbugs.gnu.org, Phillip Lord <phillip.lord@russet.org.uk>
Subject: bug#22471: ert batch should print compile parsable error messages
Date: Sun, 24 Oct 2021 22:01:17 +0200 [thread overview]
Message-ID: <87y26i19bm.fsf@gnus.org> (raw)
In-Reply-To: <CADwFkmnDM-8161nYvW6FSCJyEnSZSLqPFpu37ap57Q_q5E5Ezg@mail.gmail.com> (Stefan Kangas's message of "Sun, 24 Oct 2021 07:27:31 -0700")
Stefan Kangas <stefan@marxist.se> writes:
> Right, I'm just wondering what has changed as presumably the patch
> worked when Phillip Lord first wrote it?
Oh, I interpreted the branch as a sketch towards a solution but I see
that he posted apparent output from it, too:
> I put a quick attempt at this up on feature/parsable-ert-output.
>
> passed 22/24 sisyphus-test-with-find-file at test/sisyphus-test.el
> line 277.
> passed 23/24 to-string at test/sisyphus-test.el line 96.
> passed 24/24 with-temp-buffers at test/sisyphus-test.el line 232.
So it worked at one point? (I'm not able to compile that branch at
all -- it segfaults while bootstrapping.)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-10-24 20:01 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
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 [this message]
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=87y26i19bm.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=22471@debbugs.gnu.org \
--cc=phillip.lord@russet.org.uk \
--cc=stefan@marxist.se \
/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).