From: <mingli.yu@windriver.com>
To: <meta-virtualization@lists.yoctoproject.org>,
<patrick.wicki@siemens.com>
Subject: [PATCH] netavark: Make ptest run
Date: Wed, 15 May 2024 10:54:30 +0800 [thread overview]
Message-ID: <20240515025431.3049144-1-mingli.yu@windriver.com> (raw)
In-Reply-To: <17C92B9B397D8953.1247@lists.yoctoproject.org>
From: Mingli Yu <mingli.yu@windriver.com>
Fixes:
# ./run-ptest
/tmp/bats-run-ELGGaA/bats.18820.src: line 5: To: command not found
1..1
not ok 1 bats-gather-tests
# (in test file test/README.md, line 5)
# `To run the tests locally in your sandbox, you can use one of these methods:' failed with status 127
Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
---
recipes-containers/netavark/files/run-ptest | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/recipes-containers/netavark/files/run-ptest b/recipes-containers/netavark/files/run-ptest
index 7e017ae2..f6f90b15 100644
--- a/recipes-containers/netavark/files/run-ptest
+++ b/recipes-containers/netavark/files/run-ptest
@@ -5,4 +5,10 @@ shopt -s extglob
# Skip the plugin tests because those example plugins are built only while
# running cargo test and for this to work as a ptest they would need to be cross
# compiled and installed as part of the ptest.
-NETAVARK=/usr/libexec/podman/netavark bats test/!(*-plugin.bats)
+for i in `ls test`; do
+ if [ $i == "200-bridge-firewalld.bats" ] || [ $i == "500-plugin.bats" ] ; then
+ continue
+ fi
+ [ ${i: -4 -1} == ".bats" ] && NETAVARK=/usr/libexec/podman/netavark bats test/$i
+done
+
--
2.25.1
next parent reply other threads:[~2024-05-15 2:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17C92B9B397D8953.1247@lists.yoctoproject.org>
2024-05-15 2:54 ` mingli.yu [this message]
2024-05-28 19:14 ` [meta-virtualization] [PATCH] netavark: Make ptest run Bruce Ashfield
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=20240515025431.3049144-1-mingli.yu@windriver.com \
--to=mingli.yu@windriver.com \
--cc=meta-virtualization@lists.yoctoproject.org \
--cc=patrick.wicki@siemens.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).