all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Jens Schmidt <jschmidt4gnu@vodafonemail.de>
Cc: emacs-devel@gnu.org, Andrea Corallo <acorallo@gnu.org>
Subject: Re: Native compilation unit tests failing since last weekend or so
Date: Fri, 27 Oct 2023 21:29:48 +0000	[thread overview]
Message-ID: <ZTwrzAbpeq9U1Uz_@ACM> (raw)
In-Reply-To: <ec08c737-c734-496c-a6e3-aa9a45aecc2b@vodafonemail.de>

Hello, Jens.

On Fri, Oct 27, 2023 at 21:10:38 +0200, Jens Schmidt wrote:
> I have been hoping these would go away ... on GNU/Linux, emacs-master,
> with "-C --with-native-compilation --with-mailutils", after make
> bootstrap:

Same here: I've been patiently waiting for them to get fixed, but
without taking the trouble to report them.  ;-(

> SUMMARY OF TEST RESULTS
> -----------------------
> Files examined: 498
> Ran 7568 tests, 7303 results as expected, 43 unexpected, 222 skipped
> 3 files contained unexpected results:
>   src/comp-tests.log
>   lisp/emacs-lisp/comp-cstr-tests.log
>   lisp/emacs-lisp/bytecomp-tests.log

> Am I the only one seeing this?

No, I see these, too.  Exactly 43 successes.

They seem mainly to be due to "fixnum" and "integer" getting confused in
some fashion, and things like that.

> Please let me know if you need more information on that.

-- 
Alan Mackenzie (Nuremberg, Germany).



  reply	other threads:[~2023-10-27 21:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-27 19:10 Native compilation unit tests failing since last weekend or so Jens Schmidt
2023-10-27 21:29 ` Alan Mackenzie [this message]
2023-10-30 20:24 ` Jens Schmidt
2023-11-01  8:21   ` Andrea Corallo
2023-11-03 20:25   ` bytecomp-tests still failing after Mattias' commit a3db503351e9 Jens Schmidt
2023-11-04  9:32     ` Mattias Engdegård

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=ZTwrzAbpeq9U1Uz_@ACM \
    --to=acm@muc.de \
    --cc=acorallo@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jschmidt4gnu@vodafonemail.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 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.