13:02:27 <jki> #startmeeting CIP IRC weekly meeting
13:02:27 <collab-meetbot`> Meeting started Thu May 15 13:02:27 2025 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:02:27 <collab-meetbot`> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:02:27 <collab-meetbot`> The meeting name has been set to 'cip_irc_weekly_meeting'
13:02:34 <jki> #topic AI review
13:02:41 <jki> nothing on my list
13:03:36 <jki> 5
13:03:38 <jki> 4
13:03:40 <jki> 3
13:03:41 <jki> 2
13:03:43 <jki> 1
13:03:45 <jki> #topic Kernel maintenance updates
13:03:56 <pave1> I'm reviewing 6.1.138 & .139.
13:03:58 <uli_> i pushed 4.4
13:04:24 <pave1> .139 contains workarounds for another Spectre-like problem, and they currently break the build in our 6.1 testing.
13:04:57 <iwamatsu__> I reviewed 6.1.136, and released 5.10.y-cip
13:05:22 <pave1> Oh -stable is not back porting them to 5.10 for now.
13:05:54 <jki> known-bugs? :)
13:06:21 <pave1> It will be "wait a bit, then investigate... and then KNOWN-BUGS".
13:06:47 <jki> and 6.1.139 has a build-bug then?
13:07:00 <jki> reported already?
13:07:16 <pave1> jki: No, we caught it in -rc1 testing, so we are now at -rc2 (different bug) and it is likely to be fixed.
13:07:26 <jki> ah, ok
13:10:05 <jki> anything to add?
13:10:37 <jki> 5
13:10:38 <jki> 4
13:10:40 <jki> 3
13:10:41 <jki> 2
13:10:43 <jki> 1
13:10:46 <jki> #topic Kernel release status
13:10:55 <jki> all on schedule
13:11:02 <patersonc> \o/
13:11:12 <jki> 6.12-cip status?
13:11:12 <pave1> Thanks Iwamatsu for 5.10-cip, -cip-rt is now being tested.
13:11:27 <iwamatsu__> :-)
13:13:25 <jki> so, where are we with 6.12?
13:13:54 <iwamatsu__> I dont think there's a blocker now.
13:14:37 <jki> then tag what we have? :)
13:15:10 <iwamatsu__> Who will release it?
13:15:35 <jki> iwamatsu__: wasn't that you?
13:16:26 <iwamatsu__> Ah, sorry . I did not understand that.
13:16:37 <iwamatsu__> I will prepare it.
13:19:59 <jki> ok, perfect
13:20:12 <jki> then let's move on
13:20:15 <jki> 5
13:20:17 <jki> 4
13:20:18 <jki> 3
13:20:21 <jki> 2
13:20:22 <jki> 1
13:20:24 <jki> #topic Kernel testing
13:20:50 <arisut> working on adding cip-kernel-confing to KernelCI https://github.com/kernelci/kernelci-pipeline/pull/1149
13:20:50 <patersonc> No updates from my end this week
13:21:15 <patersonc> Thanks arisut, I missed that
13:21:50 <arisut> we recently ported the legacy code of cip fragments to maestro
13:22:37 <arisut> and we are currently working on adding cip-kernel-configs and disable all the configurations that are not needed to us
13:24:07 <arisut> also currently cip kernel can be build on demand with kci-dev
13:24:17 <patersonc> That's great.
13:24:40 <patersonc> I saw that there were a couple of build errors for cip 5.10, but both for chromeos configs
13:25:03 <arisut> yes we need to disable chromeos configs on cip
13:25:24 <arisut> unfortunatly for doing that part of the code need to be rewrite afaik
13:25:25 <pave1> If there are failures on -cip that are not present on corresponding -stable, we may want to investigate.
13:25:39 <pave1> If there are failures on -stable, we may want -stable people to investigate :-).
13:25:55 <arisut> yes but chromeos are chromeos dependent configurations
13:26:14 <arisut> we actually want to test chromeos configurations ?
13:27:00 <pave1> Even random configs should build in ideal world.
13:27:01 <arisut> I don't mind both cases
13:27:25 <pave1> ...we don't need to spend too much time testing, but if we already have the failure.
13:28:04 <arisut> so we don't need to block chromeos config?
13:28:09 <pave1> It may be good time for me to familiarize with test environment :-).
13:28:13 <patersonc> I can see a kernelci build for v5.10.236, but not v5.10.237 for some reason
13:28:39 <arisut> the code i write is not yet in production
13:29:41 <arisut> we can look into that
13:30:44 <pave1> Maybe you can send pointer to failures to the mailing list, and I'll try to take a look?
13:34:23 <arisut> patersonc, is that from the dashboard?
13:34:50 <patersonc> yes
13:34:57 <arisut> v5.10.237 cip is here https://dashboard.kernelci.org/tree/f32dc72d4e2a5cadfdfca58f84404d51cae038a0?ti%7Cc=v5.10.237-cip60&ti%7Cch=f32dc72d4e2a5cadfdfca58f84404d51cae038a0&ti%7Cgb=linux-5.10.y-cip&ti%7Cgu=https%3A%2F%2Fgit.kernel.org%2Fpub%2Fscm%2Flinux%2Fkernel%2Fgit%2Fcip%2Flinux-cip.git&ti%7Ct=cip
13:35:06 <arisut> cip60
13:35:21 <patersonc> Yes. But the linux-stable build for 5.10.237 isn't as far as I can see
13:35:30 <arisut> I see
13:36:55 <patersonc> I've asked on Discord
13:37:04 <iwamatsu__> https://dashboard.kernelci.org/tree/f32dc72d4e2a5cadfdfca58f84404d51cae038a0?df%7Cbs%7CFAIL=true&df%7Cc%7Cdefconfig%2Barm64-chromebook%2BCONFIG_CPU_BIG_ENDIAN%3Dy%2Bdebug%2Bkselftest%2Btinyconfig=true&ti%7Cc=v5.10.237-cip60&ti%7Cch=f32dc72d4e2a5cadfdfca58f84404d51cae038a0&ti%7Cgb=linux-5.10.y-cip&ti%7Cgu=https%3A%2F%2Fgit.kernel.org%2Fpub%2Fscm%2Fl
13:37:04 <iwamatsu__> inux%2Fkernel%2Fgit%2Fcip%2Flinux-cip.git&ti%7Ct=cip
13:38:27 <iwamatsu__> ihere appears to be a problem with the CIP.
13:40:01 <patersonc> Maybe we should be testing more configs then :P
13:40:25 <patersonc> More info here: https://dashboard.kernelci.org/issue/maestro%3Abad69ae5a6031018d1b7534daa1623f5b6bc4cef?iv=1
13:40:56 <jki> sorry, I'm distracted right now - let me know when you are done :)
13:41:52 <iwamatsu__> OK, I will take a look, too.
13:42:03 <patersonc> Thanks
13:42:03 <pave1> I guess we should take this to the mailing list.
13:42:37 <pave1> irqreturn_t problem seems like a missing include; trying CONFIG_BIG_ENDIAN is .. interesting but it should not be hard to fix.
13:44:42 <jki> anything to add for testing?
13:46:04 <jki> 5
13:46:06 <jki> 4
13:46:08 <jki> 3
13:46:09 <jki> 2
13:46:11 <jki> 1
13:46:12 <jki> #topic AOB
13:46:24 <uli_> i'll be absent next week
13:48:05 <jki> ok - anything else?
13:48:39 <jki> 5
13:48:42 <jki> 4
13:48:44 <jki> 3
13:48:46 <jki> 2
13:48:48 <jki> 1
13:48:49 <jki> #endmeeting