From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH v3 4/7] CI: Do not run QEMU start tests from Gitlab
Date: Wed, 16 Mar 2022 10:16:44 +0300 [thread overview]
Message-ID: <20220316071647.8919-5-amikan@ilbers.de> (raw)
In-Reply-To: <20220316071647.8919-1-amikan@ilbers.de>
To leave existing behaviour of vm_start tests execution introduce
'--norun' flag to use it in .gitlab-ci.yml scripts.
Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
---
.gitlab-ci.yml | 4 ++--
scripts/ci_build.sh | 8 ++++++++
2 files changed, 10 insertions(+), 2 deletions(-)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 37882ef..d0488a0 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -27,7 +27,7 @@ fast-ci:
except:
- schedules
script:
- - scripts/ci_build.sh -q -f -d
+ - scripts/ci_build.sh -q -f -d -n
full-ci:
<<: *common-build
@@ -37,7 +37,7 @@ full-ci:
- PREVIOUS_SHA="$(cat .CI_COMMIT_SHA || true)"
- if [ "$CI_COMMIT_SHA" != "$PREVIOUS_SHA" ]; then
echo "$CI_COMMIT_SHA" > .CI_COMMIT_SHA;
- scripts/ci_build.sh -q -c -r -d;
+ scripts/ci_build.sh -q -c -r -d -n;
fi
cache:
key: "$CI_COMMIT_REF_SLUG"
diff --git a/scripts/ci_build.sh b/scripts/ci_build.sh
index fe139d1..ea69553 100755
--- a/scripts/ci_build.sh
+++ b/scripts/ci_build.sh
@@ -52,6 +52,7 @@ show_help() {
echo " -f, --fast cross build reduced set of configurations."
echo " -q, --quiet suppress verbose bitbake output."
echo " -r, --repro enable use of cached base repository."
+ echo " -n, --norun do not execute QEMU run tests."
echo " --help display this message and exit."
echo
echo "Exit status:"
@@ -100,6 +101,9 @@ do
-s|--sign) shift ;;
esac
;;
+ -n|--norun)
+ NORUN="1"
+ ;;
*)
echo "error: invalid parameter '$key', please try '--help' to get list of supported parameters"
exit $ES_BUG
@@ -113,6 +117,10 @@ if [ -z "$REPRO_BUILD" ]; then
TAGS="$TAGS,-repro"
fi
+if [ -n "$NORUN" ]; then
+ TAGS="$TAGS,-startvm"
+fi
+
# Provide working path
mkdir -p .config/avocado
cat <<EOF > .config/avocado/avocado.conf
--
2.17.1
next prev parent reply other threads:[~2022-03-16 7:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 7:16 [PATCH v3 0/7] Unify build and run test cases Anton Mikanovich
2022-03-16 7:16 ` [PATCH v3 1/7] CI: Reorganize testsuite folders Anton Mikanovich
2022-03-16 7:16 ` [PATCH v3 2/7] CI: Migrate all tests to one location Anton Mikanovich
2022-03-16 7:16 ` [PATCH v3 3/7] CI: Adopt vm_start test logging Anton Mikanovich
2022-03-16 7:16 ` Anton Mikanovich [this message]
2022-03-16 7:16 ` [PATCH v3 5/7] CI: Rename build_test.py to citest.py Anton Mikanovich
2022-03-16 7:16 ` [PATCH v3 6/7] CI: Change QEMU boot logs format Anton Mikanovich
2022-03-16 7:16 ` [PATCH v3 7/7] CI: Add timeout setting to ci_build Anton Mikanovich
2022-03-23 7:00 ` [PATCH v3 0/7] Unify build and run test cases 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=20220316071647.8919-5-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