public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Andreas Naumann' via isar-users" <isar-users@googlegroups.com>
To: Zhihang Wei <wzh@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH 0/2] Prevent adding unneeded package variants to recursive dependency chain
Date: Tue, 18 Nov 2025 15:47:50 +0100	[thread overview]
Message-ID: <52158cd5-e4de-4a3c-8a87-eccf75a997e4@emlix.com> (raw)
In-Reply-To: <e235ab70-7a44-4a92-b91a-71d398ad4560@ilbers.de>

Hello Zhihang,

Am 07.11.25 um 13:00 schrieb Zhihang Wei:
> Hi,
>
> the patch caused "citest.py:ReproTest.test_repro_unsigned" to fail on 
> full CI,
> when building target 'mc:qemuarm-bookworm:isar-image-base'.
>
> Log follows:
>
<snip>
>
> To redo the test using avocado:
> 1. Have a clean clone of isar, checkout to branch next and apply your 
> patches:
> $ git clone -b next https://github.com/ilbers/isar.git
> $ cd isar
> $ git am /path-to/0001-my-contribution-to-isar.patch
> 2. Disable unrelated targets to make error appears faster, by applying
> the following diff to "testsuite/citest.py":
>
> diff --git a/testsuite/citest.py b/testsuite/citest.py
> index a1214e9c..f81f46a3 100755
> --- a/testsuite/citest.py
> +++ b/testsuite/citest.py
> @@ -135,7 +135,6 @@ class ReproTest(CIBaseTest):
>
>      def test_repro_unsigned(self):
>          targets = [
> -            'mc:qemuamd64-bookworm:isar-image-base',
>              'mc:qemuarm-bookworm:isar-image-base',
>          ]
>
> 3.Run kas shell, setup CI prerequisites (avocado, qemu) and cleanup:
> $ ./kas/kas-container shell kas/isar.yaml --command \
>     "rm -rf /work/build/conf && /work/scripts/ci_setup.sh"
> 4.Run the failed test in fast:
> $ cd /work/testsuite
> $ avocado run citest.py:ReproTest.test_repro_unsigned$

Thank you for the instructions. I have tried to come up with a better 
integrateable test, just sent a set with it.

Even though with the changed test, the error you posted doesnt appear 
anymore (the new test and all other crossbuild and dev tests ran fine), 
I was not successful in running this test. I dont know if I ran into a 
timeout or if it is a real issue still. So because the runtime of the 
tests is extremly long, I finally gave up and sent the set anyway.

regards,
Andreas


>
> Best regards,
> Zhihang
>
> On 11/3/25 16:42, 'Andreas Naumann' via isar-users wrote:
>> This is a stripped down version of my previous
>> [RFC 0/5] Improving multiarch support for arch-incompatible packages
>>
>> For now, I've dropped all patches except the one which covers the 
>> problem
>> where targets in the dependency chain are built for both the host and 
>> the
>> target architecture while only one is needed.
>>
>> The second patch is a way to reproduce this. It's quite hacky, and
>> would need serious rework before integration into the testsuite.
>>
>> Andreas Naumann (2):
>>    rootfs: Prevent adding unneeded package variants to recursive
>>      dependency chain
>>    DONOTMERGE: testcase for transient native dependency
>>
>>   meta-isar/recipes-app/adduser/adduser.bb         | 6 ++++++
>>   meta-isar/recipes-app/gss/gss.bb                 | 5 +++++
>>   meta-isar/recipes-core/images/isar-image-base.bb | 2 ++
>>   meta/classes/rootfs.bbclass                      | 3 ++-
>>   4 files changed, 15 insertions(+), 1 deletion(-)
>>   create mode 100644 meta-isar/recipes-app/adduser/adduser.bb
>>   create mode 100644 meta-isar/recipes-app/gss/gss.bb
>>
>
-- 
Andreas Naumann

emlix GmbH
Headquarters: Berliner Str. 12, 37073 Goettingen, Germany
Phone +49 (0)551 30664-0, e-mail info@emlix.com
District Court of Goettingen, Registry Number HR B 3160
Managing Directors: Heike Jordan, Dr. Uwe Kracke
VAT ID No. DE 205 198 055
Office Berlin: Panoramastr. 1, 10178 Berlin, Germany
Office Bonn: Bachstr. 6, 53115 Bonn, Germany
http://www.emlix.com

-- 
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/52158cd5-e4de-4a3c-8a87-eccf75a997e4%40emlix.com.

      reply	other threads:[~2025-11-18 14:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03 15:42 'Andreas Naumann' via isar-users
2025-11-03 15:42 ` [PATCH 1/2] rootfs: " 'Andreas Naumann' via isar-users
2025-11-03 15:42 ` [PATCH 2/2] DONOTMERGE: testcase for transient native dependency 'Andreas Naumann' via isar-users
2025-11-03 15:52   ` 'MOESSBAUER, Felix' via isar-users
2025-11-03 17:00     ` 'Andreas Naumann' via isar-users
2025-11-07 12:00 ` [PATCH 0/2] Prevent adding unneeded package variants to recursive dependency chain Zhihang Wei
2025-11-18 14:47   ` 'Andreas Naumann' via isar-users [this message]

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=52158cd5-e4de-4a3c-8a87-eccf75a997e4@emlix.com \
    --to=isar-users@googlegroups.com \
    --cc=anaumann@emlix.com \
    --cc=wzh@ilbers.de \
    /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