unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21432@debbugs.gnu.org, tsdh@gnu.org
Subject: bug#21432: 25.0.50; file-notify-rm-watch (inotify) errors if watched dir is deleted
Date: Wed, 16 Sep 2015 16:45:56 +0200	[thread overview]
Message-ID: <87d1xi5snv.fsf@gmx.de> (raw)
In-Reply-To: <83a8sn977f.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 15 Sep 2015 15:51:16 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> I think the problem is due to the fact that the directory is deleted
> inside the file-notify--test-with-events form: doing that invalidates
> the watch, so the events are not reported.  If I remove this line from
> the macro body:
>
> So I modified the test to have the directory deletion outside of the
> macro, and the test now passes.  I also increased the timeout of
> read-event, because 0.1 was borderline: it sometimes worked and
> sometimes didn't.

I've checked further. In `file-notify-test04-file-validity', you have
also removed the final check for `file-notify-valid-p':

         ;; After deleting the parent, the descriptor must not be valid
         ;; anymore.
-        (should-not (file-notify-valid-p file-notify--test-desc)))
+        (delete-directory temporary-file-directory t)
+        (read-event nil nil 0.5))

Was this by intention? The whole test case is about this check. And
maybe this is also the reason that it passes now the remote test case,
surprisingly.

Best regards, Michael.





  parent reply	other threads:[~2015-09-16 14:45 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08  6:36 bug#21432: 25.0.50; file-notify-rm-watch (inotify) errors if watched dir is deleted Tassilo Horn
2015-09-08  7:47 ` Michael Albinus
2015-09-08  8:11   ` Tassilo Horn
2015-09-08 15:51   ` Eli Zaretskii
2015-09-08 15:49 ` Eli Zaretskii
2015-09-08 16:01   ` Michael Albinus
2015-09-12 10:18     ` Michael Albinus
2015-09-12 15:11       ` Eli Zaretskii
2015-09-12 18:09         ` Michael Albinus
2015-09-13 19:23           ` Michael Albinus
2015-09-14  6:08             ` Tassilo Horn
2015-09-14  7:08               ` Eli Zaretskii
2015-09-14  7:40                 ` Tassilo Horn
2015-09-14  7:56                   ` Tassilo Horn
2015-09-14 13:22                     ` Eli Zaretskii
2015-09-14 20:23                       ` Michael Albinus
2015-09-15  7:38                         ` Eli Zaretskii
2015-09-15  8:00                           ` Michael Albinus
2015-09-15  8:22                             ` Eli Zaretskii
2015-09-15 11:54                               ` Michael Albinus
2015-09-15 12:51                                 ` Eli Zaretskii
2015-09-15 12:56                                   ` Michael Albinus
2015-09-16 14:45                                   ` Michael Albinus [this message]
2015-09-16 17:08                                     ` Eli Zaretskii
2015-09-16 17:26                                       ` Michael Albinus
2015-09-16 17:55                                         ` Eli Zaretskii
2015-09-16 18:28                                           ` Michael Albinus
2015-09-15  5:53                       ` Tassilo Horn
2015-09-14  7:35         ` Eli Zaretskii
2015-09-14  7:37           ` Michael Albinus
2015-09-15 13:02           ` Michael Albinus
2015-09-15 13:56             ` Eli Zaretskii
2015-09-16 13:54               ` Michael Albinus
2015-09-20 17:23 ` Michael Albinus
2015-09-20 19:19   ` Eli Zaretskii
2015-09-21 13:40     ` 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=87d1xi5snv.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=21432@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=tsdh@gnu.org \
    /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).