From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: filenotify-tests.el failing inside Docker debian:stretch
Date: Mon, 31 Dec 2018 16:14:02 +0000 [thread overview]
Message-ID: <h8etllmd.fsf@lifelogs.com> (raw)
The only Emacs tests that currently fail inside Docker (using
debian:stretch image) are as follows. Is that expected because of Docker
specifics or is it something else?
Thanks
Ted
Running 8 tests (2018-12-31 15:28:15+0000, selector `(not (or (tag :expensive-test) (tag :unstable)))')
Library: `inotify'
passed 1/8 file-notify-test00-availability (0.001403 sec)
passed 2/8 file-notify-test01-add-watch (0.001401 sec)
passed 3/8 file-notify-test02-rm-watch (0.024561 sec)
Test file-notify-test03-events backtrace:
signal(ert-test-failed (((should (file-notify--test-with-events-chec
ert-fail(((should (file-notify--test-with-events-check events)) :for
#f(compiled-function () #<bytecode 0xbae5b9>)()
ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
ert-run-test(#s(ert-test :name file-notify-test03-events :documentat
ert-run-or-rerun-test(#s(ert--stats :selector (not (or ... ...)) :te
ert-run-tests((not (or (tag :expensive-test) (tag :unstable))) #f(co
ert-run-tests-batch((not (or (tag :expensive-test) (tag :unstable)))
ert-run-tests-batch-and-exit((not (or (tag :expensive-test) (tag :un
eval((ert-run-tests-batch-and-exit '(not (or (tag :expensive-test) (
command-line-1(("-L" ":." "-l" "ert" "-l" "lisp/filenotify-tests" "-
command-line()
normal-top-level()
Test file-notify-test03-events condition:
(ert-test-failed
((should
(file-notify--test-with-events-check events))
:form
(file-notify--test-with-events-check
((created changed deleted deleted stopped)))
:value nil :explanation "Received events do not match expected events
(created changed deleted)
(created changed deleted deleted stopped)"))
FAILED 4/8 file-notify-test03-events (6.078224 sec)
Reverting buffer `file-notify-testac92zf'.
Reverting buffer `file-notify-testac92zf'.
passed 5/8 file-notify-test04-autorevert (6.008533 sec)
Test file-notify-test05-file-validity backtrace:
signal(ert-test-failed (((should (file-notify--test-with-events-chec
ert-fail(((should (file-notify--test-with-events-check events)) :for
#f(compiled-function () #<bytecode 0xbb16fd>)()
ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
ert-run-test(#s(ert-test :name file-notify-test05-file-validity :doc
ert-run-or-rerun-test(#s(ert--stats :selector (not (or ... ...)) :te
ert-run-tests((not (or (tag :expensive-test) (tag :unstable))) #f(co
ert-run-tests-batch((not (or (tag :expensive-test) (tag :unstable)))
ert-run-tests-batch-and-exit((not (or (tag :expensive-test) (tag :un
eval((ert-run-tests-batch-and-exit '(not (or (tag :expensive-test) (
command-line-1(("-L" ":." "-l" "ert" "-l" "lisp/filenotify-tests" "-
command-line()
normal-top-level()
Test file-notify-test05-file-validity condition:
(ert-test-failed
((should
(file-notify--test-with-events-check events))
:form
(file-notify--test-with-events-check
((created changed deleted deleted stopped)))
:value nil :explanation "Received events do not match expected events
(created changed deleted)
(created changed deleted deleted stopped)"))
FAILED 6/8 file-notify-test05-file-validity (6.045527 sec)
Test file-notify-test06-dir-validity backtrace:
signal(ert-test-failed (((should-not (file-notify-valid-p file-notif
ert-fail(((should-not (file-notify-valid-p file-notify--test-desc))
#f(compiled-function () #<bytecode 0xbb1af5>)()
ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
ert-run-test(#s(ert-test :name file-notify-test06-dir-validity :docu
ert-run-or-rerun-test(#s(ert--stats :selector (not (or ... ...)) :te
ert-run-tests((not (or (tag :expensive-test) (tag :unstable))) #f(co
ert-run-tests-batch((not (or (tag :expensive-test) (tag :unstable)))
ert-run-tests-batch-and-exit((not (or (tag :expensive-test) (tag :un
eval((ert-run-tests-batch-and-exit '(not (or (tag :expensive-test) (
command-line-1(("-L" ":." "-l" "ert" "-l" "lisp/filenotify-tests" "-
command-line()
normal-top-level()
Test file-notify-test06-dir-validity condition:
(ert-test-failed
((should-not
(file-notify-valid-p file-notify--test-desc))
:form
(file-notify-valid-p
(1 . 0))
:value t))
FAILED 7/8 file-notify-test06-dir-validity (3.001878 sec)
passed 8/8 file-notify-test08-backup (3.058565 sec)
Ran 8 tests, 5 results as expected, 3 unexpected (2018-12-31 15:28:41+0000, 25.120320 sec)
3 unexpected results:
FAILED file-notify-test03-events
FAILED file-notify-test05-file-validity
FAILED file-notify-test06-dir-validity
next reply other threads:[~2018-12-31 16:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 16:14 Ted Zlatanov [this message]
2018-12-31 17:27 ` filenotify-tests.el failing inside Docker debian:stretch Michael Albinus
2018-12-31 18:48 ` Ted Zlatanov
2018-12-31 19:39 ` Ted Zlatanov
2019-01-02 8:36 ` Michael Albinus
2019-01-02 14:19 ` Ted Zlatanov
2019-01-06 15:40 ` Michael Albinus
2019-01-07 13:17 ` Michael Albinus
2019-01-07 21:18 ` Ted Zlatanov
2019-01-08 8:35 ` Michael Albinus
2019-01-09 14:01 ` Ted Zlatanov
2019-01-02 8:31 ` Michael Albinus
2019-01-02 14:16 ` Ted Zlatanov
2019-01-02 14:31 ` Michael Albinus
2019-01-02 14:40 ` Ted Zlatanov
2019-01-02 14:48 ` Michael Albinus
2019-01-02 17:10 ` Ted Zlatanov
2019-01-03 14:32 ` Michael Albinus
2019-01-03 15:50 ` Ted Zlatanov
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=h8etllmd.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@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.