unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: nikolay.kudryavtsev@gmail.com, emacs-devel@gnu.org
Subject: Re: master 65fe177: Don't use pdumper-stats with unexec
Date: Sun, 02 May 2021 15:52:41 +0300	[thread overview]
Message-ID: <83sg3570x2.fsf@gnu.org> (raw)
In-Reply-To: <87v981fncs.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun,  02 May 2021 12:20:51 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Sun, 02 May 2021 12:20:51 +0200
> Cc: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
> 
> eliz@gnu.org (Eli Zaretskii) writes:
> 
> >     Don't use pdumper-stats with unexec
> >
> >     * lisp/emacs-lisp/bytecomp.el (byte-compile-refresh-preloaded): Check if
> >     pdumper-stats is bound before using it.
> 
> Some recent change (possibly this patch) leads to the following test
> failure:
> 
> 1 unexpected results:
>    FAILED  bytecomp-tests--dest-mountpoint

That test is skipped on the systems to which I have access, so someone
else will have to debug the failure.  Or does the detailed error
message tell something obvious?



  reply	other threads:[~2021-05-02 12:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210502101737.3076.72208@vcs0.savannah.gnu.org>
     [not found] ` <20210502101741.8586F20D0F@vcs0.savannah.gnu.org>
2021-05-02 10:20   ` master 65fe177: Don't use pdumper-stats with unexec Lars Ingebrigtsen
2021-05-02 12:52     ` Eli Zaretskii [this message]
2021-05-03  8:54       ` Lars Ingebrigtsen
2021-05-03 15:09         ` Nikolay Kudryavtsev
2021-05-30 13:28         ` Nikolay Kudryavtsev
2021-05-31  5:37           ` Lars Ingebrigtsen
2021-05-31 19:46             ` Nikolay Kudryavtsev
2021-06-01  6:15               ` Lars Ingebrigtsen
2021-06-01 18:39               ` Lars Ingebrigtsen
2021-06-01 18:54                 ` Nikolay Kudryavtsev
2021-06-02  5:24                   ` 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

  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=83sg3570x2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=nikolay.kudryavtsev@gmail.com \
    /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).