From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Michael Albinus Newsgroups: gmane.emacs.devel Subject: Re: Emacs master, w32/w64 Date: Mon, 21 Dec 2015 22:42:14 +0100 Message-ID: <87poxz5vih.fsf@gmx.de> References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1450734206 4853 80.91.229.3 (21 Dec 2015 21:43:26 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 21 Dec 2015 21:43:26 +0000 (UTC) Cc: Emacs developers To: Fabrice Popineau Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 21 22:43:17 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 1aB8Ed-0005nZ-Rj for ged-emacs-devel@m.gmane.org; Mon, 21 Dec 2015 22:43:16 +0100 Original-Received: from localhost ([::1]:47460 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aB8Ed-0006Sl-8p for ged-emacs-devel@m.gmane.org; Mon, 21 Dec 2015 16:43:15 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:36271) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aB8Dm-0005a7-UG for emacs-devel@gnu.org; Mon, 21 Dec 2015 16:42:23 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aB8Dh-0007Bo-RX for emacs-devel@gnu.org; Mon, 21 Dec 2015 16:42:22 -0500 Original-Received: from mout.gmx.net ([212.227.17.20]:57795) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aB8Dh-0007Az-J9 for emacs-devel@gnu.org; Mon, 21 Dec 2015 16:42:17 -0500 Original-Received: from detlef.gmx.de ([93.209.68.120]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0Lxdfb-1aEBKO29KF-017HcE; Mon, 21 Dec 2015 22:42:15 +0100 In-Reply-To: (Fabrice Popineau's message of "Mon, 21 Dec 2015 22:22:22 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) X-Provags-ID: V03:K0:jtaxu641oI5IeKrt68ubiOyJkbd0IXzwzbyWbOaxSRMQSYgBRzw Kx3r+b138ZWUmNjGw3zzuoUdzXpKvqL0ieToEyVK7u37inwrfmA4eLhjIwbOdZYYaDZfh69 8/oDDNUEdR+Im/LURt0u47BMZkdCNVq7zkd1PJDmknSlkfRxgDn9VRn9z7KIiZRrYxO/kdj z7jJIxGayEVsyZ9bcEFfA== X-UI-Out-Filterresults: notjunk:1;V01:K0:EVC6RRqkJT4=:gWWE1+UBaR9mQMzExS8+ug pTz7FnlbQzCVJew4Zd92E+h8STTIo5hjWtDVuRhdUqCd144xb0IBiyX4DLe0Q1tHevGn1N4eU PCMlivlJVRsw/D9QcppFH54RIhwoWksHKph8FEg0Ve9ekh/HJP/HhcZDQXMSy67ttargpKzCV IH4Xnt8OV24BVnto84ko/ijzugkxHUjykx8rtYuc5UqPsHRsler4weKggvVsPb5HkXT+2e+E1 3x5ytaVkutBkvut5F2T6+gqEGnRyQCQs7bBqMCTM2ymcxlAwVVj5QZEuPWPMX3bGKhSITdXJD KIQDVVptLyVWlDqz8h5JWx+yj0Fehlwa/tiN+JxuTZ0OdZBPNwi1BFZGKuyoL/209DMqtT9Cb baw1t8KFwzTEPu/UfrfeS2K3JUAkRhTaRGVkLewwhi3Ii5wNmkf5IaTJgV8VyNBNYVuYy6QUi CLQPvQwzWv5Z2+rM0sy2fWIJynCrAblQ1AtbloVydzAH2/kjjxbGWq/quWO7mJW0OejWHKBay YY6h+tA6g1TNolokl3fxwLGH2Taw/GJhhYkpEtOHuPTIhnuCdcj8R3uNbj/DEoyG8SWB9h6DQ Yuoc1H+N7HTc5nxeA+29gvj0WmkDN3P4SQiNfBw4TC5Nq9E705GEi1wFrgkGsBJIo395VM2tL Xx1uBYx6HQ3GHPoUVePcwRjJV76ELZVa4CxgukOxOWRF3IEQl0XJgi2XIJulkkxBSECiDkg43 y5EZccMw7X08gpJE/69eoxrwj11O1zbOYiogrW8HKrs6skpyx9UT+50GCw5wwOnl21CuNzFE X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 212.227.17.20 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:196631 Archived-At: 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. > Best regards, > > Fabrice Best regards, Michael.