From: "João Távora" <joaotavora@gmail.com>
To: Jeremy Bryant <jb@jeremybryant.net>
Cc: 71966@debbugs.gnu.org, john muhl <jm@pub.pink>
Subject: bug#71966: 30.0.60; Intermittent failure in eglot-tests
Date: Sun, 7 Jul 2024 00:30:11 +0100 [thread overview]
Message-ID: <CALDnm50eoj-PiDJ_C8Uh6G+eOjxg9obs5WVeO=qyuw5QORN2hA@mail.gmail.com> (raw)
In-Reply-To: <87y16ep2wq.fsf@jeremybryant.net>
Hmmm,
Seems like the clangd on that underpowered machine takes
longer than the default 10 seconds to respond to Eglot's
initiation. I don't think it's worth bumping the timeouts for
such cases, but I don't mind it either. Why are you running tests
on those ARM machines?
BTW clangd is usually very spiffy by comparison with other
servers, so I can't imagine how the other tests will ever pass
(they're probably skipped).
João
On Sat, Jul 6, 2024 at 11:32 PM Jeremy Bryant <jb@jeremybryant.net> wrote:
>
> john muhl <jm@pub.pink> writes:
>
> > The failing test is ‘eglot-test-auto-detect-running-server’. I
> > can’t reproduce it here by running the individual test in a loop
> > (well it didn’t fail during 5 hours of looping). However it has
> > failed 10 times in the last 62 runs of ‘make check’. It only
> > happens on the 32bit ARM test machine but happens across all
> > tested configurations there.
> >
> > I was able to run ‘make check’ a dozen times without failure using
> > the patch below. Let’s see how it does for a week or two of builds.
> >
> > --- a/test/lisp/progmodes/eglot-tests.el
> > +++ b/test/lisp/progmodes/eglot-tests.el
> > @@ -326,7 +326,7 @@ eglot-tests--auto-detect-running-server-1
> > ("anotherproject" . (("cena.c" . "bla"))))
> > (with-current-buffer
> > (eglot--find-file-noselect "project/coiso.c")
> > - (should (setq server (eglot--tests-connect)))
> > + (should (setq server (eglot--tests-connect 20)))
> > (should (eglot-current-server)))
> > (with-current-buffer
> > (eglot--find-file-noselect "project/merdix.c")
> >
> > [2. text/plain; eglot-tests.log]...
>
> Adding João on this bug report
--
João Távora
prev parent reply other threads:[~2024-07-06 23:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-06 3:42 bug#71966: 30.0.60; Intermittent failure in eglot-tests john muhl
2024-07-06 22:32 ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-06 23:30 ` João Távora [this message]
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='CALDnm50eoj-PiDJ_C8Uh6G+eOjxg9obs5WVeO=qyuw5QORN2hA@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=71966@debbugs.gnu.org \
--cc=jb@jeremybryant.net \
--cc=jm@pub.pink \
/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).