All of lore.kernel.org
 help / color / mirror / Atom feed
From: patrick@subset.ch
To: meta-virtualization@lists.yoctoproject.org
Cc: Patrick Wicki <patrick.wicki@siemens.com>
Subject: [meta-virtualization][PATCH 2/2] netavark: skip plugins in ptest
Date: Fri, 25 Aug 2023 16:51:48 +0200	[thread overview]
Message-ID: <20230825145148.234559-2-patrick@subset.ch> (raw)
In-Reply-To: <20230825145148.234559-1-patrick@subset.ch>

From: Patrick Wicki <patrick.wicki@siemens.com>

Skip the plugin tests that were introduced in 1.6.0 and lead to ptest
failure.

Signed-off-by: Patrick Wicki <patrick.wicki@siemens.com>
---
 recipes-containers/netavark/files/run-ptest | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/recipes-containers/netavark/files/run-ptest b/recipes-containers/netavark/files/run-ptest
index 41a37dce..7e017ae2 100644
--- a/recipes-containers/netavark/files/run-ptest
+++ b/recipes-containers/netavark/files/run-ptest
@@ -1,3 +1,8 @@
 #!/bin/bash
 
-NETAVARK=/usr/libexec/podman/netavark bats ./test/
+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)
-- 
2.41.0



  reply	other threads:[~2023-08-25 14:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 14:51 [meta-virtualization][PATCH 1/2] netavark: require iputils for ptest patrick
2023-08-25 14:51 ` patrick [this message]
2024-04-24  8:57   ` [meta-virtualization][PATCH 2/2] netavark: skip plugins in ptest Yu, Mingli
2023-08-27 13:26 ` [meta-virtualization][PATCH 1/2] netavark: require iputils for ptest 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=20230825145148.234559-2-patrick@subset.ch \
    --to=patrick@subset.ch \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.