bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#62694: 30.0.50; eglot-tests fails with recent pylsp


From: João Távora
Subject: bug#62694: 30.0.50; eglot-tests fails with recent pylsp
Date: Fri, 07 Apr 2023 20:05:46 +0100
User-agent: Gnus/5.13 (Gnus v5.13)

Michael Albinus <michael.albinus@gmx.de> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
> Hi,
>
>>> I just replaced all the pylsp tests with clangd based versions of
>>> the same tests.
>>
>> Thank you.
>
> I've just ran with my local Emba environment, all eglot-tests run
> successfully. Except the skipped ones of course :-)

If you want to run those, arrange for the following to be installed:

jdtls
typescript-language-server
vscode-json-languageserver
rust-analyzer
Company
Yasnippet
Microsoft Windows

When installing Company and Yasnippet, which are not part of Emacs but
are GNU ELPA packages, strongly recommend to use our own package-install
tool instead of Debian's packaging for these.  I only test against
package-install.

> Ran 48 tests, 37 results as expected, 0 unexpected, 11 skipped (2023-04-07 
> 14:57:56+0000, 18.064532 sec)
>
> 11 skipped results:
>   SKIPPED  eglot-test-eclipse-connect
>   SKIPPED  eglot-test-javascript-basic
>   SKIPPED  eglot-test-json-basic
>   SKIPPED  eglot-test-path-to-uri-windows
>   SKIPPED  eglot-test-project-wide-diagnostics-rust-analyzer
>   SKIPPED  eglot-test-project-wide-diagnostics-typescript
>   SKIPPED  eglot-test-rust-analyzer-hover-after-edit
>   SKIPPED  eglot-test-rust-analyzer-watches-files
>   SKIPPED  eglot-test-rust-on-type-formatting
>   SKIPPED  eglot-test-snippet-completions
>   SKIPPED  eglot-test-snippet-completions-with-company
>
> Thanks. I'll keep the bug open ...

I don't think this issue should be open.  The title is misleading as
eglot-tests didn't ever "fail with a recent pylsp" (I just tested the
most recent versions).  It used to fails with Debian's pylsp, but there
are no more pylsp tests since a few hours ago.

So I think you should either retitle it (if you know how) or close it
and open a new one.

João





reply via email to

[Prev in Thread] Current Thread [Next in Thread]