all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-29 9c0d7bb73b 2/2: Add automated tests for Eglot
Date: Mon, 12 Dec 2022 09:52:04 +0000	[thread overview]
Message-ID: <CALDnm5231hWkS_rSbyU6Vj1mOSDib5-_K8siFiJqKWvC7smYwg@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmnN6DRtqdpnD-9LHyEDsWooeDx4WDV-thHPT5NEA_2Rmw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1476 bytes --]

Hi Stefan,

Are you seeing these failures on Emacs's CI infrastructure (EMBA,
If I'm not mistaken), or on your own machine? Tests run fine on
my machine.

I'm going to assume this was on your machine from now on.

It seems you have some language servers and language
toolchains installed but that, for some reason, they are not behaving
as they should.

In tests such as 'project-wide-diagnostics-rust-analyzer' an additional
"skip-unless"  check for "cargo" was missing.  I've now fixed that.  Can you
explain why you have a "rust-analyzer" executable, but not "cargo"? Is
this a usual Rust setup?

In other tests, such as 'javascript-basic',
'project-wide-diagnostics-typescript',
the error is strange:

(error "[eglot] -32603: Request initialize failed with message:
  Could not find a valid tsserver version. Exiting.")

I don't know what this can mean. Again, it seems you have
"typescript-language-server", but somehow "no valid tsserver".

In general, I don't know if it's a good idea to keep these tests in the
normal 'make check' run, since many Eglot tests are dependent
on having correctly working servers.  Or at least what I and other test
authors believe to be "correctly configured".  Which is generally the
simplest installation method for said servers, with the fewest bells
and whistles.

Let me know if you've investigated your setup for these servers (again,
I'm assuming this is on your machine and not EMBA).

João

[-- Attachment #2: Type: text/html, Size: 1781 bytes --]

  reply	other threads:[~2022-12-12  9:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <167080394233.4339.5863353994038854528@vcs2.savannah.gnu.org>
     [not found] ` <20221212001223.E9A9DC004BE@vcs2.savannah.gnu.org>
2022-12-12  8:34   ` emacs-29 9c0d7bb73b 2/2: Add automated tests for Eglot Stefan Kangas
2022-12-12  9:52     ` João Távora [this message]
2022-12-12 11:26       ` Stefan Kangas
2022-12-12 11:56         ` João Távora
2022-12-12 21:52           ` Stefan Kangas
2022-12-13  8:49             ` Michael Albinus
2022-12-13 19:23               ` Stefan Kangas
2022-12-14  9:55                 ` Michael Albinus
2022-12-12 10:32   ` Michael Albinus
2022-12-12 10:37     ` João Távora
2022-12-13 19:10       ` Michael Albinus
2022-12-13 20:18         ` João Távora
2022-12-14  9:57           ` Michael Albinus
2022-12-14 12:58             ` João Távora
2022-12-14 14:11               ` Michael Albinus
2022-12-14 15:46                 ` João Távora
2022-12-14 17:41                   ` Stefan Monnier
2022-12-14 21:42                   ` Stefan Kangas
2022-12-15  9:12                     ` Michael Albinus
2022-12-15 12:08                       ` João Távora
2022-12-12 10:59   ` Michael Albinus
2022-12-12 11:03     ` João Távora
2022-12-12 11:08       ` Michael Albinus

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALDnm5231hWkS_rSbyU6Vj1mOSDib5-_K8siFiJqKWvC7smYwg@mail.gmail.com \
    --to=joaotavora@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=stefankangas@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.