From: Adriaan Schmidt <adriaan.schmidt@siemens.com>
To: isar-users@googlegroups.com
Cc: Adriaan Schmidt <adriaan.schmidt@siemens.com>
Subject: [PATCH v6 11/13] test: pass absolute path for build_dir
Date: Thu, 11 Nov 2021 07:47:26 +0100 [thread overview]
Message-ID: <20211111064728.2375760-12-adriaan.schmidt@siemens.com> (raw)
In-Reply-To: <20211111064728.2375760-1-adriaan.schmidt@siemens.com>
When having multiple calls to `perform_*_test` in one test case (which
is what a future test for the sstate cache will use), `build_dir`
gets mixed up if it's passed as a relative path. I observe that
the first bitbake has the correct build dir ($isar_root/build), but
the second one has $isar_root/build/build, and then fails.
I briefly tried fixing this in the testsuite itself, but did not
manage, so here's a workaround.
Signed-off-by: Adriaan Schmidt <adriaan.schmidt@siemens.com>
---
scripts/ci_build.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/ci_build.sh b/scripts/ci_build.sh
index 5ff455e..4ebd1a5 100755
--- a/scripts/ci_build.sh
+++ b/scripts/ci_build.sh
@@ -28,7 +28,7 @@ fi
BUILD_TEST_DIR="$(pwd)/testsuite/build_test"
# Start build in Isar tree by default
-BUILD_DIR=./build
+BUILD_DIR="$(pwd)/build"
# Check dependencies
DEPENDENCIES="umoci skopeo"
--
2.30.2
next prev parent reply other threads:[~2021-11-11 6:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 6:47 [PATCH v6 00/13] Add sstate-cache Adriaan Schmidt
2021-11-11 6:47 ` [PATCH v6 01/13] oe imports in central location Adriaan Schmidt
2021-11-11 6:47 ` [PATCH v6 02/13] images: create deploy dir Adriaan Schmidt
2021-11-11 6:47 ` [PATCH v6 03/13] rootfs: recursively depend on packages Adriaan Schmidt
2021-11-11 6:47 ` [PATCH v6 04/13] base: remove unneeded "before do_build" task dependencies Adriaan Schmidt
2021-11-11 6:47 ` [PATCH v6 05/13] dpkg: add explicit dependency to isar-apt Adriaan Schmidt
2021-11-11 6:47 ` [PATCH v6 06/13] meta: add sstate feature from oe Adriaan Schmidt
2021-11-11 6:47 ` [PATCH v6 07/13] sstate: configure Adriaan Schmidt
2021-11-11 6:47 ` [PATCH v6 08/13] sstate: add caching to isar-bootstrap Adriaan Schmidt
2021-11-11 6:47 ` [PATCH v6 09/13] sstate: add caching to rootfs Adriaan Schmidt
2021-11-11 6:47 ` [PATCH v6 10/13] sstate: add caching to debian packages Adriaan Schmidt
2021-11-11 6:47 ` Adriaan Schmidt [this message]
2021-11-11 6:47 ` [PATCH v6 12/13] test: make bitbake_args a list Adriaan Schmidt
2021-11-11 6:47 ` [PATCH v6 13/13] sstate: add test case Adriaan Schmidt
2021-11-16 16:46 ` Anton Mikanovich
2021-11-16 22:47 ` Henning Schild
2021-11-17 8:21 ` Schmidt, Adriaan
2021-11-17 16:51 ` Anton Mikanovich
2021-11-19 10:33 ` Schmidt, Adriaan
2021-12-02 9:19 ` [PATCH v6 00/13] Add sstate-cache Anton Mikanovich
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=20211111064728.2375760-12-adriaan.schmidt@siemens.com \
--to=adriaan.schmidt@siemens.com \
--cc=isar-users@googlegroups.com \
/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