From: Eli Zaretskii <eliz@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: 62694@debbugs.gnu.org, michael.albinus@gmx.de
Subject: bug#62694: 30.0.50; eglot-tests fails with recent pylsp
Date: Fri, 07 Apr 2023 16:57:07 +0300 [thread overview]
Message-ID: <83o7nzokwc.fsf@gnu.org> (raw)
In-Reply-To: <87y1n3hnlh.fsf@gmail.com> (message from João Távora on Fri, 07 Apr 2023 13:40:42 +0100)
> From: João Távora <joaotavora@gmail.com>
> Cc: Michael Albinus <michael.albinus@gmx.de>, 62694@debbugs.gnu.org
> Date: Fri, 07 Apr 2023 13:40:42 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Given João's reluctance to help you to find a better solution,
>
> FTR I've given a solution about 20 times now that was ignored
> repeteadly. There is no general bullet-proof solution for the problem
> of broken or misbehaving installations of external tools. So these
> tests cannot ever be "stable". You can mark them _all_ unstable.
Great, then we agree.
Michael, would you please mark the relevant tests unstable?
> FTR I've given a solution known to be working in an Ubuntu-based CI
> system, very similar to Debian, for almost 5 years now. Noone seems to
> be heeding it, so what can I do?
>
> FTR I've explained at length why the "better solution" that you and
> Michael are conjecturing to be very easy is beyond me. In my analysis,
> there is no simple Elisp code that can, in this pylsp case, easily
> discern between a functioning installation and a malfunctioning one.
> I've asked for your suggestions on how this can be done and I've not
> received any concrete ideas.
>
> FTR, earlier this year, I took Michael's idea of adding a version check
> to clangd for eglot-tests.el because it was relatively easy and cheap
> and shown to be working. _Not_ because there were any reports of people
> with old clangd running make check (absolutely 0 of those too), but
> because I found it easy to do so (and why not appease good old
> Michael?). There the argument was that in that old Debian Stable debian
> system of EMBA it was not easy to install a newer clangd. OK. But, for
> pylsp that is _not_ the case at all, it's a simple one liner.
>
> So if anyone is being stubborn here, it's _not_ me.
I didn't stay you were stubborn.
next prev parent reply other threads:[~2023-04-07 13:57 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 [this message]
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
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=83o7nzokwc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62694@debbugs.gnu.org \
--cc=joaotavora@gmail.com \
--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).