From: Ken Brown <kbrown@cornell.edu>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 21804@debbugs.gnu.org
Subject: bug#21804: 25.0.50; file-notify-tests failure on Cygwin
Date: Wed, 28 Dec 2016 18:16:20 -0500 [thread overview]
Message-ID: <f491fd1a-ae9e-6621-31e8-ff7d79a822ac@cornell.edu> (raw)
In-Reply-To: <87h95pp6dd.fsf@gmx.de>
On 12/27/2016 1:35 PM, Michael Albinus wrote:
> I'm reading glib's sources now, in order to
> understand how the polling works exactly.
Hi Michael,
I just looked at the sources also, and the reason for the roughly
5-second delays I've been observing is clear. In gio/gpollfilemonitor.c
we have the following:
#define POLL_TIME_SECS 5
[...]
schedule_poll_timeout (GPollFileMonitor* poll_monitor)
{
poll_monitor->timeout = g_timeout_source_new_seconds (POLL_TIME_SECS);
[...]
}
So I guess there's no way to avoid using a value of
file-notify--test-read-event-timeout bigger than 5.
Best regards,
Ken
next prev parent reply other threads:[~2016-12-28 23:16 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-01 15:51 bug#21804: 25.0.50; file-notify-tests failure on Cygwin Ken Brown
2015-11-01 16:40 ` Eli Zaretskii
2015-11-01 17:25 ` Ken Brown
2015-11-01 17:34 ` Michael Albinus
2015-11-03 17:20 ` Michael Albinus
2015-11-04 3:54 ` Ken Brown
2015-11-04 8:20 ` Michael Albinus
2015-11-04 16:55 ` Ken Brown
2015-11-04 18:44 ` Michael Albinus
2015-11-05 3:21 ` Ken Brown
2015-11-05 19:58 ` Michael Albinus
2015-11-05 20:14 ` Ken Brown
2015-11-06 6:35 ` Michael Albinus
2016-12-26 17:08 ` Ken Brown
[not found] ` <cea29d3c-30d7-45b1-6d8c-1a8b3511791c@cornell.edu>
2016-12-27 12:06 ` Michael Albinus
2016-12-27 16:28 ` Ken Brown
2016-12-27 17:33 ` Ken Brown
2016-12-27 18:35 ` Michael Albinus
2016-12-27 22:48 ` Ken Brown
2016-12-28 23:16 ` Ken Brown [this message]
2016-12-29 19:06 ` Michael Albinus
2016-12-29 20:33 ` Ken Brown
2016-12-30 8:50 ` Eli Zaretskii
2016-12-30 19:07 ` Michael Albinus
2016-12-30 22:19 ` Ken Brown
2016-12-31 8:26 ` Eli Zaretskii
2016-12-31 9:42 ` Michael Albinus
2016-12-30 19:16 ` Michael Albinus
2016-12-30 23:15 ` Ken Brown
2017-01-02 18:47 ` Michael Albinus
2017-01-02 23:15 ` Ken Brown
2017-01-03 9:11 ` Michael Albinus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f491fd1a-ae9e-6621-31e8-ff7d79a822ac@cornell.edu \
--to=kbrown@cornell.edu \
--cc=21804@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).