From: Lars Ingebrigtsen <larsi@gnus.org>
To: 51308@debbugs.gnu.org
Cc: Andrea Corallo <akrl@sdf.org>
Subject: bug#51308: 29.0.50; A number of tests fail with AOT
Date: Thu, 21 Oct 2021 06:31:26 +0200 [thread overview]
Message-ID: <87k0i7gfs1.fsf@gnus.org> (raw)
In-Reply-To: <87o87jlfr7.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 20 Oct 2021 20:20:44 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Files examined: 375
> Ran 5645 tests, 5513 results as expected, 8 unexpected, 124 skipped
> 5 files contained unexpected results:
> lisp/net/socks-tests.log
> lisp/loadhist-tests.log
> lisp/hi-lock-tests.log
> lisp/emacs-lisp/ert-tests.log
> lisp/calendar/todo-mode-tests.log
I've now fixed
> lisp/hi-lock-tests.log
> lisp/calendar/todo-mode-tests.log
which were about wrong number of parameters (which native-comp is more
strict about) when redefining functions.
> lisp/emacs-lisp/ert-tests.log
is about
(backtrace-frame-fun (car (ert-test-failed-backtrace result)))
=> ert-fail
(car (ert-test-failed-backtrace result))
=> #s(backtrace-frame t ert-fail ("foo") nil ((debugger-may-continue . t) (inhibit-redisplay) (inhibit-debugger . t) (inhibit-changing-match-data)) nil nil)
while it's `signal' when ert isn't natively compiled.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-10-21 4:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 18:20 bug#51308: 29.0.50; A number of tests fail with AOT Lars Ingebrigtsen
2021-10-20 18:28 ` Eli Zaretskii
2021-10-21 3:04 ` Lars Ingebrigtsen
2021-10-21 4:20 ` Lars Ingebrigtsen
2022-03-12 21:32 ` bug#51308: bug#52138: 29.0.50; Some tests fail on emba when run with native compilation Lars Ingebrigtsen
2022-03-13 5:45 ` Eli Zaretskii
2022-03-13 14:14 ` Lars Ingebrigtsen
2022-03-13 16:40 ` bug#52138: " Eli Zaretskii
2021-10-21 4:31 ` Lars Ingebrigtsen [this message]
2022-03-12 21:42 ` Lars Ingebrigtsen
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=87k0i7gfs1.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=51308@debbugs.gnu.org \
--cc=akrl@sdf.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.