unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Ken Brown <kbrown@cornell.edu>
Cc: 21804@debbugs.gnu.org
Subject: bug#21804: 25.0.50; file-notify-tests failure on Cygwin
Date: Thu, 05 Nov 2015 20:58:42 +0100	[thread overview]
Message-ID: <87y4ecnrpp.fsf@gmx.de> (raw)
In-Reply-To: <563ACB3F.5080709@cornell.edu> (Ken Brown's message of "Wed, 4 Nov 2015 22:21:35 -0500")

Ken Brown <kbrown@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?

> Ken

Best regards, Michael.





  reply	other threads:[~2015-11-05 19:58 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 [this message]
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
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=87y4ecnrpp.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=21804@debbugs.gnu.org \
    --cc=kbrown@cornell.edu \
    /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).