From: "Fabian Groffen" <grobian@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage-utils:master commit in: tests/
Date: Mon, 10 Jun 2019 10:09:06 +0000 (UTC) [thread overview]
Message-ID: <1560160705.f45d8de0bc9d477dce9b3ae7a0d958e089307473.grobian@gentoo> (raw)
commit: f45d8de0bc9d477dce9b3ae7a0d958e089307473
Author: Fabian Groffen <grobian <AT> gentoo <DOT> org>
AuthorDate: Mon Jun 10 09:58:25 2019 +0000
Commit: Fabian Groffen <grobian <AT> gentoo <DOT> org>
CommitDate: Mon Jun 10 09:58:25 2019 +0000
URL: https://gitweb.gentoo.org/proj/portage-utils.git/commit/?id=f45d8de0
tests: allow tmpdir to reside in a place defined by Q_TMPDIR
when using NFS or something like that, using local storage iso builddir
is nice, because of speed but more because also not all operations are
allowed on network shares, so using this in some scenarios allows to
pass the tests
Signed-off-by: Fabian Groffen <grobian <AT> gentoo.org>
tests/init.sh.in | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/init.sh.in b/tests/init.sh.in
index c031ae3..875e2af 100644
--- a/tests/init.sh.in
+++ b/tests/init.sh.in
@@ -68,7 +68,7 @@ end() {
}
mktmpdir() {
- local d=${1:-${ab}/tmp}
+ local d=${1:-${Q_TMPDIR:-${ab}}/q-tmp}
rm -rf "$d" && \
mkdir -p "$d" && \
pushd "$d" >/dev/null \
@@ -76,7 +76,7 @@ mktmpdir() {
}
_cleantmpdir() {
local cmd=$1; shift
- local d=${1:-${ab}/tmp}
+ local d=${1:-${Q_TMPDIR:-${ab}}/q-tmp}
popd >/dev/null
${cmd} "${d}" || fail "could not clean tmp dir '$d'"
}
next reply other threads:[~2019-06-10 10:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 10:09 Fabian Groffen [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-06 15:32 [gentoo-commits] proj/portage-utils:master commit in: tests/ Fabian Groffen
2021-12-27 18:13 Fabian Groffen
2021-12-23 12:55 Fabian Groffen
2021-12-13 8:39 Fabian Groffen
2020-05-25 19:15 Fabian Groffen
2020-05-25 19:06 Fabian Groffen
2020-05-25 18:40 Fabian Groffen
2020-01-18 13:09 Fabian Groffen
2020-01-02 21:25 Fabian Groffen
2020-01-02 20:48 Fabian Groffen
2015-06-03 15:44 Mike Frysinger
2015-02-21 18:06 Mike Frysinger
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=1560160705.f45d8de0bc9d477dce9b3ae7a0d958e089307473.grobian@gentoo \
--to=grobian@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox