Re: mark expensive tests

[Michael Albinus]

Eli Zaretskii <address@hidden> writes:

>> I'd especially like the file-notify tests to move to #3, since these are what
>> consistently bog down my testing environment.
>
> file-notify-tests takes about 25 sec here, so I'm unsure why it should
> be in #3.  Maybe that's because of remote tests (which are skipped on
> my system), in which case perhaps the remote tests should be separated
> into a separate test file and run on demand only.

The most time consuming test is file-notify-test06-many-events. It takes
more than 4 minutes on my laptop:

Started at:   2016-01-04 17:08:45+0100
Finished.
Finished at:  2016-01-04 17:13:05+0100

I'm impressed that your supercomputer is that fast. Or do you test under
cygwin? Then this test is skipped.

Remote tests in filenotify-tests.el could go into #3, indeed. Like some
of the tests of tramp-test.el.

Best regards, Michael.