all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Fabrice Popineau <fabrice.popineau@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Emacs master, w32/w64
Date: Mon, 21 Dec 2015 22:42:14 +0100	[thread overview]
Message-ID: <87poxz5vih.fsf@gmx.de> (raw)
In-Reply-To: <CAFgFV9O6qC=R-LtHUU8+qcYR0U7WX0Dw9NzFUh8VATqjsXD=eA@mail.gmail.com> (Fabrice Popineau's message of "Mon, 21 Dec 2015 22:22:22 +0100")

Fabrice Popineau <fabrice.popineau@gmail.com> writes:

> At the moment, when I ran tests on emacs master build with msys2 on
> w64, 
> filenotify-tests take forever long : 15mn on a core i7. I have the
> feeling something is wrong with read_event / timeouts. I don't
> remember something like this was happening before.
>
> Any idea where to look for to fix this ?

Modify n in `file-notify-test06-many-events' to be a smaller number, or
disable that test entirely. It is expected that this test runs for a
while. However, when I have tried this last time (some weeks ago), I
don't remember that all tests in filenotify.el took 15mn. 

Looking into `file-notify--test-timeout', the timeout for "w32notify" is
much larger than the other timeouts. Likely it was me who has declared
this long timeout, but I don't remember the details. It could be a sign
that we have there problems, indeed.

> Best regards,
>
> Fabrice

Best regards, Michael.



  reply	other threads:[~2015-12-21 21:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-21 21:22 Emacs master, w32/w64 Fabrice Popineau
2015-12-21 21:42 ` Michael Albinus [this message]
2015-12-21 22:05   ` Fabrice Popineau
2015-12-22 10:44     ` Michael Albinus
2015-12-22  3:32 ` Eli Zaretskii
2015-12-22 10:03   ` Michael Albinus
2015-12-22 16:17     ` Eli Zaretskii

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87poxz5vih.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=emacs-devel@gnu.org \
    --cc=fabrice.popineau@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.