13:02:49 <pave1> #startmeeting CIP IRC weekly meeting
13:02:49 <collab-meetbot> Meeting started Thu Oct 17 13:02:49 2024 UTC and is due to finish in 60 minutes.  The chair is pave1. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:02:49 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:02:49 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting'
13:02:59 <pave1> #topic AI review
13:03:09 <pave1> -  prepare blog entry on SLTS kernel state and challenges [Jan]
13:03:13 <pave1> Jan is not here, so skip.
13:03:16 <pave1> Anything else?
13:03:17 <pave1> 5
13:03:18 <pave1> 4
13:03:20 <pave1> 3
13:03:21 <pave1> 2
13:03:22 <pave1> 1
13:03:31 <pave1> #topic Kernel maintenance updates
13:03:40 <uli> i'm reviewing 6.1.113
13:03:44 <masami> This week reported 1 new CVEs and 14 updated CVEs.
13:03:53 <pave1> I'm reviewing 6.1.113.
13:03:56 <iwamatsu__> I am reviewing 6.1.113
13:04:10 <pave1> 3
13:04:12 <pave1> 2
13:04:14 <pave1> 1
13:04:26 <pave1> #topic Kernel release status
13:04:37 <pave1> iwamatsu, can you run the script?
13:05:11 <iwamatsu__> OK
13:05:20 <pave1> 4.19-cip-rt is due to next week, otherwise -rt should be on track.
13:05:37 <iwamatsu__> Date the data is created: Thu Oct 17 12:55:37 PM UTC 2024
13:05:38 <iwamatsu__> linux-4.4.y-cip: interval 30 day
13:05:38 <iwamatsu__> latest version: v4.4.302-cip92
13:05:39 <iwamatsu__> latest version release date: Wed Oct  9 04:23:37 AM UTC 2024
13:05:39 <iwamatsu__> limit date: Fri Nov  8 04:23:37 AM UTC 2024Status: On track
13:05:40 <iwamatsu__> linux-4.4.y-cip-rt: interval 60 day
13:05:40 <iwamatsu__> latest version: v4.4.302-cip91-rt51
13:05:41 <iwamatsu__> latest version release date: Mon Sep 30 09:48:28 AM UTC 2024
13:05:41 <iwamatsu__> limit date: Fri Nov 29 09:48:28 AM UTC 2024Status: On track
13:05:42 <iwamatsu__> linux-4.19.y-cip: interval 30 day
13:05:42 <iwamatsu__> latest version: v4.19.322-cip113
13:05:43 <iwamatsu__> latest version release date: Tue Sep 24 09:32:37 AM UTC 2024
13:05:43 <iwamatsu__> limit date: Thu Oct 24 09:32:37 AM UTC 2024Status: On track
13:05:44 <iwamatsu__> linux-4.19.y-cip-rt: interval 60 day
13:05:44 <iwamatsu__> latest version: v4.19.322-cip113-rt38
13:05:45 <iwamatsu__> latest version release date: Tue Sep 24 10:34:04 AM UTC 2024
13:05:45 <iwamatsu__> limit date: Sat Nov 23 10:34:04 AM UTC 2024Status: On track
13:05:46 <iwamatsu__> linux-5.10.y-cip: interval 30 day
13:06:27 <pave1> Hmm. Paste did not work well.
13:06:33 <pave1> But I guess everything is on track?
13:06:57 <iwamatsu__> https://www.nigauri.org/~iwamatsu/trash/status.txt
13:07:07 <iwamatsu__> Yes, all green
13:07:31 <pave1> linux-5.10.y-cip: interval 30 day
13:07:31 <pave1> latest version: v5.10.226-cip53
13:07:31 <pave1> latest version release date: Wed Oct  9 10:54:23 PM UTC 2024
13:07:31 <pave1> limit date: Fri Nov  8 10:54:23 PM UTC 2024Status: On track
13:07:31 <pave1> linux-5.10.y-cip-rt: interval 60 day
13:07:32 <pave1> latest version: v5.10.224-cip52-rt22
13:07:32 <pave1> latest version release date: Sat Sep  7 01:56:36 PM UTC 2024
13:07:33 <pave1> limit date: Wed Nov  6 01:56:36 PM UTC 2024Status: On track
13:07:33 <pave1> linux-6.1.y-cip: interval 15 day
13:07:34 <pave1> latest version: v6.1.112-cip30
13:07:34 <pave1> latest version release date: Wed Oct 16 09:40:02 PM UTC 2024
13:07:35 <pave1> limit date: Thu Oct 31 09:40:02 PM UTC 2024Status: On track
13:07:47 <pave1> 3
13:07:48 <pave1> 2
13:07:49 <pave1> 1
13:08:00 <pave1> #topic Kernel testing
13:08:55 <patersonc> I had to reboot the LAVA master again as it wasn't running the latest version - so the labs all need to be rebooted again, which may take a day or so depending on timezones - sorry
13:09:05 <patersonc> This should fix the de0-nano-soc issue though
13:09:09 <patersonc> Sorry about that Pave1
13:09:23 <pave1> No problem, thanks for fixing this!
13:09:27 <arisut> kci-dev is currently working. it can currently rebuild failed jobs and check for results
13:09:38 <patersonc> Thanks for Iwamatsu-san for pointing out the issue
13:09:48 <patersonc> That's great, thank you arisut
13:10:00 <patersonc> arisut are you going to OSS-J in a couple of weeks?
13:10:08 <arisut> currently we are working on adding bisection
13:10:14 <arisut> patersonc, yes
13:10:49 <patersonc> Great - can we meet up and discuss various cip/kernelci things like kci-dev?
13:10:58 <arisut> sure
13:11:12 <patersonc> In related news, I've started to migrate the CIP trees into the new kernelCI system
13:11:29 <arisut> patersonc, thanks
13:11:36 <arisut> what is still missing ?
13:12:00 <patersonc> It'll just do a basic build for now. Need to work out the configs side of things and the testing side - so most of it :P
13:12:14 <arisut> ok
13:12:36 <pave1> I'd like a feature:
13:12:52 <pave1> Currently, to test a tree, I need to add .gitlab..yml file, first.
13:13:01 <pave1> Which ... is not nice when bisecting.
13:13:19 <patersonc> Hopefully with kci-dev you won't need to do that
13:13:25 <pave1> (Because I'm searching between two commits, and now I'm adding more commits, and ...)
13:13:33 <pave1> Ok. :-). Looking forward.
13:14:09 <arisut> https://kernelci.github.io/kci-dev/
13:14:13 <patersonc> In the mid-term I'm investigating moving completely to kernelci and stopping our current gitlab ci approach. How exactly that will look is yet to be worked out
13:14:36 <pave1> What timeline are we talking about?
13:14:40 <patersonc> The new KernelCI dashboard _should_ be much easier to use than the last one.
13:14:53 <patersonc> pave1: Maybe e/2024
13:15:05 <pave1> Ok, sounds good, thank you!
13:15:07 <pave1> Anything else?
13:15:08 <patersonc> I'd like to get it in place for when we have all these new kernels to self-maintain
13:15:19 <patersonc> We need more tests done, not just boot tests imho
13:15:30 <pave1> Yes, that would be nice.
13:15:37 <pave1> We are going to be very busy at start of 2025.
13:15:51 <patersonc> Yep
13:15:55 <patersonc> Fun fun :)
13:16:17 <patersonc> Get your estimates into Jan/the CIP board as they are planning the 2025 budget
13:16:39 <pave1> Anything else?
13:16:44 <pave1> 3
13:16:49 <pave1> 2
13:16:49 <pave1> 1
13:17:06 <pave1> #topic AOB
13:17:16 <patersonc> o/      I have an AOB
13:17:21 <pave1> Go ahead!
13:17:50 <patersonc> Can anyone remember why we have a separate cip-kernel-config repo for the configs, rather than just add them to the linux-cip tree?
13:18:14 <pave1> There's not really a good place in linux-cip.
13:18:42 <pave1> We want our users to clone the kernel trees, they'll not want configs...
13:19:36 <patersonc> Would they really destroy their trees that much? I guess it's a personal preference thing
13:19:55 <patersonc> Not a big issue, it just would be easier to make use of them then having them in separate repos
13:20:46 <patersonc> On a different topic - iwamatsu__: Do you happen to have a spare BBB board?
13:21:04 <pave1> Its kind of tradition that configs are not stored in kernel tree :-). It would also mean
13:21:21 <pave1> having the configs at different branches, and we have other data we need per config -- like
13:21:41 <pave1> list of files compiled for each config. It would be strange to store that in kernel tree directly.
13:21:57 <iwamatsu__> Also, I think that putting your own config in the kernel tree is contrary to the stable/CIP patch rule.
13:22:26 <patersonc> Fair doos :)
13:22:38 <iwamatsu__> patersonc: yes, I have.
13:23:21 <iwamatsu__> we need more BBB?
13:24:03 <patersonc> If you have one and it's not too much effort I'd welcome it your LAVA lab
13:24:12 <patersonc> Don't worry too much though
13:24:53 <iwamatsu__> OK, I will connect BBB to my LAVA lab for CIP.
13:25:13 <patersonc> Thank you
13:25:41 <pave1> Ok, anything else?
13:25:51 <pave1> 3
13:25:55 <pave1> 2
13:26:01 <pave1> 1
13:26:13 <pave1> #endmeeting