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

[Eli Zaretskii <eliz@gnu.org>]

> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: 62694@debbugs.gnu.org,  joaotavora@gmail.com
> Date: Fri, 07 Apr 2023 14:59:44 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> > Alternatively, we could mark these tests as known to fail, right?
> >>
> >> This would be unfortune if there is a pylsp version on the machine which
> >> let the tests succeed.
> >
> > Why unfortunate? what am I missing?
> 
> On my laptop, where the eglot pylsp tests pass, "mark these tests as
> known to fail" would result in something like this:
> 
> --8<---------------cut here---------------start------------->8---
> (ert-deftest foo ()
>   :expected-result :failed
>   (should t))
> 
> M-x ert RET foo RET
> 
> Selector: foo
> Passed:  1 (1 unexpected)
> Failed:  0
> Skipped: 0
> Total:   1/1
> 
> Started at:   2023-04-07 14:52:01+0200
> Finished.
> Finished at:  2023-04-07 14:52:01+0200
> 
> P
> 
> P foo
>     passed unexpectedly
> --8<---------------cut here---------------end--------------->8---
> 
> The test foo is marked red in the *ert* buffer.

I understand, but I don't see this as a problem, FWIW.

However, if you prefer marking them as unstable, I'm okay with that.