From: Eli Zaretskii <eliz@gnu.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: rgm@gnu.org, 47138@debbugs.gnu.org
Subject: bug#47138: 28.0.50; comp-tests suite creates a /nonexistent directory
Date: Sun, 21 Mar 2021 21:00:11 +0200 [thread overview]
Message-ID: <834kh4badg.fsf@gnu.org> (raw)
In-Reply-To: <xjf5z1ktnwj.fsf@sdf.org> (bug-gnu-emacs@gnu.org)
> Cc: 47138@debbugs.gnu.org
> Date: Sun, 21 Mar 2021 17:30:36 +0000
> From: Andrea Corallo via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> if we have a better idea on how to detect we are running the testsuite
> we can use that in place. Maybe defining a dedicated env variable
> during the build?
Howe about EMACS_ELN_PATH, similar to EMACS_LOADPATH? Then the test
Makefile could set it for the src/comp-tests test.
next prev parent reply other threads:[~2021-03-21 19:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-14 15:59 bug#47138: 28.0.50; comp-tests suite creates a /nonexistent directory Eli Zaretskii
2021-03-16 17:32 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-16 18:36 ` Eli Zaretskii
2021-03-21 8:43 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-21 10:33 ` Eli Zaretskii
2021-03-21 16:28 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-21 16:57 ` Eli Zaretskii
2021-03-21 18:53 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-21 17:17 ` Glenn Morris
2021-03-21 17:30 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-21 19:00 ` Eli Zaretskii [this message]
2021-03-24 14:47 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-24 12:30 ` Lars Ingebrigtsen
2022-05-24 14:16 ` Eli Zaretskii
2022-05-24 14:18 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834kh4badg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=47138@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=rgm@gnu.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.