GNU bug report logs -
#36940
tests slowness and failure after recent Tramp changes
Previous Next
Reported by: Paul Eggert <eggert <at> cs.ucla.edu>
Date: Tue, 6 Aug 2019 00:29:02 UTC
Severity: normal
Done: Paul Eggert <eggert <at> cs.ucla.edu>
Bug is archived. No further changes may be made.
Full log
Message #14 received at 36940 <at> debbugs.gnu.org (full text, mbox):
Paul Eggert <eggert <at> cs.ucla.edu> writes:
Hi Paul,
>> If you want to run the
>> default tests, which are active while "make check", you must use the
>> default selector. See test/README.
>
> Thanks, I didn't know that. But that's confusing, as it's natural to
> assume that if FOO is an individual check, then 'make FOO' will run it
> the same way that 'make check' would. Would it make sense to change
> this test to be more natural?
It is intended this way. If I call 'make FOO', I'm interested in package
FOO. For example, because I have changed something in FOO, and I want
to know that I didn't break anything. Expensive tests are part of this.
This is the most applied use case of 'make FOO'. At least I call it
several times a week for exactly this reason. That's why we have the
behavior as it is.
All of this has been discussed already, somewhere in the emacs-devel ML
archives.
Best regards, Michael.
This bug report was last modified 5 years and 326 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.