13:03:45 <jki> #startmeeting CIP IRC weekly meeting
13:03:45 <collab-meetbot> Meeting started Thu Aug 29 13:03:45 2024 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:03:45 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:03:45 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting'
13:03:54 <jki> #topic AI review
13:04:00 <jki> - prepare blog entry on SLTS kernel state and challenges [Jan]
13:04:13 <jki> no update, except that I want to have something before the conf
13:04:17 <jki> - clarify role of linux-6.1.y-cip-rebase tag [iwamatsu-san]
13:04:45 <jki> iwamatsu__: is this resolved now?
13:06:06 <iwamatsu__> Yes. I have confirmed that this problem does not occur.
13:07:05 <jki> ok
13:07:19 <jki> and the tag has been removed?
13:07:29 <iwamatsu__> Yes.
13:07:33 <jki> perfect
13:07:39 <jki> then moving on...
13:07:40 <jki> 5
13:07:42 <jki> 4
13:07:44 <jki> 3
13:07:45 <jki> 2
13:07:47 <jki> 1
13:07:48 <jki> #topic Kernel maintenance updates
13:07:59 <pave1> I am reviewing 6.1.107 and AUTOSEL.
13:08:00 <uli> i'm preparing the next 4.4 release
13:08:03 <masami> This week reported 90 new CVEs and 1 updated CVEs.
13:08:30 <iwamatsu__> I am reviewing 6.1.107.
13:11:13 <jki> anything else?
13:11:26 <jki> 5
13:11:27 <jki> 4
13:11:29 <jki> 3
13:11:31 <jki> 2
13:11:33 <jki> 1
13:11:35 <jki> #topic Kernel release status
13:11:38 <jki> all green
13:11:51 <jki> anything to add?
13:12:10 <jki> 5
13:12:12 <jki> 4
13:12:14 <jki> 3
13:12:16 <jki> 2
13:12:17 <jki> 1
13:12:19 <jki> #topic Kernel testing
13:12:32 <patersonc> Hello!
13:12:52 <arisut> patersonc,  hello
13:12:59 <arisut> no updates from me
13:13:02 <patersonc> I'm here for once, although not much to report. I've been away for most of August tbh.
13:13:29 <patersonc> It looks like the CI infrastructure has been behaving (for a change)
13:13:39 <pave1> Umm.
13:13:42 <arisut> patersonc, wb
13:13:58 <pave1> I needd to press "retry" way too many times when 6.1.107-rc1 was out.
13:14:25 <patersonc> Ah. Was that relating to the dodgy qemu machine a couple of weeks back?
13:14:42 <pave1> Looked like network problems this time.
13:15:16 <jki> any specific machine/lab again?
13:15:33 <pave1> https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/1429493404
13:15:37 <pave1> You can have sample here.
13:15:43 <pave1> It is build time.
13:15:44 <patersonc> Thanks
13:16:09 <patersonc> So it's failing to clone from kernel.org
13:16:13 <pave1> I was ably to retry so no huge problem, but ... :-)
13:16:18 <patersonc> Not ideal
13:16:52 <pave1> Not ideal.
13:16:53 <jki> are we being throttled?
13:16:58 <patersonc> It looks like this issue occurred a lot yesterday
13:19:00 <patersonc> Not sure how to work out if we're being throttled or not
13:19:47 <pave1> We already clone kernel.org data to gitlab, then we run the tests.
13:19:57 <pave1> Would gitlab be more suitable source for the clones?
13:20:24 <patersonc> We don't clone linux-stable-rc in gitlab because the repo is larger than the limits GitLab allows us
13:20:30 <jki> I came from there with isar-cip-core (tarballs, though), and it was... not really
13:21:07 <pave1> patersonc: aha. Would it make sense to do clone somewhere near the test infrastructure?
13:21:13 <jki> but maybe use PREMIRROR?
13:21:24 <jki> if that fails, the normal one is used
13:21:49 <pave1> ...so we would only pull from kernel.org once, then do the local clones inside AWS?
13:21:50 <jki> and, yes, local caching/mirroring would also be nicer
13:22:16 <jki> are we doing shallow clones at least (does not help if there is no connection at all, though)
13:22:18 <jki> ?
13:22:36 <pave1> I don't remember ever having "git pull" failing, and I don't have particulary great connection here.
13:23:49 <patersonc> I believe it's a shallow clone
13:24:32 <patersonc> We could investigate setting up some sort of mirror in AWS I guess
13:25:29 <pave1> I guess it would make sense from "being good net citizen" standpoint, too.
13:26:33 <patersonc> yea
13:27:44 <jki> ok... anything else on testing?
13:28:21 <jki> 5
13:28:22 <jki> 4
13:28:24 <jki> 3
13:28:25 <jki> 2
13:28:27 <jki> 1
13:28:28 <jki> #topic AOB
13:29:23 <jki> curious: who all will be in Vienna now?
13:29:33 <uli> o/
13:29:41 <pave1> o/
13:29:49 <patersonc> o/
13:30:09 <iwamatsu__> o/
13:30:10 <patersonc> I heard there will be free cocktails :)
13:30:42 <jki> yeah, for some even parallelized :)
13:31:06 <jki> (RT reception is competing with CIP, tss, tss)
13:31:32 <jki> ok, seems we should also use Vienna for some live kernel WG meet-up
13:32:02 <jki> not only over cocktails ;)
13:32:24 <jki> maybe some joint lunch break again?
13:33:16 <pave1> I don't have exact place ATM, but yes, that would work.
13:33:58 <patersonc> Sounds good
13:34:04 <iwamatsu__> +1
13:34:21 <jki> I'll check the agenda again an propose some slot first of all
13:34:21 <uli> +1
13:34:25 <jki> perfect
13:34:32 <jki> anything else for today?
13:36:09 <jki> 5
13:36:11 <jki> 4
13:36:12 <jki> 3
13:36:13 <jki> 2
13:36:15 <jki> 1
13:36:15 <jki> #endmeeting