--- Begin Message ---
Subject: |
Some filenotify tests fail with extra "changed" events |
Date: |
Wed, 25 May 2016 12:55:44 -0400 |
User-agent: |
Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) |
Package: emacs
Version: 25.0.94
Severity: minor
Some filenotify tests have failed for some time (always?) for me on RHEL 7.2.
Finally a report about it. In the past I've only ever seen one extra
"changed", never the silly number the following log includes! :)
PS as you can see from the log, these tests took ~ 15 minutes to run.
file-notify-tests.log.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#23618: Some filenotify tests fail with extra "changed" events |
Date: |
Thu, 23 Jun 2016 20:34:13 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) |
Glenn Morris <address@hidden> writes:
> It's better, thanks.
Puh, finally ...
> file-notify-test08-watched-file-in-watched-dir-remote still fails, for
> impenetrable reasons. But it isn't run by default, so maybe it's time to
> stop thinking about this now. The expensive tests are so slow, no-one
> but you will ever run them anyway. ;)
It's not that bad, all created events have passed, and most of the
changed events. In reality I don't expect any problem, because changed
events appear more than once for a given change.
As you could assume, I have no problems locally. I guess it is a problem
of timing, but I don't want to increase the delays longer than they are.
Yes, let's close this bug. Thanks for your patient testing!
Best regards, Michael.
--- End Message ---