From: Ken Brown <kbrown@cornell.edu>
To: emacs-devel@gnu.org, Michael Albinus <michael.albinus@gmx.de>
Subject: Re: [Emacs-diffs] master 716b468: Extend `file-notify-test02-rm-watch'
Date: Tue, 4 Apr 2017 18:36:21 -0400 [thread overview]
Message-ID: <70055ee8-c1cb-30d2-8a0b-38637adad497@cornell.edu> (raw)
In-Reply-To: <20170322131611.5FF7D20E17@vcs0.savannah.gnu.org>
On 3/22/2017 9:16 AM, Michael Albinus wrote:
> branch: master
> commit 716b46848989bc343797d98488a7a0cc33ed3179
> Author: Michael Albinus <michael.albinus@gmx.de>
> Commit: Michael Albinus <michael.albinus@gmx.de>
>
> Extend `file-notify-test02-rm-watch'
>
> * test/lisp/filenotify-tests.el (file-notify-test02-rm-watch):
> Expect it failed for inotify. Divide tests into different
> `unwind-protect' clauses. Check, that removing watch
> descriptors out of order do not harm. (Bug#26126)
Hi Michael,
Starting with this commit, file-notify-test02-rm-watch fails on Cygwin:
$ make -C test filenotify-tests SELECTOR='\"file-notify-test02-rm-watch$$\"'
[...]
Test file-notify-test02-rm-watch condition:
(ert-test-failed
((should
(equal results
(list 2)))
:form
(equal nil
(2))
:value nil :explanation
(different-types nil
(2))))
This may be another of those timing issues that we've dealt with before,
but I haven't had a chance yet to look at it in detail.
Ken
next parent reply other threads:[~2017-04-04 22:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170322131610.22658.57119@vcs0.savannah.gnu.org>
[not found] ` <20170322131611.5FF7D20E17@vcs0.savannah.gnu.org>
2017-04-04 22:36 ` Ken Brown [this message]
2017-04-05 6:58 ` [Emacs-diffs] master 716b468: Extend `file-notify-test02-rm-watch' Michael Albinus
2017-04-05 19:24 ` Ken Brown
2017-04-05 21:02 ` Andreas Politz
2017-04-06 2:59 ` Ken Brown
2017-04-07 14:56 ` Ken Brown
2017-05-01 10:21 ` Michael Albinus
2017-05-01 18:28 ` Ken Brown
2017-05-01 18:45 ` Michael Albinus
2017-05-08 13:28 ` Ken Brown
2017-05-08 15:30 ` 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=70055ee8-c1cb-30d2-8a0b-38637adad497@cornell.edu \
--to=kbrown@cornell.edu \
--cc=emacs-devel@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).