unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 22851@debbugs.gnu.org
Subject: bug#22851: 25.1.50; filenotify tests take so long to run
Date: Mon, 29 Feb 2016 15:48:59 +0100	[thread overview]
Message-ID: <87io17lgh0.fsf@gmx.de> (raw)
In-Reply-To: <87oaazk31w.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 01 Mar 2016 01:24:11 +1100")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> If I say "make lisp/filenotify-tests", the tests take an inordinate
> amount of time.  It's been running for ten minutes now, and it's still
> just up to 13/18.  This means that I (and I would assume this applies to
> other people, too) can't just say "make" in the test directory to see
> whether anything interesting has broken lately.
>
> Can we inhibit those tests?

The usual tests when calling "make" (or "make check" from Emacs' top
directory) do not run such long. They suppress all tests marked as
expensive.

When you call "make filenotify-tests" it is intended to run all tests,
including the expensive ones. If you want to suppress expensive tests as
well, call "make filenotify-tests SELECTOR='$(SELECTOR_DEFAULT)'". Note,
that you don't need the "lisp/" prefix.

See test/README for further discussion.

Best regards, Michael.





  reply	other threads:[~2016-02-29 14:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29 14:24 bug#22851: 25.1.50; filenotify tests take so long to run Lars Ingebrigtsen
2016-02-29 14:48 ` Michael Albinus [this message]
2016-02-29 20:58   ` Lars Ingebrigtsen
2016-03-01  5:52     ` Michael Albinus
2016-03-01 10:02     ` Michael Albinus
2016-03-02 16:42       ` Lars Ingebrigtsen

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=87io17lgh0.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=22851@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    /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).