Subject: bug#21432: 25.0.50; file-notify-rm-watch (inotify) errors if watched dir is deleted

From: Michael Albinus <[email-masked]>
Date: Tue, 15 Sep 2015 10:00:10 +0200

Eli Zaretskii <[email-masked]> writes:

>> I've adapted `file-notify-test04-file-validity' and
>> `file-notify-test05-dir-validity', and they pass the tests now for the
>> inotify case. Hopefully, it is the same for w32notify.
>
> No, it fails:
>
>   Test file-notify-test04-file-validity condition:
>       (ert-test-failed
>        ((should
> 	 (equal '...
> 	  (mapcar ... events)))
> 	:form
> 	(equal
> 	 (created changed deleted)
> 	 nil)
> 	:value nil :explanation
> 	(different-types
> 	 (created changed deleted)
> 	 nil)))
>      FAILED   9/12  file-notify-test04-file-validity
>
> I guess the file-notify--test-with-events macro doesn't allow events
> to come in on w32, but I have no idea how to debug this.

After loading file-notify-tests.el, trace-function for
file-notify-handle-event, file-notify-callback,
file-notify--test-event-handler. Run only file-notify-test04-file-validity.
Show the trace buffer.

Best regards, Michael.