GNU bug report logs - #79124
emacs -Q doesn't give me a clean slate

Previous Next

Full log

View this message in rfc822 format

From: Lynn Winebarger <owinebar <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 79124 <at> debbugs.gnu.org, Rudolf Schlatte <rudi <at> constantly.at>
Subject: bug#79124: emacs -Q doesn't give me a clean slate
Date: Mon, 4 Aug 2025 10:12:09 -0400

[Message part 1 (text/plain, inline)]

On Mon, Aug 4, 2025, 10:00 AM Eli Zaretskii <eliz <at> gnu.org> wrote:

> > From: Rudolf Schlatte <rudi <at> constantly.at>
> > Date: Mon, 04 Aug 2025 07:13:42 +0200
> >
> > Paul Eggert <eggert <at> cs.ucla.edu> writes:
> >
> > > It's a matter of priorities. If we want Emacs to be easy to test
> > > reproducibly, there's a real need for improvement here. If we think
> > > this sort of testing is unimportant, then indeed we should stop this
> > > discussion.
> >
> > You probably are already aware, but (if my understanding is correct) the
> > code that is tested with a non-existent or non-writable home directory
> > is byte-code interpreted, whereas with a writable home directory the
> > code that is run is natively compiled.  So the tests will test something
> > subtly different than what end users will run.
>
> Yes, this is another downside of suppressing native compilation in a
> build that's supposed to use it in production.
>

For reproducible testing of anything other than the support of on-demand
native compilation, the tester should build two versions of emacs.  The
first --with-native-compilation=no, the second with
--with-native-compilation=aot.  Then the use of byte- or native code will
be deterministic even if HOME doesn't exist.

Lynn

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.