From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Fabrice Popineau Newsgroups: gmane.emacs.devel Subject: Re: Emacs master, w32/w64 Date: Mon, 21 Dec 2015 23:05:38 +0100 Message-ID: References: <87poxz5vih.fsf@gmx.de> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c2de0a8fa42f05276fb144 X-Trace: ger.gmane.org 1450735568 25875 80.91.229.3 (21 Dec 2015 22:06:08 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 21 Dec 2015 22:06:08 +0000 (UTC) Cc: Emacs developers To: Michael Albinus Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 21 23:06:08 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aB8ai-0002bM-6K for ged-emacs-devel@m.gmane.org; Mon, 21 Dec 2015 23:06:04 +0100 Original-Received: from localhost ([::1]:47565 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aB8ah-0005Sj-HQ for ged-emacs-devel@m.gmane.org; Mon, 21 Dec 2015 17:06:03 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42260) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aB8ad-0005SG-5m for emacs-devel@gnu.org; Mon, 21 Dec 2015 17:06:00 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aB8ac-0004GW-2u for emacs-devel@gnu.org; Mon, 21 Dec 2015 17:05:59 -0500 Original-Received: from mail-ob0-x22d.google.com ([2607:f8b0:4003:c01::22d]:36825) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aB8ab-0004GR-SR for emacs-devel@gnu.org; Mon, 21 Dec 2015 17:05:57 -0500 Original-Received: by mail-ob0-x22d.google.com with SMTP id ba1so40475592obb.3 for ; Mon, 21 Dec 2015 14:05:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=wNHplHV391G6yzXYJC5PnvduqUaS52Jv5LaTT6+sbXY=; b=AipAmfWS5OYvIHsUKuMpVhukxhbevvk6kmnkZxFUtoIBlsToWcWMA6sJQlQPmEx4YR lAIQ+LgAq517IRKGPhsD3NMsdF3HUv+6ZzVJoj/cNmoUaYNhcatorY/IzN30KGyeaXMH 7xe9g2cf+OuaZZ3r0T+TyLkehgfkFDWDSSaFoExVn0WAXlzBQjvJ4BmQfDhRKY6NKI8L nQDSWQ3wTt9QF0mCjb8slCnilUhzYpPL3h+jAk1uaqmyySMBngPjvtmWEBy4lGmwnMIO zjxvyrD1xSe3xXusKtBgYykRO+MEql3nuK/bjd7FcIuN2P4hh+JqbfmJHIVXKqj+2fAD 5rZg== X-Received: by 10.182.231.136 with SMTP id tg8mr8365524obc.27.1450735557385; Mon, 21 Dec 2015 14:05:57 -0800 (PST) Original-Received: by 10.202.79.215 with HTTP; Mon, 21 Dec 2015 14:05:38 -0800 (PST) In-Reply-To: <87poxz5vih.fsf@gmx.de> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:4003:c01::22d X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:196632 Archived-At: --001a11c2de0a8fa42f05276fb144 Content-Type: text/plain; charset=UTF-8 2015-12-21 22:42 GMT+01:00 Michael Albinus : > Fabrice Popineau 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. > > Thanks for the quick answer. I can see that now. However : - both `file-notify-test02-events' and `file-notify-test06-many-events' fail (with nil instead of the expected value) - I have the feeling that the read-event calls do not timeout in 0.1s as expected. When I run file-notify-test02-events in edebug mode, read-event does not return in less than 5-10s. I don't know it is meaningful however. I'll try to investigate, but I'm not familiar at all with the way all of this is working. Fabrice > > Best regards, > > > > Fabrice > > Best regards, Michael. > --001a11c2de0a8fa42f05276fb144 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


2015-12-21 22:42 GMT+01:00 Michael Albinus <michael.albinus@gmx.d= e>:
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 num= ber, 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 "w32noti= fy" 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.

--001a11c2de0a8fa42f05276fb144--