From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Temp files from testing are permanent...
Date: Thu, 16 Feb 2012 21:47:50 +0100 [thread overview]
Message-ID: <87lio2y07d.fsf@Rainer.invalid> (raw)
In-Reply-To: 8739aceycb.fsf@Rainer.invalid
Achim Gratz <Stromeko@nexgo.de> writes:
> Barring any setup or options I might have missed, it looks like I will
> have to do two things: first, set TMPDIR to a newly created directory
> during the test runs and second, remove that directory after the test
> (with an option to keep it for inspection and removing only with
> "clean").
Done and pushed to my Makefile fork on repo.or.cz.
Temporary test files automatically vaporize when the test suite
successfully runs and are left for inspection otherwise. If you need to
keep them regardless of the test result, define TEST_NO_AUTOCLEAN
non-empty. A new target cleantest can be used to remove the temporary
test directory and all its content whenever necessary, this is also done
when doing a "cleanall". The location of the temporary test directory
follows $TMPDIR and can be overriden in local.mk via variable testdir.
TMPDIR, if not already present in the environment, will default to /tmp,
which incidentally should resolve a bug in my tricky build environment
at work.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2012-02-16 20:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 18:31 Temp files from testing are permanent Achim Gratz
2012-02-14 23:12 ` Olaf Meeuwissen
2012-02-15 17:11 ` Achim Gratz
2012-02-15 18:02 ` Brian Wightman
2012-02-15 18:38 ` Achim Gratz
2012-02-16 20:47 ` Achim Gratz [this message]
2012-02-16 0:54 ` Olaf Meeuwissen
2012-02-16 18:14 ` Achim Gratz
2012-02-18 17:46 ` Eric Schulte
2012-02-18 18:48 ` Achim Gratz
2012-02-19 16:21 ` Eric Schulte
2012-02-19 17:03 ` Achim Gratz
2012-02-20 0:11 ` Olaf Meeuwissen
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lio2y07d.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=emacs-orgmode@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).