From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH] CI: Fix paths for the latest Avocado version
Date: Fri, 22 Oct 2021 09:51:10 +0300 [thread overview]
Message-ID: <1634885470-19422-1-git-send-email-amikan@ilbers.de> (raw)
We can't use relative path for logdir in Avocado 89.0+ because it fails with:
FileNotFoundError: [Errno 2] No such file or directory: '.../whiteboard'
Move to absolute paths to be able to use the latest version.
Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
---
scripts/ci_build.sh | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/scripts/ci_build.sh b/scripts/ci_build.sh
index 32054c4a..5ff455e3 100755
--- a/scripts/ci_build.sh
+++ b/scripts/ci_build.sh
@@ -21,8 +21,7 @@ if ! command -v avocado > /dev/null; then
rm -rf /tmp/avocado_venv
virtualenv --python python3 /tmp/avocado_venv
source /tmp/avocado_venv/bin/activate
- # The latest working version of Avocado framework
- pip install avocado-framework==88.0
+ pip install avocado-framework
fi
# Get Avocado build tests path
@@ -121,10 +120,10 @@ set -x
mkdir -p .config/avocado
cat <<EOF > .config/avocado/avocado.conf
[datadir.paths]
-base_dir = $BUILD_DIR/
-test_dir = $BUILD_DIR/tests
-data_dir = $BUILD_DIR/data
-logs_dir = $BUILD_DIR/job-results
+base_dir = $(realpath $BUILD_DIR)/
+test_dir = $(realpath $BUILD_DIR)/tests
+data_dir = $(realpath $BUILD_DIR)/data
+logs_dir = $(realpath $BUILD_DIR)/job-results
EOF
export VIRTUAL_ENV="./"
--
2.20.1
next reply other threads:[~2021-10-22 6:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 6:51 Anton Mikanovich [this message]
2021-10-22 7:57 ` [PATCH] CI: install avocado debian packages from isar-build.org Henning Schild
2021-10-22 7:59 ` Henning Schild
2021-10-22 8:08 ` Henning Schild
2021-10-26 7:37 ` Anton Mikanovich
2021-10-26 8:02 ` Henning Schild
2021-11-02 16:21 ` [PATCH] CI: Fix paths for the latest Avocado version 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=1634885470-19422-1-git-send-email-amikan@ilbers.de \
--to=amikan@ilbers.de \
--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