public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Felix Moessbauer' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com, stefan-koch@siemens.com,
	Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH v2 4/4] testsuite: add test for KERNEL_LIBC_DEV_DEPLOY
Date: Mon,  3 Aug 2026 10:34:50 +0200	[thread overview]
Message-ID: <20260803083450.2048909-5-felix.moessbauer@siemens.com> (raw)
In-Reply-To: <20260803083450.2048909-1-felix.moessbauer@siemens.com>

Enabling KERNEL_LIBC_DEV_DEPLOY=1 results in a complex dependency chain
that is built, also depending on the distro version. We add a fast
parser check to ensure the expected targets are attracted / built.

Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
 testsuite/citest.py | 36 ++++++++++++++++++++++++++++++++++++
 1 file changed, 36 insertions(+)

diff --git a/testsuite/citest.py b/testsuite/citest.py
index 019bfb2c..2ba7962b 100644
--- a/testsuite/citest.py
+++ b/testsuite/citest.py
@@ -633,6 +633,42 @@ class KernelTests(CIBaseTest):
         self.init()
         self.perform_build_test(targets, image_install=' '.join(modules), lines=lines)
 
+    def test_libc_dev_deploy(self):
+        """Test that the linux-libc-dev packages are deployed (parse only)."""
+        targets = [
+            'mc:hikey-bookworm:isar-image-ci',
+            'mc:hikey-trixie:isar-image-ci'
+        ]
+        lines = [
+            "KERNEL_LIBC_DEV_DEPLOY = '1'",
+        ]
+        self.init()
+        buildlist, _ = self.generate_dependency_graph(targets, lines=lines)
+
+        with open(buildlist, 'r') as f:
+            built = set(line.strip() for line in f if line.strip())
+
+        # trixie produces arch=all linux-libc-dev packages, which are built by
+        # the dedicated -libctarget variant.
+        self.assertIn(
+            'mc:hikey-trixie:linux-mainline-libctarget', built,
+            "trixie: linux-mainline-libctarget (linux-libc-dev is not built)")
+
+        # bookworm produces an arch-specific linux-libc-dev, built by the base
+        # recipe itself; no -libctarget variant is needed.
+        self.assertIn(
+            'mc:hikey-bookworm:linux-mainline', built,
+            "bookworm: linux-mainline (linux-libc-dev is not built)")
+        self.assertNotIn(
+            'mc:hikey-bookworm:linux-mainline-libctarget', built,
+            "bookworm: unexpected -libctarget variant is built")
+
+        # The unrelated cip kernel must not be pulled in as libc-dev provider.
+        for target in built:
+            self.assertNotIn(
+                'linux-cip', target,
+                f"unexpected linux-cip provider pulled in: {target}")
+
 
 class InitRdBaseTest(CIBaseTest):
     """
-- 
2.53.0

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/20260803083450.2048909-5-felix.moessbauer%40siemens.com.

  parent reply	other threads:[~2026-08-03  8:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03  8:34 [PATCH v2 0/4] Fix kernel build and propagation of linux-libc-dev 'Felix Moessbauer' via isar-users
2026-08-03  8:34 ` [PATCH v2 1/4] kernel: drop implicit build dependency to build-essential 'Felix Moessbauer' via isar-users
2026-08-03  8:34 ` [PATCH v2 2/4] fix(kernel): restore building of linux-libc-dev 'Felix Moessbauer' via isar-users
2026-08-03  8:34 ` [PATCH v2 3/4] testsuite: emit output filenames in generate_dependency_graph 'Felix Moessbauer' via isar-users
2026-08-03  8:34 ` 'Felix Moessbauer' via isar-users [this message]
2026-08-05  8:42 ` [PATCH v2 0/4] Fix kernel build and propagation of linux-libc-dev Zhihang Wei

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=20260803083450.2048909-5-felix.moessbauer@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=jan.kiszka@siemens.com \
    --cc=stefan-koch@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