From: Stephen Berman <stephen.berman@gmx.net>
To: emacs-devel@gnu.org
Subject: test failures
Date: Fri, 21 Aug 2020 22:23:05 +0200 [thread overview]
Message-ID: <87zh6nd9zq.fsf@gmx.net> (raw)
I just built current master (at commit 348686b3f3) and then ran make
check (for the first time in a long time), and this is the result:
SUMMARY OF TEST RESULTS
-----------------------
Files examined: 298
Ran 4216 tests, 4148 results as expected, 20 unexpected, 48 skipped
3 files contained unexpected results:
lisp/progmodes/elisp-mode-tests.log
lisp/help-fns-tests.log
lisp/emacs-lisp/cl-generic-tests.log
Here are the tests that unexpectedly failed:
Ran 45 tests, 28 results as expected, 14 unexpected, 3 skipped (2020-08-21 21:40:33+0200, 2.127913 sec)
14 unexpected results:
FAILED xref-elisp-test-find-defs-defgeneric-co-located-default
FAILED xref-elisp-test-find-defs-defgeneric-el
FAILED xref-elisp-test-find-defs-defgeneric-implicit-generic
FAILED xref-elisp-test-find-defs-defgeneric-no-default
FAILED xref-elisp-test-find-defs-defgeneric-no-methods
FAILED xref-elisp-test-find-defs-defgeneric-separate-default
FAILED xref-elisp-test-find-defs-define-overload-co-located-default
FAILED xref-elisp-test-find-defs-define-overload-no-default
FAILED xref-elisp-test-find-defs-define-overload-no-methods
FAILED xref-elisp-test-find-defs-define-overload-separate-default
FAILED xref-elisp-test-find-defs-defun-defvar-el
FAILED xref-elisp-test-find-defs-defun-el
FAILED xref-elisp-test-find-defs-defvar-el
FAILED xref-elisp-test-find-defs-feature-el
Ran 19 tests, 14 results as expected, 5 unexpected (2020-08-21 21:39:58+0200, 0.689917 sec)
5 unexpected results:
FAILED help-fns-test-alias-to-defun
FAILED help-fns-test-bug23887
FAILED help-fns-test-lisp-defsubst
FAILED help-fns-test-lisp-defun
FAILED help-fns-test-lisp-macro
Ran 17 tests, 16 results as expected, 1 unexpected (2020-08-21 21:39:05+0200, 0.073067 sec)
1 unexpected results:
FAILED cl-generic-tests--method-files--finds-methods
Are these known failures, or did something go wrong with my build, or
would perhaps make bootstrap eliminate the failures?
Steve Berman
next reply other threads:[~2020-08-21 20:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 20:23 Stephen Berman [this message]
2020-08-21 20:36 ` test failures Lars Ingebrigtsen
2020-08-21 20:45 ` Stephen Berman
2020-08-22 11:32 ` Stephen Berman
2020-08-22 6:31 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2020-10-28 3:00 Test Failures Vin Shelton
2020-10-28 8:20 ` Lars Ingebrigtsen
2020-10-28 13:59 ` Vin Shelton
2020-10-29 2:30 ` Dmitry Gutov
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=87zh6nd9zq.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--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 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).