Re: [isar-cip-core 4/5] .reproducible-check-ci.yml: Add BBB target

From: Jan Kiszka <jan.kiszka@siemens.com>
To: Venkata.Pyla@toshiba-tsip.com, cip-dev@lists.cip-project.org
Cc: dinesh.kumar@toshiba-tsip.com, kazuhiro3.hayashi@toshiba.co.jp
Subject: Re: [isar-cip-core 4/5] .reproducible-check-ci.yml: Add BBB target
Date: Thu, 14 Sep 2023 11:22:55 +0530	[thread overview]
Message-ID: <4062dd3b-77c3-4ff5-a7ff-a195f35b9e12@siemens.com> (raw)
In-Reply-To: <OSYPR01MB5542F9FA4966AA0F34736826A4F0A@OSYPR01MB5542.jpnprd01.prod.outlook.com>

On 13.09.23 09:37, Venkata.Pyla@toshiba-tsip.com wrote:
> 
> 
>> -----Original Message-----
>> From: Jan Kiszka <jan.kiszka@siemens.com>
>> Sent: Tuesday, September 12, 2023 1:20 PM
>> To: pyla venkata(ＴＳＩＰ TMIEC ODG Porting) <Venkata.Pyla@toshiba-
>> tsip.com>; cip-dev@lists.cip-project.org
>> Cc: dinesh kumar(ＴＳＩＰ TMIEC ODG Porting) <dinesh.kumar@toshiba-
>> tsip.com>; hayashi kazuhiro(林 和宏 ＤＭＥ ○ＤＩＧ□ＭＰＳ○ＭＰ４)
>> <kazuhiro3.hayashi@toshiba.co.jp>
>> Subject: Re: [isar-cip-core 4/5] .reproducible-check-ci.yml: Add BBB target
>>
>> On 12.09.23 12:22, Venkata.Pyla@toshiba-tsip.com wrote:
>>>
>>>
>>>> -----Original Message-----
>>>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>>> Sent: Tuesday, September 12, 2023 8:39 AM
>>>> To: pyla venkata(ＴＳＩＰ TMIEC ODG Porting) <Venkata.Pyla@toshiba-
>>>> tsip.com>; cip-dev@lists.cip-project.org
>>>> Cc: dinesh kumar(ＴＳＩＰ TMIEC ODG Porting) <dinesh.kumar@toshiba-
>>>> tsip.com>; hayashi kazuhiro(林 和宏 ＤＭＥ ○ＤＩＧ□ＭＰＳ○ＭＰ４)
>>>> <kazuhiro3.hayashi@toshiba.co.jp>
>>>> Subject: Re: [isar-cip-core 4/5] .reproducible-check-ci.yml: Add BBB
>>>> target
>>>>
>>>> On 11.09.23 19:01, venkata.pyla@toshiba-tsip.com wrote:
>>>>> From: venkata pyla <venkata.pyla@toshiba-tsip.com>
>>>>>
>>>>
>>>> Which additional aspects of reproducibility does this target test?
>>>
>>> It will try to verify additionally beagle bone specific files like MLO, u-boot and
>> dtb files.
>>>
>>
>> OK, so this includes firmware generation, understood. Does it also include
>> something that is now checked twice by other targets? I.e. can this supersede
>> some other target?
> 
> No, the kernel is different because it uses different configs, rootfs contents also different as it installs additional packages like u-boot-script and u-boot-tools.
> So the bbb target image contents are not verified in previous targets.

So far, we are not looking for testing each artifact we could produce
for reproducibility, just like we do not check each configuration
combination a user can select. Instead, we are testing representative
combinations. So my question would be if the BBB can be sufficiently
representative for qemu-arm specifically.

Jan

-- 
Siemens AG, Technology
Linux Expert Center