Running pre-commit tests (was: master e54b94c28cd: Use @xref more consistently; "See @ref" -> "@xref")

[Michael Albinus]

Pip Cet via "Emacs development discussions." <emacs-devel@gnu.org>
writes:

Hi,

>> We could have something that one could install and use optionally, but
>> even then I'd request it to be very fast, so that the whole thing takes
>> less than a fraction of a second to run.  Much more than that, and I'd
>> probably just turn it off again.
>
> I hope "make check" can be fixed, but right now it is that way for me.
> It's still incredibly useful, but running it on an enable-checking build
> without optimization requires some patience (it just did find a bug in
> one of my patches, though).
>
> And if the idea is to do the best we can in the limited time period
> until the user confirms they do want to push (this is my idea of
> zero-cost checking), always running the tramp tests first seems
> suboptimal.  A good randomization strategy would be important; running a
> full test matrix on every commit isn't viable.

FTR, you can run 'make -C test <test-file>' for any <test-file> under
test/, like 'make -C test files-tests'. You can run 'make -C test
check-<dirname>' for any direcory under test/, like 'make -C test
check-lisp-net'. See test/README.

This is how I check prior a commit in Tramp, always running 'make -C
test tramp-tests'.

> Pip

Best regards, Michael.