Hi Michal,
> On Dec 8, 2023, at 17:19, Michal Orzel <[email protected]> wrote:
>
> Hi Henry,
>
> On 08/12/2023 06:46, Henry Wang wrote:
>>
>>
>> Add a job in the build stage to export the TF-A, U-Boot and the
>> device tree for the FVP platform from the test artifact container.
>>
>> Add a FVP smoke test job in the test stage to do the same test as
>> the `qemu-smoke-dom0-arm64-gcc` job.
>>
>> Signed-off-by: Henry Wang <[email protected]>
>> Reviewed-by: Stefano Stabellini <[email protected]>
> Reviewed-by: Michal Orzel <[email protected]>
Thanks.
>
> with a remark...
>
>> +fvp-smoke-dom0-arm64-gcc-debug:
>> + extends: .fvp-arm64
>> + script:
>> + - ./automation/scripts/fvp-base-smoke-dom0-arm64.sh 2>&1 | tee
>> ${LOGFILE}
>> + needs:
>> + - *arm64-test-needs
> This would imply the need for qemu-system-aarch64-6.0.0-arm64-export which
> you don't need.
> I think you could do:
>
> .fvp-arm64-test-needs: &fvp-arm64-test-needs
> - alpine-3.18-arm64-rootfs-export
> - kernel-5.19-arm64-export
> - armfvp-uboot-tfa-2023.10-2.9.0-arm64-export
>
> and then reference this in your job. This will be reused by other FVP tests
> in the future.
Sounds good, will do in v3. Thanks!
Kind regards,
Henry
>
> ~Michal
