13:02:00 #startmeeting CIP IRC weekly meeting 13:02:00 Meeting started Thu Jul 18 13:02:00 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:00 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:02:00 The meeting name has been set to 'cip_irc_weekly_meeting' 13:02:00 hi 13:02:07 #topic AI review 13:02:13 - prepare blog entry on SLTS kernel state and challenges [Jan] 13:02:32 no news, need to see after my vacation if there is a chance to resume 13:02:42 other AI not recorded 13:02:50 5 13:02:52 4 13:02:54 3 13:02:55 2 13:02:57 1 13:02:59 #topic Kernel maintenance updates 13:03:16 This week reported 102 new CVEs and 1 updated CVEs. 13:03:19 Reviewing 6.1.97, 98, 100. 13:03:28 i reviewed autosel patches 13:03:43 I reviewed  6.1.97, 98, 99. 13:05:01 other topics? 13:05:43 5 13:05:45 4 13:05:47 3 13:05:49 2 13:05:51 1 13:05:54 #topic Kernel release status 13:06:04 all were green 13:06:26 4.19-rt is due soon, so I'll be looking for suitable match. 13:06:50 really? 13:07:02 latest version release date: Fri Jul 12 03:18:17 PM UTC 2024 13:07:11 said the script 13:07:45 Oops, sorry, will need to update my dates :-). 13:08:04 did you release earlier than planned? 13:08:18 A bit, yes. I seen a good match and it was quiet period. 13:08:42 ok, that's what our script can't handle 13:09:26 10 days early in two months cadence should be acceptable. 13:09:33 ack 13:09:38 We don't need a script to guard for that :-). 13:10:09 ok, let's move on 13:10:13 5 13:10:15 4 13:10:16 3 13:10:18 2 13:10:20 1 13:10:28 #topic Kernel testing 13:11:05 working on the new KernelCI development tool but no updates from me 13:11:23 I'm seeing ocassional random failures on qemu target. I just hit retry, but one day it would 13:11:26 be worth investigating. 13:11:51 that's gitlab or KernelCI qemu ? i suppose gitlab 13:11:56 gitlab. 13:12:37 so that's patersonc territory 13:12:38 If you are willing to look into that, I'll not hit retry next time it happens, and we can have a look? 13:12:41 Aha, ok. 13:13:42 but these are still lava "devices", no? 13:13:58 yes qemu lava devices i suppose 13:14:28 so probably is failing also kernelci requests 13:14:32 https://lava.ciplatform.org/scheduler/device_type/qemu 13:14:42 we have many qemu instances, maybe one is bad 13:14:55 that's strange 13:15:05 maybe ours... :D 13:15:16 https://lava.ciplatform.org/scheduler/device/qemu-cip-siemens-muc 13:15:22 I see 13:15:32 we could take it into maintenance for now 13:15:43 nice to know, thanks pave1 13:16:02 This is how it usually looks: 13:16:04 https://lava.ciplatform.org/scheduler/job/1168713 13:16:12 1.028113] uart-pl011 9000000.pl011: no DMA platform data 13:16:13 login-action timed out after 119 seconds 13:16:58 always like that? 13:17:22 I believe so. 13:17:34 I don't always look at logs, but from memory, that's what it does. 13:18:52 ok, I don't have access, will ask Quirin to check or take the device offline 13:19:13 Thank you! 13:19:53 anything else on testing? 13:20:38 5 13:20:40 4 13:20:42 3 13:20:43 2 13:20:45 1 13:20:48 #topic AOB 13:21:00 I have two topics 13:21:16 first: anyone alreay looked at https://gitlab.com/cip-playground/kernel-cve-triage? 13:22:57 would be great to get feedback and clarify if we should continue this way 13:23:50 OK, I will check it. 13:24:15 TIA 13:24:37 the other topic: I'm out for the next two weeks 13:25:46 who can take over? 13:25:57 I'm away from Aug 3 to Aug 10, probably with internet access. 13:26:10 I can take over. 13:26:26 perfect - thanks! 13:26:46 other topics for today? 13:27:40 5 13:27:41 4 13:27:43 3 13:27:45 2 13:27:46 1 13:27:49 #endmeeting