all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Glenn Morris <rgm@gnu.org>
Cc: 23618@debbugs.gnu.org
Subject: bug#23618: Some filenotify tests fail with extra "changed" events
Date: Fri, 27 May 2016 20:00:53 +0200	[thread overview]
Message-ID: <87oa7rgz3e.fsf@gmx.de> (raw)
In-Reply-To: <oqshx3sbh0.fsf@fencepost.gnu.org> (Glenn Morris's message of "Fri, 27 May 2016 12:38:03 -0400")

Glenn Morris <rgm@gnu.org> writes:

>> We have done some work in the master branch, which is not contained in
>> the emacs-25 branch. I don't see any problem running the tests in the
>> master branch. Do you see the problems also in the master branch?
>
> I do.
>
>> It might be also interesting to know whether the failed tests appear
>> also during an ordinary "make check".
>
> Current master make check:
>
> 3 unexpected results:
>    FAILED  file-notify-test02-events
>    FAILED  file-notify-test04-file-validity
>    FAILED  file-notify-test07-backup
>
> Still due to extra "changed" events.

OK, I'll try to get an RHEL 7.2 VM in order to reproduce it. Or maybe a
CentOS VM, in case RHEL VMs are not available.

In case it fails, I will send you an instrumentation patch for
filenotify-tests.el. We do agree that we work on the master branch,
don't we?

Best regards, Michael.





  reply	other threads:[~2016-05-27 18:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-25 16:55 bug#23618: Some filenotify tests fail with extra "changed" events Glenn Morris
2016-05-27  9:24 ` Michael Albinus
2016-05-27 16:38   ` Glenn Morris
2016-05-27 18:00     ` Michael Albinus [this message]
2016-06-05 17:59       ` Michael Albinus
2016-06-07 21:23         ` Glenn Morris
2016-06-20 12:46           ` Michael Albinus
2016-06-23 17:34             ` Glenn Morris
2016-06-23 18:34               ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87oa7rgz3e.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=23618@debbugs.gnu.org \
    --cc=rgm@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.