unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Eli Zaretskii <eliz@gnu.org>, 62694@debbugs.gnu.org
Subject: bug#62694: 30.0.50; eglot-tests fails with recent pylsp
Date: Fri, 07 Apr 2023 20:05:46 +0100	[thread overview]
Message-ID: <87h6trh5rp.fsf@gmail.com> (raw)
In-Reply-To: <87edov3f69.fsf@gmx.de> (Michael Albinus's message of "Fri, 07 Apr 2023 17:06:22 +0200")

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	other threads:[~2023-04-07 19:05 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-06  9:55 bug#62694: 30.0.50; eglot-tests fails with recent pylsp Michael Albinus
2023-04-06 10:54 ` João Távora
2023-04-06 11:22   ` Michael Albinus
2023-04-06 12:49     ` João Távora
2023-04-06 14:58       ` Michael Albinus
2023-04-06 16:59         ` João Távora
2023-04-06 17:39           ` Michael Albinus
2023-04-06 19:50             ` João Távora
2023-04-07  7:44               ` Michael Albinus
2023-04-07 10:20                 ` João Távora
2023-04-07 10:29                   ` Michael Albinus
2023-04-07 10:47                     ` João Távora
2023-04-07 10:50                       ` Michael Albinus
2023-04-07 10:57                         ` João Távora
2023-04-07 11:04                           ` Gregory Heytings
2023-04-07 11:10                             ` João Távora
2023-04-07 11:11                           ` Eli Zaretskii
2023-04-07 11:20                             ` João Távora
2023-04-07 12:20                               ` Michael Albinus
2023-04-07 10:43                   ` Eli Zaretskii
2023-04-07 10:51                     ` João Távora
2023-04-07 10:53                       ` Michael Albinus
2023-04-07 10:59                       ` Eli Zaretskii
2023-04-07 11:06                         ` João Távora
2023-04-07 11:17                           ` Eli Zaretskii
2023-04-07 11:23                             ` João Távora
2023-04-07 11:37                               ` João Távora
2023-04-07 11:41                                 ` Michael Albinus
2023-04-07 11:47                                   ` João Távora
2023-04-07 11:53                                     ` João Távora
2023-04-07 12:07                                 ` Eli Zaretskii
2023-04-07 12:13                                   ` Michael Albinus
2023-04-07 12:22                                     ` Eli Zaretskii
2023-04-07 12:40                                       ` João Távora
2023-04-07 12:58                                         ` Gregory Heytings
2023-04-07 13:02                                           ` João Távora
2023-04-07 13:57                                         ` Eli Zaretskii
2023-04-07 12:59                                       ` Michael Albinus
2023-04-07 13:48                                         ` Eli Zaretskii
2023-04-07 13:57                                           ` Michael Albinus
2023-04-07 14:00                                             ` Eli Zaretskii
2023-04-07 14:04                                               ` João Távora
2023-04-07 14:33                                                 ` Eli Zaretskii
2023-04-07 15:06                                                   ` Michael Albinus
2023-04-07 19:05                                                     ` João Távora [this message]
2023-04-09 13:49                                                   ` Michael Albinus
2023-04-07 12:04                             ` Michael Albinus
2023-04-07 12:24                               ` João Távora
2023-04-07 12:47                                 ` Michael Albinus
2023-04-07 13:01                                   ` João Távora
2023-04-07 13:04                                     ` Michael Albinus
2023-04-09 11:24               ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-09 11:22       ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-09 12:41         ` João Távora
2023-04-09 13:21           ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-09 14:45             ` João Távora
2023-04-09 15:32               ` Michael Albinus
2023-04-09 15:48                 ` João Távora
2023-04-09 16:08                   ` Michael Albinus
2023-04-09 18:17                     ` João Távora
2023-04-09 19:04                       ` Eli Zaretskii

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=87h6trh5rp.fsf@gmail.com \
    --to=joaotavora@gmail.com \
    --cc=62694@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=michael.albinus@gmx.de \
    /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).