From: "Fabian Groffen" <grobian@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage-utils:master commit in: tests/atom_explode/
Date: Wed, 20 Mar 2019 07:57:19 +0000 (UTC) [thread overview]
Message-ID: <1553068426.11ac8188bfdee030fa233fd4480f35c2d8e3df69.grobian@gentoo> (raw)
commit: 11ac8188bfdee030fa233fd4480f35c2d8e3df69
Author: Fabian Groffen <grobian <AT> gentoo <DOT> org>
AuthorDate: Wed Mar 20 07:53:46 2019 +0000
Commit: Fabian Groffen <grobian <AT> gentoo <DOT> org>
CommitDate: Wed Mar 20 07:53:46 2019 +0000
URL: https://gitweb.gentoo.org/proj/portage-utils.git/commit/?id=11ac8188
tests: ensure repeatable results on any host when TRAVIS_OS_NAME is set
Always use the static "cache" of ebuilds provided in the tree, even if
we find a tree when we're testing in Travis mode.
Signed-off-by: Fabian Groffen <grobian <AT> gentoo.org>
tests/atom_explode/dotest | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/atom_explode/dotest b/tests/atom_explode/dotest
index 3a45fc1..f47d44f 100755
--- a/tests/atom_explode/dotest
+++ b/tests/atom_explode/dotest
@@ -3,7 +3,7 @@
. ../init.sh || exit 1
PORTDIR=$(DEBUG=: q -Ch 2>&1 | grep ^PORTDIR | awk '{print $NF}')
-if [[ -d "${PORTDIR}"/metadata/md5-cache ]] &&
+if [[ -z ${TRAVIS_OS_NAME} && -d "${PORTDIR}"/metadata/md5-cache ]] &&
"$s"/atom-explode.py < /dev/null >& /dev/null ;
then
pushd "${PORTDIR}"/metadata/md5-cache >/dev/null || exit $?
next reply other threads:[~2019-03-20 7:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 7:57 Fabian Groffen [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-29 10:58 [gentoo-commits] proj/portage-utils:master commit in: tests/atom_explode/ Fabian Groffen
2019-06-10 10:09 Fabian Groffen
2018-08-01 12:18 Fabian Groffen
2018-05-18 18:30 Fabian Groffen
2018-03-30 18:27 Fabian Groffen
2016-02-14 1:26 Mike Frysinger
2015-11-26 8:59 Mike Frysinger
2015-02-21 0:00 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=1553068426.11ac8188bfdee030fa233fd4480f35c2d8e3df69.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