From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eli Zaretskii <eliz@gnu.org>, Andrea Corallo <akrl@sdf.org>,
57152@debbugs.gnu.org
Subject: bug#57152: 29.0.50; Emacs executable isn't rebuilt when loaddefs.el is modified
Date: Fri, 19 Aug 2022 11:24:36 +0200 [thread overview]
Message-ID: <48845bf9-f24b-a2f8-9940-833cbc000354@gmail.com> (raw)
In-Reply-To: <87fshthg74.fsf@gnus.org>
On 22-08-18 14:46 , Lars Ingebrigtsen wrote:
> So I just went ahead and pushed it. :-)
Oh no :-).
> There is one pretty strange thing though, which I can't explain. I once
>> got an error "trying to load incoherent eln" which is mentioned in
>> bug#45103. I can't say much else about this though, not even what the
>> cause of this might be. It was a build with -j8 if that matters. Maybe
>> elns are modified during dumping, so that a second dump cannot be done?
>> But that wouldn't explain why it succeeds most of the time. No idea,
>> and not easily reproducible, alas.
> Yes, I've seen those, too, but very seldom (like -- once a month?), and
> I haven't been able to reproduce it.
If anyone reading this has any idea, be it just a gut feeling or
something, how to reproduce this failure, even if not 100% reliable, I'd
be grateful to hear it.
next prev parent reply other threads:[~2022-08-19 9:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 7:03 bug#57152: 29.0.50; Emacs executable isn't rebuilt when loaddefs.el is modified Eli Zaretskii
2022-08-12 15:14 ` Lars Ingebrigtsen
2022-08-12 15:29 ` Eli Zaretskii
2022-08-13 11:42 ` Lars Ingebrigtsen
2022-08-15 10:07 ` Lars Ingebrigtsen
2022-08-15 11:58 ` Eli Zaretskii
2022-08-15 13:32 ` Gerd Möllmann
2022-08-17 10:40 ` Lars Ingebrigtsen
2022-08-17 13:50 ` Gerd Möllmann
2022-08-18 12:46 ` Lars Ingebrigtsen
2022-08-19 9:24 ` Gerd Möllmann [this message]
2022-08-17 10:34 ` Lars Ingebrigtsen
2022-08-17 12:08 ` Eli Zaretskii
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=48845bf9-f24b-a2f8-9940-833cbc000354@gmail.com \
--to=gerd.moellmann@gmail.com \
--cc=57152@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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.