|
From: | Ken Brown |
Subject: | bug#21804: 25.0.50; file-notify-tests failure on Cygwin |
Date: | Tue, 27 Dec 2016 12:33:39 -0500 |
User-agent: | Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 |
Hi again Michael, On 12/27/2016 7:06 AM, Michael Albinus wrote:
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);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.
Best regards, Ken
[Prev in Thread] | Current Thread | [Next in Thread] |