unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thomas Fitzsimmons <fitzsim@fitzsim.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: master 32e790f: Implement NTLM server for ntlm.el testing
Date: Fri, 19 Feb 2021 17:15:50 -0500	[thread overview]
Message-ID: <m3tuq7ln55.fsf@fitzsim.org> (raw)
In-Reply-To: <87a6s0vtuh.fsf@gmx.de> (Michael Albinus's message of "Fri, 19 Feb 2021 18:40:54 +0100")

Hi Michael,

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

> Thomas Fitzsimmons <fitzsim@fitzsim.org> writes:

[...]

>>> Could you pls provide more advanced checks for dependencies? For
>>> example, instead of
>>>
>>>  (and (featurep 'url-http-ntlm) (featurep 'web-server))
>>>
>>> you could check a proper version of the packages?
>>
>> I'd rather not add the complexity, e.g., depending on package.el.
>> Beyond this first requirement to update web-server to the latest, I
>> don't see how a version check would be useful.  I tried to implement a
>> specific check for the ws-parse functionality, but I couldn't find an
>> easy way of confirming the new NTLM path.
>
> That's just *this* case. Other changes might apply to your packages in
> the future, which require newer package code. And I'm thinking also
> about a more general approach for other Emacs tests, how to use GNU ELPA
> packages as dependency.

OK, makes sense.

> And you don't need package.el. Require lisp-mnt, then you could do
> something like

[...]

OK, thanks.  I've pushed a variation on your suggestion that checks for
the NTLM ws-parse functionality (web-server's GNU ELPA version has not
been bumped yet).

>>> Warning (emacs): Cannot find one or more GNU ELPA packages
>>> Warning (emacs): Skipping NTLM authentication tests
>>> Warning (emacs): See GNU_ELPA_DIRECTORY in test/README
>>> Running 3 tests (2021-02-19 10:26:00+0100, selector `(not (tag :unstable))')
>>>   skipped  1/3  ntlm-authentication (0.000133 sec)
>>>   skipped  2/3  ntlm-authentication-old-compatibility-level (0.000097 sec)
>>>    passed  3/3  ntlm-time-to-timestamp (0.000136 sec)
>>>
>>> Is it necessary to be such chatty? The tests are skipped (like other
>>> tests), fine.
>>
>> I debated not putting in those warnings.  I wanted to point out why the
>> tests are being skipped, and in particular that it's easy to have them
>> not be skipped if you have a GNU ELPA checkout (versus tests that are
>> unavoidably skipped because they depend on a different OS or
>> architecture).
>>
>> Basically, I'd like to encourage Emacs maintainers to not skip these
>> tests; the reason I wrote them was to prevent regressions like Bug#43566
>> (merged with Bug#44195 and Bug#44439), which broke all uses of NTLM in
>> an Emacs point release.
>
> Again, not every Emacs developer has an ELPA checkout. And we shouldn't
> be bossy to them.

Sure, I removed the warnings.

Thomas



  reply	other threads:[~2021-02-19 22:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210219014652.27375.17475@vcs0.savannah.gnu.org>
     [not found] ` <20210219014654.0131020DFB@vcs0.savannah.gnu.org>
2021-02-19  9:30   ` master 32e790f: Implement NTLM server for ntlm.el testing Michael Albinus
2021-02-19 14:13     ` Thomas Fitzsimmons
2021-02-19 17:40       ` Michael Albinus
2021-02-19 22:15         ` Thomas Fitzsimmons [this message]
2021-02-20  8:34           ` Michael Albinus
2021-02-20 10:42         ` Stephen Leake

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=m3tuq7ln55.fsf@fitzsim.org \
    --to=fitzsim@fitzsim.org \
    --cc=emacs-devel@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).