13:02:35 <jki> #startmeeting CIP IRC weekly meeting
13:02:35 <collab-meetbot`> Meeting started Thu Nov  2 13:02:35 2023 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:02:35 <collab-meetbot`> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:02:35 <collab-meetbot`> The meeting name has been set to 'cip_irc_weekly_meeting'
13:02:41 <jki> #topic AI review
13:02:48 <jki> still none recorded
13:02:59 <jki> anything to add?
13:03:05 <jki> 5
13:03:07 <jki> 4
13:03:08 <jki> 3
13:03:10 <jki> 2
13:03:11 <jki> 1
13:03:13 <jki> #topic Kernel maintenance updates
13:03:16 <pave1> Hi!
13:03:51 <pave1> Reviewing 6.1.61.
13:03:53 <uli_> i'm preparing 4.4 and reviewing 6.1.60
13:03:55 <masami> This week reported 2 new CVEs and 3 updated CVEs.
13:04:46 <iwamatsu> I reviewed 6.1.60, and reviewing 6.1.61.
13:05:13 <pave1> I looked at the CVEs. There's a scary one, but it should be virtualization-only, and only affects "Secure Encrypted Virtualizations", so likely we can wait for stable to handle this.
13:07:22 <jki> anyhing else?
13:07:40 <jki> 5
13:07:42 <jki> 4
13:07:43 <jki> 3
13:07:45 <jki> 2
13:07:47 <jki> 1
13:07:49 <jki> #topic Kernel release status
13:07:55 <jki> - 4.4
13:08:02 <uli_> on track, will post request for reviews soon
13:08:04 <pave1> -rt is up-to-date.
13:08:11 <jki> - 4.19
13:08:22 <pave1> -rt is due next month
13:08:39 <iwamatsu> on track, I am preparing release this week.
13:09:33 <jki> - 5.10
13:10:13 <pave1> -rt is due in 14 days
13:10:16 <iwamatsu> on track I will release this week too.
13:10:23 <jki> - 6.1
13:10:26 <pave1> iwamatsu:
13:10:35 <pave1> you may want to wait with 5.10 release.
13:10:50 <pave1> 5.10.199 is buggy on renesas. FIx is known but maybe just wait for .10.200.
13:11:10 <iwamatsu> Aha, I forgot it. Thanks.
13:11:39 <pave1> 6.1-rt is due at end of month.
13:12:12 <jki> and regular one was just released as well
13:12:13 <iwamatsu> Pave1: thanks for release -cip tree.
13:12:13 <jki> good
13:12:31 <jki> yeah, good to see that we can rotate roles :)
13:12:32 <pave1> iwamatsu: You are welcome. I'm glad I tried the process.
13:13:20 <jki> then let's move on
13:13:25 <jki> #topic Kernel testing
13:13:42 <patersonc> Hello
13:14:08 <patersonc> Nothing that exciting to highlight this week from me
13:14:19 <patersonc> I looked into multi-boot jobs in LAVA a bit
13:14:31 <patersonc> Hopefully that'll be useful for swupdate
13:14:49 <jki> does that solve the issue of testing watchdog resets?
13:15:23 <patersonc> No - it would only work if LAVA initiates the reboot
13:15:30 <jki> that is the problem
13:15:37 <patersonc> ah okay
13:15:40 <jki> we can't set swupdate properly without watchdogs
13:15:52 <jki> s/set/test/
13:16:07 <patersonc> Maybe we can find a way
13:16:20 <jki> you can test a good share, but not the "funny" cases
13:16:57 <patersonc> LAVA will watch for specific strings, so if we tell a test case to watch for the first line of a reboot after watchdog timeout maybe it can do something, but then the LAVA scripts won't be running in Linux anymore so it won't be able to complete the test case. hmmm
13:17:30 <patersonc> It may be worth sending a mail to the lava mailing list to see if anyone there has any suggestions
13:17:30 <jki> exactly, there is a design problem with lava here
13:17:47 <jki> i thought that was discussed already, but I was not involved
13:18:03 <jki> will ping my colleagues on that
13:18:23 <patersonc> Thanks
13:20:16 <jki> another DE-Nano-SOC is running again in our lab
13:20:40 <jki> the IPC227E still had some issue on Tuesday, should follow soon
13:21:50 <patersonc> Thanks!
13:22:04 <jki> anything else regarding testing?
13:22:23 <patersonc> Not from me
13:23:08 <jki> 5
13:23:09 <jki> 4
13:23:11 <jki> 3
13:23:12 <jki> 2
13:23:14 <jki> 1
13:23:15 <jki> #topic AOB
13:23:34 <jki> everyone still happy with our time slot?
13:23:58 <HRafuse> Yes, it is fine with me.
13:24:14 <pave1> I would not mind hour earlier, but can do this.
13:24:29 <masami> Yes.
13:24:56 <iwamatsu> Either is fine.
13:26:21 <jki> well, if no one suggests to move, let's keep it (CET-anchored)
13:26:42 <jki> maybe Europe will give up on daylight saving, one day, when all other problems are solved ;)
13:26:49 <patersonc> We can only hope
13:26:58 <jki> anyone anything else?
13:26:59 <HRafuse> I am hoping
13:27:31 <jki> 5
13:27:32 <patersonc> Budget for 2024
13:27:32 <jki> 4
13:27:38 <jki> good point
13:27:56 <jki> was some update requested already from us?
13:28:04 <jki> ah, I missed the TSC...
13:28:09 <patersonc> I think in this weeks TSC, but I wasn't there :P
13:28:18 <jki> me neither
13:28:21 <jki> oops
13:28:33 <patersonc> I got asked to think about testing budget for next year
13:28:47 <patersonc> Presumably kernel team needs to do the same
13:28:54 <jki> right
13:29:07 <jki> are we expecting more work next year?
13:29:28 <jki> are we fine with the current situation? (I'm assuming that)
13:29:56 <pave1> When is 4.19 ending maintainance by kernel team?
13:30:07 <jki> end of 24
13:30:14 <pave1> Dec 2024.
13:30:24 <jki> exactly
13:30:39 <jki> 2026 will be the "fun" year
13:30:42 <pave1> So we'll get little more work at that point. I guess that means increase in 2025.
13:31:42 <jki> yep, plus one more kernel in 25, if all goes well
13:31:54 <pave1> Ok, so significant increase in 2025.
13:32:05 <patersonc> We really need to get our testing better by then...
13:32:19 <pave1> Yeah.
13:32:24 <HRafuse> What are the current issues with testing?
13:32:32 <pave1> Actually I believe we should somehow expanding 4.4 testing.
13:32:35 <patersonc> The person in charge is rubbish
13:32:45 <patersonc> pave1: agreed
13:32:52 <pave1> stable team was doing testing for us, and that no longer happens.
13:33:07 <HRafuse> ahh okay well I am not a team but will be willing to help
13:33:42 <jki> do we have a concrete list of todos?
13:33:55 <jki> would help contributors to get started
13:34:02 <pave1> For 4.4 I'd suggest at least compile testing all non-crazy architectures.
13:34:07 <jki> and would also help us to budget efforts
13:34:28 <jki> what's in KernelCI so far? nothing for 4.4?
13:34:34 <patersonc> jki: No. I need to carve out a day and get a backlog sorted
13:35:07 <patersonc> 4.4 is being tested by kernelci: https://linux.kernelci.org/job/cip/
13:35:36 <patersonc> CIP and -st versions
13:35:48 <patersonc> and -rt
13:35:50 <jki> so, what is missing then for 4.4?
13:36:35 <patersonc> For CIP's testing, we're not actually testing much, mainly boot testing. And for the kernelci testing noone is really monitoring the output and acting on failures (as far as I understand)
13:37:31 <jki> maybe we should have a week test report, just like the weekly CVE news ;)
13:38:16 <jki> yeah, someone reading, sorting tracking, possibly fixing - that would be a start
13:38:30 <pave1> I can do the fixing :-).
13:38:40 <patersonc> jkl: agreed
13:39:23 <jki> HRafuse: would you have some bandwidth - and an idea where to look at?
13:40:26 <HRafuse> Somewhat, I am looking through the testing and things now. I think a backlog might be more structured and reduce the time it takes to fix this issue.
13:41:23 <HRafuse> I can do the reading and sorting to start with.
13:41:39 <patersonc> Thank you HRafuse. And yes some tickets would certainly help! I'll try and get organised
13:41:51 <jki> cool!
13:42:12 <HRafuse> No worries patersonc.
13:43:10 <jki> ok - back to budget
13:43:28 <jki> then I will only ask Neal to request offers for the same amount of hours next year
13:43:38 <jki> then we have the kernel budget at least
13:43:42 <patersonc> Sure
13:45:12 <jki> anything else for today?
13:45:47 <jki> 5
13:45:49 <jki> 4
13:45:50 <jki> 3
13:45:52 <jki> 2
13:45:54 <jki> 1
13:45:55 <HRafuse> Just that I am quite excited to get things rolling. Looking forward to working on this project.
13:45:55 <jki> #endmeeting