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

Previous Next

Full log

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

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Ken Brown <kbrown <at> cornell.edu>
Cc: 21804 <at> debbugs.gnu.org
Subject: Re: bug#21804: 25.0.50; file-notify-tests failure on Cygwin
Date: Tue, 27 Dec 2016 19:35:42 +0100

Ken Brown <kbrown <at> cornell.edu> writes:

> Hi again Michael,

Hi Ken,

>> Maybe we need to determine the polling interval, and to set
>> file-notify--test-read-event-timeout larger than that. Will check,
>> whether information this could be retrieved from gfilenotify.
>
> Isn't the polling interval set to 100 msec by the following line in
> gfilenotify.c?
>
>   g_file_monitor_set_rate_limit (monitor, 100);

Yes. IIRC, I did that, because there were problems with gfilenotify on
GNU/Linux otherwise.

> By the way, I tried removing that line and using the default polling
> interval, and it seemed (subjectively) to work better, i.e., the wait
> time for a `created' event in an interactive session appeared to be
> 2-3 
> seconds instead of 5-6 seconds.  But this doesn't seem to be
> consistent enough to allow me to substantially reduce
> file-notify--test-read-event-timeout.

Good to know, thanks. I'm reading glib's sources now, in order to
understand how the polling works exactly.

Btw, which version of glib do you use for your tests?

> Best regards,
>
> Ken

Best regards, Michael.

Previous Next

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