GNU bug report logs - #21804
25.0.50; file-notify-tests failure on Cygwin

Previous Next

Package: emacs;

Reported by: Ken Brown <kbrown <at> cornell.edu>

Date: Sun, 1 Nov 2015 15:52:02 UTC

Severity: normal

Found in version 25.0.50

Done: Michael Albinus <michael.albinus <at> gmx.de>

Bug is archived. No further changes may be made.

Full log


Message #38 received at 21804 <at> debbugs.gnu.org (full text, mbox):

From: Ken Brown <kbrown <at> cornell.edu>
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: 21804 <at> debbugs.gnu.org
Subject: Re: bug#21804: 25.0.50; file-notify-tests failure on Cygwin
Date: Thu, 5 Nov 2015 15:14:58 -0500
On 11/5/2015 2:58 PM, Michael Albinus wrote:
> Ken Brown <kbrown <at> cornell.edu> writes:
>
>> Hi Michael,
>
> Hi Ken,
>
>>> Hard to debug, because we are faced with timing issues. So I would need
>>> to do this myself ...
>>>
>>> Well, I'll try to find a machine where I could install cygwin. Where
>>> could I find a very recent Emacs, including the patch of gfilenotify.c
>>> I've committed yesterday?
>>
>> I've just built one and put it on my private Cygwin repository at
>
> I've played with this the whole afternoon. Looks like there is no error
> in gfilenotify for Cygwin. But it is a hard job to trigger the file
> notification events to appear such a way they could be checked for
> correctness in the test cases.
>
> Increasing timeouts was necessary. But even this does not make the
> events to appear reliably. One would need to write additional code to
> get every single event one after the other. Waiting for a series of
> events, as the test cases do expect, does not seem to work.
>
> Since I have no further idea how to get those events reliably, I tend to
> skip both test cases for cygwin. What do you think?

That makes sense to me.  Thanks for your efforts on this.

Ken





This bug report was last modified 8 years and 201 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.