All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
	Matan Azrad <matan@nvidia.com>
Subject: [PATCH] net/vdev_netvsc: block driver in github action
Date: Mon, 23 Feb 2026 09:21:37 -0800	[thread overview]
Message-ID: <20260223172137.93558-1-stephen@networkplumber.org> (raw)

On Hyper-V systems (including Azure-hosted CI), the vdev_netvsc
driver auto-injects itself during vdev bus scan. This interferes
with other tests.

Suppress this by detecting via environment variable.

Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
 drivers/net/vdev_netvsc/vdev_netvsc.c | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/drivers/net/vdev_netvsc/vdev_netvsc.c b/drivers/net/vdev_netvsc/vdev_netvsc.c
index f4a84783ce..39d52b7541 100644
--- a/drivers/net/vdev_netvsc/vdev_netvsc.c
+++ b/drivers/net/vdev_netvsc/vdev_netvsc.c
@@ -805,6 +805,14 @@ vdev_netvsc_scan_callback(__rte_unused void *arg)
 /** Initialize the custom scan. */
 RTE_INIT(vdev_netvsc_custom_scan_add)
 {
+	/*
+	 * Hack: github actions run on Azure/Hyper-V container and don't
+	 * want any network devices in that environment to get intertwined
+	 * with any tests.
+	 */
+	if (getenv("GITHUB_ACTIONS"))
+		return;
+
 	if (rte_hypervisor_get() == RTE_HYPERVISOR_HYPERV)
 		rte_vdev_add_custom_scan(vdev_netvsc_scan_callback, NULL);
 }
-- 
2.51.0


             reply	other threads:[~2026-02-23 17:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23 17:21 Stephen Hemminger [this message]
2026-02-23 23:29 ` [PATCH] net/vdev_netvsc: block driver in github action Stephen Hemminger

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=20260223172137.93558-1-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.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.