Re: [isar-cip-core][PATCH v2] .gitlab-ci.yml: Override default release with sid

On 23.07.26 12:47, Jan Kiszka wrote:
> On 23.07.26 07:09, [email protected] wrote:
>> From: Shivanand Kunijadar <[email protected]>
>>
>> By default, the release is set to trixie, pass release as sid to
>> override it for sid based test targets.
>>
>> Signed-off-by: Shivanand Kunijadar <[email protected]>
>> ---
>>  .gitlab-ci.yml | 3 +++
>>  1 file changed, 3 insertions(+)
>>
>> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
>> index 5a20ad6..b53def4 100644
>> --- a/.gitlab-ci.yml
>> +++ b/.gitlab-ci.yml
>> @@ -740,6 +740,7 @@ test:qemu-amd64-IEC-sid:
>>     - .test-cip-core-sid
>>    variables:
>>      target: qemu-amd64
>> +    release: sid
>>      test_function: IEC
>>      iec_test_timeout: 40
>>  
>> @@ -749,6 +750,7 @@ test:qemu-arm64-IEC-sid:
>>    needs: ["build:qemu-arm64-base-sid"]
>>    variables:
>>      target: qemu-arm64
>> +    release: sid
>>      test_function: IEC
>>      iec_test_timeout: 40
>>  
>> @@ -758,6 +760,7 @@ test:qemu-arm-IEC-sid:
>>    needs: ["build:qemu-arm-base-sid"]
>>    variables:
>>      target: qemu-arm
>> +    release: sid
>>      test_function: IEC
>>      iec_test_timeout: 40
>>  
> 
> Thanks, applied with a slightly adjusted subject ("Actually set release
> to sid for sid targets").
> 

But what is now the expected state of the pipeline? It's currently
failing in all tests:

https://gitlab.com/cip-project/cip-core/isar-cip-core/-/pipelines/2704797364

Is this due to changes in sid or due to still missing patches to the CI
infrastructure?

Please also have a look at the even more important inclusion of forky
soon. This is where we need to be ready for testing  as well. Could
become part of those weekly runs as well, at least until it goes into
stabilization in spring next year.

Jan

-- 
Siemens AG, Foundational Technologies
Linux Expert Center