13:02:39 <jki> #startmeeting CIP IRC weekly meeting
13:02:39 <collab-meetbot> Meeting started Thu Jun 20 13:02:39 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:39 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:02:39 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting'
13:02:48 <jki> #topic AI review
13:02:51 <jki> - prepare blog entry on SLTS kernel state and challenges [Jan]
13:03:00 <jki> no news, still busy otherwise
13:03:11 <jki> no other recordings from last week as well
13:03:19 <jki> 5
13:03:21 <jki> 4
13:03:23 <jki> 3
13:03:25 <jki> 2
13:03:27 <jki> 1
13:03:29 <jki> #topic Kernel maintenance updates
13:03:37 <uli> i'm reviewing 6.1.93 and autosel patches
13:03:50 <pave1> I'm reviewing 6.1.94 and .95.
13:04:01 <iwamatsu__> I am reviewing  6.1.94.
13:04:12 <pave1> There's 5.10.220, which is very unusual. It contains 770 nfs related patches.
13:04:43 <pave1> Not sure what happened there... If someone cares about nfs, it would be good to test that.
13:05:07 <jki> huh
13:05:17 <jki> only 5.10 affected so far?
13:05:51 <jki> were there critical fixes that depended on a larger rewrite?
13:06:06 <pave1> Yep. Random checks show that most of those patches are in 6.1.
13:06:19 <pave1> jki: Yes, that would be possible explanation.
13:07:02 <jki> aren't we testing to some degree nfs anyway via lava?
13:07:23 <jki> but likely not systematically...
13:07:55 <patersonc> Yea, most LAVA testing uses NFS
13:08:08 <patersonc> "uses", not "tests"
13:08:30 <pave1> I guess -cip users are really using nfs for development, but not in production, still it makes me a bit nervous.
13:09:21 <jki> yeah, NFS in the field is rather unlikely
13:09:48 <jki> but not easy to exclude, given that it technically needed for testing
13:10:11 <pave1> I could imagine it in NMR machine, but if you say its unlikely -- good! :-)
13:10:49 <jki> maybe leave a note about this in the next 5.10 release announcement
13:11:04 <pave1> Sounds like good idea.
13:11:24 <jki> may already be good if 4.19 is not seeing this wave
13:13:02 <jki> good - anything else?
13:13:22 <jki> 5
13:13:24 <jki> 4
13:13:25 <jki> 3
13:13:27 <jki> 2
13:13:29 <jki> 1
13:13:31 <jki> #topic Kernel release status
13:13:43 <jki> just 6.1 was late according to the check
13:14:11 <iwamatsu__> I am preparing it.
13:14:20 <jki> good
13:14:33 <iwamatsu__> I am releasing it  tomorrow.
13:14:45 <jki> if no other blockers in sight...
13:14:52 <jki> 5
13:14:54 <jki> 4
13:14:55 <jki> 3
13:14:57 <jki> 2
13:14:58 <jki> 1
13:15:01 <jki> #topic Kernel testing
13:15:09 <patersonc> jki: I don't suppose you have any updates for the Siemens lab?
13:16:57 <jki> our colleagues got their new lab working, I heard, and that is now supposed to take over
13:18:58 <patersonc> Great
13:19:29 <patersonc> I've not done much for testing this week, so no updates from me really
13:20:15 <jki> we had some issues with the small gitlab ci runner, not sure if others were affected besides isar-cip-core
13:20:41 <patersonc> What kind of issues?
13:20:42 <jki> Michael was looking into it this morning, and we should have an updated runner soon/now
13:20:59 <jki> the runners died, gitlab compplained as well
13:21:26 <patersonc> oh
13:21:31 <jki> "There has been a runner system failure, please try again"
13:21:56 <patersonc> Just a one off? Or happening a lot?
13:22:52 <jki> a lot since yesterday afternoon
13:23:04 <jki> then AWS DNS issues as well
13:23:07 <jki> messy
13:25:17 <patersonc> okay
13:26:16 <jki> patersonc: onboarding request for our new lab sent
13:26:27 <patersonc> I've just seen it, thanks
13:26:38 <jki> will start with qemu, hw to follow
13:26:49 <patersonc> Is this instead of muc?
13:27:18 <jki> yep
13:27:23 <patersonc> Great
13:27:36 <jki> muc was relocated into connectivity issues
13:28:01 <jki> ok, anything else on testing?
13:29:42 <jki> 5
13:29:44 <jki> 4
13:29:46 <jki> 3
13:29:48 <jki> 2
13:29:49 <jki> 1
13:29:51 <jki> #topic AOB
13:30:02 <pave1> I'll be traveling next two weeks.
13:30:10 <jki> ok
13:30:43 <jki> any releases in that phase needed? will someone take over?
13:31:17 <pave1> I'll check, but I should have enough connectivity to do them.
13:31:54 <pave1> ...actually, nothing needed, good. Closest is 6.1rt at Jul 5th.
13:32:04 <jki> ok, perfect
13:32:21 <jki> anything else for today?
13:32:55 <jki> 5
13:32:57 <jki> 4
13:32:58 <jki> 3
13:33:00 <jki> 2
13:33:02 <jki> 1
13:33:04 <jki> #endmeeting