From: Mark Hatle <mark.hatle@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: [PATCH 2/3] lib/layerindexlib/tests/cooker.py: Fix topdir to use an absolute (real) path
Date: Tue, 25 Sep 2018 11:07:07 -0400 [thread overview]
Message-ID: <20180925150708.2983-3-mark.hatle@windriver.com> (raw)
In-Reply-To: <20180925150708.2983-1-mark.hatle@windriver.com>
The test case needs to access test case files. Different versions of python
may return absolute or relative locations in __file__. Use the same approach
as other test cases in determining the location of the test files.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
---
lib/layerindexlib/tests/cooker.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/layerindexlib/tests/cooker.py b/lib/layerindexlib/tests/cooker.py
index 9ce6e8c..46d006b 100644
--- a/lib/layerindexlib/tests/cooker.py
+++ b/lib/layerindexlib/tests/cooker.py
@@ -32,7 +32,7 @@ class LayerIndexCookerTest(LayersTest):
# configure the test data. But we can emulate the basics of the layer.conf
# files, so that is what we will do.
- new_topdir = os.path.join(os.path.dirname(__file__), "testdata")
+ new_topdir = topdir = os.path.join(os.path.dirname(os.path.realpath(__file__)), "testdata")
new_bbpath = os.path.join(new_topdir, "build")
self.d.setVar('TOPDIR', new_topdir)
--
1.8.3.1
next prev parent reply other threads:[~2018-09-25 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 15:07 [PATCH 0/3] Fix bitbake-selftest failures Mark Hatle
2018-09-25 15:07 ` [PATCH 1/3] lib/bb/tests/parse.py: Test case was changing chdir Mark Hatle
2018-09-25 15:07 ` Mark Hatle [this message]
2018-09-25 15:18 ` [PATCH 2/3] lib/layerindexlib/tests/cooker.py: Fix topdir to use an absolute (real) path Mark Hatle
2018-09-25 15:07 ` [PATCH 3/3] lib/layerindexlib/tests/restapi.py: Fix test cases when BB_SKIP_NETTETS=yes Mark Hatle
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=20180925150708.2983-3-mark.hatle@windriver.com \
--to=mark.hatle@windriver.com \
--cc=bitbake-devel@lists.openembedded.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 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.