Re: [ANNOUNCE] 4.4.302-cip71-rt41
Chris Paterson
Hello Pavel,
Thank you for the release!
For example [0] , RT build configurations will only run if the branch name contains "linux-4.4.y-cip-rt".
This is why Iwamatsu-san got a different result [1] on his "ci/Iwamatsu/linux-4.4.y-cip-rt-rebase" branch.
It obviously leads to lots of "ci" branches [2], but it does make tracking build/test history for the different kernel versions easier.
Would it be possible for you to switch to a similar approach?
[0] https://gitlab.com/cip-project/cip-testing/linux-cip-pipelines/-/blob/master/trees/linux-4.4.y-cip.yml#L130
[1] https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/710140750
[2] https://gitlab.com/cip-project/cip-kernel/linux-cip/-/branches?state=all&sort=updated_desc&search=ci%2F
Both will get built if a push is made to a branch name containing "linux-4.4.y-cip-rt".
RT specific tests also get run on renesas_shmobile-rt_defconfig.
[3] https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/-/blob/master/4.4.y-cip-rt/arm/renesas_shmobile-rt_defconfig
[4] https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/-/blob/master/4.4.y-cip-rt/x86/siemens_i386-rt.config
Let me know if there's anything else I can help with.
Kind regards, Chris
Thank you for the release!
From: Pavel Machek <pavel@...>The CI pipelines look at the branch name to determine what builds/tests get run.
Sent: 01 December 2022 08:59
Hi!Thanks for release work!/jobs/3405080634#L4519
BTW, rt_x86_siemens_i386-rt.config is the build error.
https://gitlab.com/cip-project/cip-kernel/linux-cip/-I'm posting a patch to cip-dev that fixes this. Please check that.warning
[RESEND][PATCH for 4.4.y] extcon: adc-jack: Fix incompatible pointer type
Yes, will take a look, thanks for noticing.
I tried to run tests before release, and they succeeded
https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/709907648
:
1) Any idea why my testing differs / how I can properly run the tests
for the -rt branch?
For example [0] , RT build configurations will only run if the branch name contains "linux-4.4.y-cip-rt".
This is why Iwamatsu-san got a different result [1] on his "ci/Iwamatsu/linux-4.4.y-cip-rt-rebase" branch.
It obviously leads to lots of "ci" branches [2], but it does make tracking build/test history for the different kernel versions easier.
Would it be possible for you to switch to a similar approach?
[0] https://gitlab.com/cip-project/cip-testing/linux-cip-pipelines/-/blob/master/trees/linux-4.4.y-cip.yml#L130
[1] https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/710140750
[2] https://gitlab.com/cip-project/cip-kernel/linux-cip/-/branches?state=all&sort=updated_desc&search=ci%2F
We currently have two -rt specific configs for 4.4-cip, renesas_shmobile-rt_defconfig [3] and siemens_i386-rt.config [4].
2) Should we have config similar to rt_x86_siemens_i386-rt.config for
4.4-cip, too? The -rt bits will not apply, but we should be able to
test the rest.
Both will get built if a push is made to a branch name containing "linux-4.4.y-cip-rt".
RT specific tests also get run on renesas_shmobile-rt_defconfig.
[3] https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/-/blob/master/4.4.y-cip-rt/arm/renesas_shmobile-rt_defconfig
[4] https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/-/blob/master/4.4.y-cip-rt/x86/siemens_i386-rt.config
Let me know if there's anything else I can help with.
Kind regards, Chris
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany