all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 21669@debbugs.gnu.org
Subject: bug#21669: 25.0.50; file-notify-tests failure on Fedora x86-64
Date: Sat, 17 Oct 2015 11:27:37 +0200	[thread overview]
Message-ID: <877fmlg7zq.fsf@gmx.de> (raw)
In-Reply-To: <56215C20.2090203@cs.ucla.edu> (Paul Eggert's message of "Fri, 16 Oct 2015 13:20:48 -0700")

Paul Eggert <eggert@cs.ucla.edu> writes:

> Unfortunately it does not. Most of the time file-notify-tests
> succeeds, but it occasionally fails. I'm attaching a failure log,
> generated from commit 1e1a326c0f609f403c625bd9082e1099a4d9a52a and
> built with GCC 5.2 on Fedora 21 x86-64 with './configure
> --enable-gcc-warnings'.
>
> Running 12 tests (2015-10-16 13:14:40-0700)
> Local library: `inotify'
>    passed   1/12  file-notify-test00-availability
> Remote command: `gvfs-monitor-dir'
>
> 1 unexpected results:
>    FAILED  file-notify-test02-events-remote

Well, with gfilenotify it is known that there are timimg issues if
events occur in short period. Some of them are suppressed then, likely
as performance feature of gio.

With the local gfilenotify library (not used in your case) I could fix
this; the remote gvfs-monitor-dir process does not offer an argument for
changing the timing.

I've changed file-notify-tests.el in order to handle this. Could you,
pls, check?

Best regards, Michael.





  reply	other threads:[~2015-10-17  9:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-11 22:35 bug#21669: 25.0.50; file-notify-tests failure on Fedora x86-64 Paul Eggert
2015-10-12 11:14 ` Michael Albinus
2015-10-13  1:36   ` Paul Eggert
2015-10-13  7:46     ` Michael Albinus
2015-10-16 20:20       ` Paul Eggert
2015-10-17  9:27         ` Michael Albinus [this message]
2015-10-21  1:34           ` Paul Eggert
2015-10-21  8:01             ` Michael Albinus
2015-10-21 16:03               ` Paul Eggert
2015-10-21 18:25                 ` Michael Albinus
2015-10-23 11:31                 ` Michael Albinus
2015-10-31  8:31                   ` Michael Albinus
2015-10-31 12:49                   ` Paul Eggert
2015-10-31 13:36                     ` 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=877fmlg7zq.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=21669@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    /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.