[debbugs-tracker] bug#21804: closed (25.0.50; file-notify-tests failure on Cygwin)

[GNU bug Tracking System]

Your message dated Fri, 06 Nov 2015 07:35:19 +0100
with message-id <address@hidden>
and subject line Re: bug#21804: 25.0.50; file-notify-tests failure on Cygwin
has caused the debbugs.gnu.org bug report #21804,
regarding 25.0.50; file-notify-tests failure on Cygwin
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
21804: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=21804
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: 25.0.50; file-notify-tests failure on Cygwin Date: Sun, 1 Nov 2015 10:51:19 -0500 User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0

The following tests are failing on Cygwin:

file-notify-test02-events
file-notify-test02-events-remote
file-notify-test04-file-validity
file-notify-test04-file-validity-remote
file-notify-test05-dir-validity

The first two have been failing for as long as I can remember, but I never got around to reporting it.

The next two failed immediately after they were introduced in the following commit:

commit 7a3f3183cd8faff8901ead547711e1c90ea02efe
Author: Tassilo Horn <address@hidden>
Date: Mon Sep 14 08:03:11 2015 +0200

Test file-notify-valid-p.

* test/automated/file-notify-tests.el
(file-notify-test04-file-validity, file-notify-test05-dir-validity): New
tests.

The last one started failing shortly after that, but I haven’t pinned down the exact commit.

I’m attaching the log based on a build from git 1500667. Please let me know what I can do to help track this down.

Ken

file-notify-tests.log
Description: Binary data

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#21804: 25.0.50; file-notify-tests failure on Cygwin
>
>
>
>
> Date: 
>
> Fri, 06 Nov 2015 07:35:19 +0100
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux)
>
>
>
>
> Ken Brown <address@hidden> writes:
>
> >> 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.
>
> Done. Closing the bug.
>
> > Ken
>
> Best regards, Michael.
>
>
> --- End Message ---