From: Paul Eggert <eggert@cs.ucla.edu>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 21669@debbugs.gnu.org
Subject: bug#21669: 25.0.50; file-notify-tests failure on Fedora x86-64
Date: Tue, 20 Oct 2015 18:34:21 -0700 [thread overview]
Message-ID: <5626EB9D.5040708@cs.ucla.edu> (raw)
In-Reply-To: <877fmlg7zq.fsf@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 214 bytes --]
Michael Albinus wrote:
> I've changed file-notify-tests.el in order to handle this. Could you,
> pls, check?
Still not working, I'm afraid. Failures are intermittent. A failing
file-notify-tests.log is attached.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: file-notify-tests.log --]
[-- Type: text/x-log; name="file-notify-tests.log", Size: 2074 bytes --]
Running 12 tests (2015-10-20 18:31:13-0700)
Local library: `inotify'
passed 1/12 file-notify-test00-availability
Remote command: `gvfs-monitor-dir'
passed 2/12 file-notify-test00-availability-remote
passed 3/12 file-notify-test01-add-watch
passed 4/12 file-notify-test01-add-watch-remote
passed 5/12 file-notify-test02-events
Test file-notify-test02-events-remote backtrace:
#[0 "\306\307\310C\307C\3111(\0\312\313\314\315\316\x06\b\x06\b\x06\b\x06\b$\317\"\32
#[0 "\b\x19\303\304!\305\306\307C\306C\3101-\0\311\312\313\314\315\x06\b\x06\b\x06\b\x06
ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc
ert-run-test([cl-struct-ert-test file-notify-test02-events-remote "C
ert-run-or-rerun-test([cl-struct-ert--stats t [[cl-struct-ert-test f
ert-run-tests(t #[385 "\306\x02\307\"\203G\0\211\211G\310U\203\x14\0\211@\20
ert-run-tests-batch(nil)
ert-run-tests-batch-and-exit()
command-line-1(("-L" ":." "-l" "ert" "-l" "file-notify-tests.elc" "-
command-line()
normal-top-level()
Test file-notify-test02-events-remote condition:
(ert-test-failed
((should
(equal '...
(mapcar ... file-notify--test-events)))
:form
(equal
(attribute-changed)
(attribute-changed attribute-changed))
:value nil :explanation
(proper-lists-of-different-length 1 2
(attribute-changed)
(attribute-changed attribute-changed)
first-mismatch-at 1)))
FAILED 6/12 file-notify-test02-events-remote
Reverting buffer `file-notify-test1422adk'.
passed 7/12 file-notify-test03-autorevert
Reverting buffer `file-notify-test1422nnq'.
passed 8/12 file-notify-test03-autorevert-remote
passed 9/12 file-notify-test04-file-validity
passed 10/12 file-notify-test04-file-validity-remote
passed 11/12 file-notify-test05-dir-validity
passed 12/12 file-notify-test05-dir-validity-remote
Ran 12 tests, 11 results as expected, 1 unexpected (2015-10-20 18:32:01-0700)
1 unexpected results:
FAILED file-notify-test02-events-remote
next prev parent reply other threads:[~2015-10-21 1:34 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
2015-10-21 1:34 ` Paul Eggert [this message]
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
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=5626EB9D.5040708@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=21669@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
/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).