13:02:01 <jki> #startmeeting CIP IRC weekly meeting
13:02:01 <collab-meetbot> Meeting started Thu Feb  8 13:02:01 2024 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:02:01 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:02:01 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting'
13:02:13 <jki> #topic AI review
13:02:18 <jki> - prepare blog entry on SLTS kernel state and challenges [Jan]
13:02:24 <jki> still a todo...
13:02:24 <pave1> hi
13:02:48 <jki> didn't record anything new last week, so...
13:02:54 <jki> 3
13:02:56 <jki> 2
13:02:58 <jki> 1
13:03:00 <jki> #topic Kernel maintenance updates
13:03:08 <uli> i'm reviewing 6.1.75
13:03:13 <masami> This week reported 10 new CVEs and 3 updated CVEs.
13:03:37 <pave1> I'm reviewing 6.1.77
13:04:08 <iwamatsu> I reviewed 6.1.76, and reviewing 6.1.77.
13:04:13 <pave1> Ton of patches applied from the list, but our to-do should now be empty
13:06:17 <jki> pavel: what went wrong with the -rt release upload?
13:06:25 <jki> any recommendations, also to others, to avoid that in the future?
13:09:47 <pave1> be careful with the scripts...
13:10:07 <pave1> I had wrong tree checked out.
13:10:36 <jki> is that script yours or used by others as well?
13:10:43 <pave1> Bad thing is that undoin mistake is not easy.
13:10:59 <pave1> Script of mine.
13:11:38 <jki> yeah, that's the major issue, generally with prominent upload targets
13:11:41 <jki> ok
13:11:49 <jki> anything else on maintenance?
13:12:03 <jki> 5
13:12:05 <jki> 4
13:12:07 <jki> 3
13:12:08 <jki> 2
13:12:11 <jki> 1
13:12:14 <jki> #topic Kernel release status
13:12:25 <iwamatsu> Date the data is created: Thu 08 Feb 2024 01:09:45 PM UTC
13:12:27 <iwamatsu> linux-4.4.y-cip: interval 30 day
13:12:29 <iwamatsu> latest version release date: Fri 02 Feb 2024 03:27:15 AM UTC
13:12:31 <iwamatsu> limit date: Sun 03 Mar 2024 03:27:15 AM UTC
13:12:33 <iwamatsu> Status: On track
13:12:35 <iwamatsu> linux-4.4.y-cip-rt: interval 60 day
13:12:37 <iwamatsu> latest version release date: Wed 03 Jan 2024 10:54:06 AM UTC
13:12:39 <iwamatsu> limit date: Sun 03 Mar 2024 10:54:06 AM UTC
13:12:41 <iwamatsu> Status: On track
13:12:43 <iwamatsu> linux-4.19.y-cip: interval 30 day
13:12:45 <iwamatsu> latest version release date: Thu 11 Jan 2024 03:28:42 PM UTC
13:12:47 <iwamatsu> limit date: Sat 10 Feb 2024 03:28:42 PM UTC
13:12:49 <iwamatsu> Status: On track
13:12:51 <iwamatsu> linux-4.19.y-cip-rt: interval 60 day
13:12:53 <iwamatsu> latest version release date: Thu 28 Dec 2023 05:34:49 PM UTC
13:12:55 <iwamatsu> limit date: Mon 26 Feb 2024 05:34:49 PM UTC
13:12:57 <iwamatsu> Status: On track
13:12:59 <iwamatsu> linux-5.10.y-cip: interval 30 day
13:13:01 <iwamatsu> latest version release date: Mon 05 Feb 2024 01:04:01 PM UTC
13:13:03 <iwamatsu> limit date: Wed 06 Mar 2024 01:04:01 PM UTC
13:13:05 <iwamatsu> Status: On track
13:13:07 <iwamatsu> linux-5.10.y-cip-rt: interval 60 day
13:13:09 <iwamatsu> latest version release date: Mon 05 Feb 2024 05:21:45 PM UTC
13:13:11 <iwamatsu> limit date: Fri 05 Apr 2024 05:21:45 PM UTC
13:13:13 <iwamatsu> Status: On track
13:13:15 <iwamatsu> linux-6.1.y-cip: interval 15 day
13:13:17 <iwamatsu> latest version release date: Fri 02 Feb 2024 07:12:46 AM UTC
13:13:19 <iwamatsu> limit date: Sat 17 Feb 2024 07:12:46 AM UTC
13:13:21 <iwamatsu> Status: On track
13:13:23 <iwamatsu> linux-6.1.y-cip-rt: interval 30 day
13:13:25 <iwamatsu> latest version release date: Sat 03 Feb 2024 08:06:26 PM UTC
13:13:27 <iwamatsu> limit date: Mon 04 Mar 2024 08:06:26 PM UTC
13:13:29 <iwamatsu> Status: On track
13:13:31 <iwamatsu> all on track.
13:13:44 <jki> I had it ready as well this time :)
13:13:47 <jki> thanks!
13:14:10 <jki> moving on then...
13:14:12 <jki> 3
13:14:14 <jki> 2
13:14:16 <jki> 1
13:14:18 <jki> #topic Kernel testing
13:14:59 <jki> chris is missing - anyone else?
13:16:12 <arisut> I'm going on investigating the kernelci core api
13:16:19 <arisut> but not su much yet
13:17:28 <pave1> Could we lessen number of testing mails on cip-dev?
13:17:43 <pave1> [cip-dev] LAVA notification for Test Job 1089996 qemu arm64 secure boot testing
13:17:46 <pave1> is not really very useful.
13:18:08 <pave1> Neither is [cip-dev] cip/linux-4.19.y-cip baseline-nfs: 34 runs, 3 regressions (v4.19.304-c
13:19:35 <uli> i have missed important stuff in the past because it was drowned out by autogenerated mails...
13:20:08 <jki> given that we have the summary report on releases yet, turn these off?
13:20:24 <pave1> I'd prefer that.
13:20:33 <jki> or someone need to generate (manual work) digests of real regressions
13:21:58 <uli> isn't that something chris is doing already?
13:22:34 <jki> then the auto-generated ones are useless as broadcast, indeed
13:23:05 <iwamatsu> For example: https://lore.kernel.org/cip-dev/TYWPR01MB118627FE1C9D6E1D42F3F9AA3B7452@TYWPR01MB11862.jpnprd01.prod.outlook.com/ ?
13:23:37 <uli> exactly
13:23:44 <pave1> Yep, I believe we should simply turn off the broadcast.
13:24:07 <jki> who can do that?
13:24:09 <arisut> probably we should get patersonc opinion on that
13:24:22 <jki> ack
13:24:31 <jki> mail to the list, CC'ing him?
13:24:40 <pave1> Topic on next meeting?
13:24:51 <jki> or that, if it is not urgent
13:25:09 <pave1> We survived like this for year, we can do one more week :-).
13:25:55 <jki> ok - other testing topics?
13:26:32 <jki> 5
13:26:34 <jki> 4
13:26:35 <jki> 3
13:26:37 <jki> 2
13:26:38 <jki> 1
13:26:41 <jki> #topic AOB
13:28:03 <jki> nothing else for today?
13:28:10 <jki> 5
13:28:12 <jki> 4
13:28:14 <jki> 3
13:28:16 <jki> 2
13:28:17 <jki> 1
13:28:19 <jki> #endmeeting