unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo via "Emacs development discussions." <emacs-devel@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Michael Albinus <michael.albinus@gmx.de>, emacs-devel@gnu.org
Subject: Re: master c622627: * Clean-up temporary eln test-suite directory when exiting (bug#48060)
Date: Wed, 28 Apr 2021 19:19:58 +0000	[thread overview]
Message-ID: <xjf7dkm1ajl.fsf@sdf.org> (raw)
In-Reply-To: <834kfqhakv.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 28 Apr 2021 15:12:32 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Michael Albinus <michael.albinus@gmx.de>
>> Date: Wed, 28 Apr 2021 13:30:37 +0200
>> Cc: Andrea Corallo <akrl@sdf.org>
>> 
>> This expects, that Emacs tests are run only via calling test/Makefile
>> (which sets $HOME to "/nonexistent"). This is not true, tests can also
>> be started interactively.

Nothing prevents tests to be run without using the makefile or even in a
normal interactive session.  Is just that in these cases the product of
native compilation will end-up in "~/.emacs.d/eln-cache".

>> And I find it problematic to have a dependency in startup.el to a
>> Makefile of the test directory.
>
> I tend to agree.
>
> Andrea, is the problem with these directories specific to comp-tests,
> or does it happen in any test run in the native-compilation build?

Every test might need to compile native code, not only directly invoking
`native-compile' & friends but also in case a trampoline has to be
synthesized.

Regards

  Andrea



  reply	other threads:[~2021-04-28 19:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210427213426.6174.29110@vcs0.savannah.gnu.org>
     [not found] ` <20210427213427.8318C20D0F@vcs0.savannah.gnu.org>
2021-04-28 11:30   ` master c622627: * Clean-up temporary eln test-suite directory when exiting (bug#48060) Michael Albinus
2021-04-28 12:12     ` Eli Zaretskii
2021-04-28 19:19       ` Andrea Corallo via Emacs development discussions. [this message]
2021-04-28 19:25         ` Eli Zaretskii
2021-04-28 19:45           ` Andrea Corallo via Emacs development discussions.
2021-04-29  5:20             ` Eli Zaretskii
2021-04-29  8:20               ` Andrea Corallo via Emacs development discussions.
2021-04-29  8:29                 ` Andrea Corallo via Emacs development discussions.
2021-04-29  9:24                   ` Eli Zaretskii
2021-04-29 14:41                     ` Andrea Corallo via Emacs development discussions.
2021-04-29 15:11                       ` Eli Zaretskii
2021-04-29 15:26                         ` Michael Albinus
2021-04-29 15:47                           ` Eli Zaretskii
2021-04-29 20:47                           ` chad
2021-04-30  5:09                             ` Eli Zaretskii
2021-04-29  9:21                 ` Eli Zaretskii
2021-04-28 19:30         ` Michael Albinus
2021-04-28 19:47           ` Andrea Corallo via Emacs development discussions.

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=xjf7dkm1ajl.fsf@sdf.org \
    --to=emacs-devel@gnu.org \
    --cc=akrl@sdf.org \
    --cc=eliz@gnu.org \
    --cc=michael.albinus@gmx.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 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).