[PATCH 1/3] testsuite: Allow using custom isar location in test initialization

[Uladzimir Bely <ubely@ilbers.de>]

By default, isar copy checked out by CI is used for the build.
This change allows to pass custom isar directory to start build from.

It may be useful if we need to have several independent builds started
from different initial directories in order to compare their results.

Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
---
 testsuite/cibuilder.py | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/testsuite/cibuilder.py b/testsuite/cibuilder.py
index 12f0e193..9c9f5a03 100755
--- a/testsuite/cibuilder.py
+++ b/testsuite/cibuilder.py
@@ -39,13 +39,13 @@ class CIBuilder(Test):
         self._file_handler.setFormatter(formatter)
         app_log.addHandler(self._file_handler)
 
-    def init(self, build_dir='build'):
+    def init(self, build_dir='build', isar_dir=isar_root):
         # initialize build_dir and setup environment
         # needs to run once (per test case)
         if hasattr(self, 'build_dir'):
             self.error("Broken test implementation: init() called multiple times.")
-        self.build_dir = os.path.join(isar_root, build_dir)
-        os.chdir(isar_root)
+        self.build_dir = os.path.join(isar_dir, build_dir)
+        os.chdir(isar_dir)
         os.environ["TEMPLATECONF"] = "meta-test/conf"
         path.usable_rw_dir(self.build_dir)
         output = process.getoutput('/bin/bash -c "source isar-init-build-env \
-- 
2.20.1