From: Alan Mackenzie <acm@muc.de>
To: chad <yandros@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: make check produces 25 failures and hangs (bug #65176).
Date: Thu, 10 Aug 2023 20:34:29 +0000 [thread overview]
Message-ID: <ZNVJ1ZTaOntwr2CZ@ACM> (raw)
In-Reply-To: <ZNVFMIadTs0tUhBq@ACM>
Hello again, Chad.
On Thu, Aug 10, 2023 at 20:14:40 +0000, Alan Mackenzie wrote:
> On Thu, Aug 10, 2023 at 15:54:26 -0400, chad wrote:
> > On Thu, Aug 10, 2023 at 3:19â¯PM Alan Mackenzie <[1]acm@muc.de> wrote:
> > [...]
> > Is anybody else seeing these problems? Has anybody else tried it,
> > and
> > _not_ seen these problems?
> > I'm also seeing them. If I let "make check" run for a very long time (I
> > was out of house for 90 minutes), it eventually terminates with 2
> > checks that did not finish, in tree-sitter and native-comp. I haven't
> > had the spare cycles to investigate further yet.
> Thanks! On the one hand, I'm sorry you're having these problems, on the
> other hand, it's a relief that I'm not on my own!
I've reconfigured my Emacs without native compilation and run make
bootstrap. I now do not see these 25 failures at all.
So the bugs seem to be triggered by native compilation.
[ .... ]
> > ~Chad
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2023-08-10 20:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 19:18 make check produces 25 failures and hangs (bug #65176) Alan Mackenzie
2023-08-10 19:54 ` chad
2023-08-10 20:14 ` Alan Mackenzie
2023-08-10 20:34 ` Alan Mackenzie [this message]
2023-08-10 21:54 ` Jens Schmidt
2023-08-11 5:37 ` Eli Zaretskii
2023-08-11 19:39 ` Jens Schmidt
2023-08-12 0:10 ` Po Lu
2023-08-12 9:30 ` Jens Schmidt
2023-08-12 18:03 ` Andrea Corallo
2023-08-12 19:09 ` Andrea Corallo
2023-08-13 10:59 ` Jens Schmidt
2023-08-13 11:34 ` Alan Mackenzie
2023-08-13 12:07 ` Eli Zaretskii
2023-08-14 7:51 ` Andrea Corallo
2023-08-14 12:07 ` Eli Zaretskii
2023-08-14 13:38 ` Andrea Corallo
2023-08-14 13:44 ` Eli Zaretskii
2023-08-14 14:13 ` Andrea Corallo
2023-08-14 14:52 ` Alan Mackenzie
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=ZNVJ1ZTaOntwr2CZ@ACM \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=yandros@gmail.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).