12:00:38 <pave1> #startmeeting CIP IRC weekly meeting
12:00:38 <collab-meetbot> Meeting started Thu Oct  1 12:00:38 2026 UTC and is due to finish in 60 minutes.  The chair is pave1. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:00:38 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:00:38 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting'
12:00:40 <iwamatsu> hello
12:00:51 <pave1> #topic AI review
12:00:55 <pave1> None.
12:00:58 <pave1> 3
12:01:01 <pave1> 2
12:01:03 <pave1> 1
12:01:12 <pave1> #topic Kernel maintenance updates
12:01:20 <masami> This week reported 608 new CVEs and 4 updated CVEs.
12:01:23 <uli> no update from me this week
12:01:26 <pave1> I'm reviewing 6.12.111 and 4.4-st.
12:01:37 <iwamatsu> I reivewed 6.12.105.
12:02:04 <pave1> 3
12:02:07 <pave1> 2
12:02:09 <pave1> 1
12:02:16 <pave1> #topic Kernel release status
12:02:22 <pave1> Can someone run the script? :-)
12:02:37 <iwamatsu> Date the data is created: Wed Sep 30 09:00:01 PM UTC 2026
12:02:38 <iwamatsu> linux-4.4.y-cip: interval 30 day
12:02:39 <iwamatsu> latest version: v4.4.302-cip114
12:02:40 <iwamatsu> latest version release date: Wed Aug 19 08:54:45 AM UTC 2026
12:02:41 <iwamatsu> limit date: Fri Sep 18 08:54:45 AM UTC 2026
12:02:42 <iwamatsu> Status: late
12:02:43 <iwamatsu> linux-4.4.y-cip-rt: interval 60 day
12:02:44 <iwamatsu> latest version: v4.4.302-cip113-rt62
12:02:45 <iwamatsu> latest version release date: Thu Jul 30 09:07:13 AM UTC 2026
12:02:47 <iwamatsu> limit date: Mon Sep 28 09:07:13 AM UTC 2026
12:02:49 <iwamatsu> Status: late
12:02:50 <iwamatsu> linux-4.19.y-cip: interval 30 day
12:02:55 <iwamatsu> latest version: v4.19.325-cip136
12:02:56 <iwamatsu> latest version release date: Fri Sep 11 08:53:07 AM UTC 2026
12:02:59 <iwamatsu> limit date: Sun Oct 11 08:53:07 AM UTC 2026
12:03:00 <iwamatsu> Status: On track
12:03:02 <iwamatsu> linux-4.19.y-cip-rt: interval 60 day
12:03:04 <iwamatsu> latest version: v4.19.325-cip136-rt50
12:03:06 <iwamatsu> latest version release date: Wed Sep 16 09:32:17 PM UTC 2026
12:03:08 <iwamatsu> limit date: Sun Nov 15 09:32:17 PM UTC 2026
12:03:11 <iwamatsu> Status: On track
12:03:12 <iwamatsu> linux-5.10.y-cip: interval 30 day
12:03:14 <iwamatsu> latest version: v5.10.268-cip77
12:03:17 <iwamatsu> latest version release date: Fri Sep 11 06:54:50 AM UTC 2026
12:03:18 <iwamatsu> limit date: Sun Oct 11 06:54:50 AM UTC 2026
12:03:20 <iwamatsu> Status: On track
12:03:24 <iwamatsu> linux-5.10.y-cip-rt: interval 60 day
12:03:27 <iwamatsu> latest version: v5.10.268-cip77-rt34
12:03:28 <iwamatsu> latest version release date: Thu Sep 17 09:59:47 AM UTC 2026
12:03:31 <iwamatsu> limit date: Mon Nov 16 09:59:47 AM UTC 2026
12:03:32 <iwamatsu> Status: On track
12:03:34 <iwamatsu> linux-6.1.y-cip: interval 30 day
12:03:37 <iwamatsu> latest version: v6.1.187-cip60
12:03:38 <iwamatsu> latest version release date: Fri Sep 11 10:35:49 PM UTC 2026
12:03:40 <iwamatsu> limit date: Sun Oct 11 10:35:49 PM UTC 2026
12:03:42 <iwamatsu> Status: On track
12:03:44 <iwamatsu> linux-6.1.y-cip-rt: interval 60 day
12:03:46 <iwamatsu> latest version: v6.1.182-cip59-rt31
12:03:48 <iwamatsu> latest version release date: Wed Aug 19 06:16:01 PM UTC 2026
12:03:51 <iwamatsu> limit date: Sun Oct 18 06:16:01 PM UTC 2026
12:03:54 <iwamatsu> Status: On track
12:03:56 <iwamatsu> linux-6.12.y-cip: interval 15 day
12:03:59 <iwamatsu> latest version: v6.12.111-cip32
12:04:00 <iwamatsu> latest version release date: Mon Sep 28 09:54:38 PM UTC 2026
12:04:02 <iwamatsu> limit date: Tue Oct 13 09:54:38 PM UTC 2026
12:04:05 <iwamatsu> Status: On track
12:04:06 <iwamatsu> Please see; https://www.nigauri.org/~iwamatsu/cip-release-term.html
12:04:08 <iwamatsu> linux-4.4.y-cip-* are late.
12:04:11 <pave1> Thank you!
12:04:34 <pave1> Yep, 4.4-cip is being reviewed, so this should be ok.
12:04:49 <pave1> 3
12:04:50 <pave1> 2
12:04:51 <pave1> 1
12:04:52 <pave1> #topic Kernel testing
12:05:22 <patersonc> KernelCI had an update yesterday which should fix some things for us
12:05:48 <patersonc> Is there any code ready to be applied and pushed to our kernel repo on kernel.org?
12:06:00 <pave1> So I took a look at kernelci, https://dashboard.kernelci.org/tree?i=7&ts=cip
12:06:07 <pave1> Currently it does not look too useful.
12:06:16 <arisut> I wrote a example of the kci-dev Python library API usage https://github.com/aliceinwire/kci_release_review https://aliceinwire.github.io/kci_release_review/
12:06:45 <arisut> a example plugin
12:07:41 <arisut> using github workflows for creating a website showing kernel versions comparisons
12:07:55 <pave1> patersonc: We have a series pending, so we should get commits to 5.10 in few days.
12:08:01 <patersonc> Thanks
12:08:32 <arisut> is doing also cip comparisons but some of cip kernel are outside of the 30 days storage window
12:09:25 <pave1> arisut: Ok, so can you provide some kind of easy output "5.10.268-cip77 tested, ok" or maybe you have some bugs that should be fixed?
12:10:36 <patersonc> pave1: The dashboard shows green for builds/boots/tests that passed, and red for failures. Each build/test run can be clicked on to get more details.
12:10:43 <patersonc> e.g. https://dashboard.kernelci.org/tree/cip/linux-5.10.y-cip-rt/3b7760683935418d3cb432901da8dea50e970a29?i=60
12:10:52 <patersonc> The kci-dev tool can also pull the same information
12:11:50 <pave1> patersonc: We can test kernels before release; we don't need new branches for that, something like https://dashboard.kernelci.org/tree?i=7&ts=cip would work, provided it provides useful information.
12:12:18 <patersonc> So what information is currently missing? We can feed this back
12:12:31 <pave1> patersonc: So what we currently have there is ... 6 build tests?
12:12:45 <pave1> patersonc: linux-5.10.y-cip-rt -- 6 build tests?
12:13:20 <pave1> patersonc: https://dashboard.kernelci.org/tree?i=7&ts=cip -- showing all the -cip branches would be good first step.
12:13:42 <patersonc> Yes 6. 2 per arch using the cip merged config, one set with and one without RT configs
12:14:23 <patersonc> Increase the interval beyond the last 7 days, e.g 30: https://dashboard.kernelci.org/tree?i=30&ts=cip
12:14:43 <patersonc> arisut: Didn't there use to be field to select the interval in the GUI?
12:15:08 <pave1> patersonc: And no runtime tests? I see stable-rc having 7000+ tests, 500 of them failing. Well, that's not too useful, either :-(.
12:15:33 <patersonc> Click the "tests" tab to see the tests
12:16:05 <patersonc> And the "boots" tab to see boots
12:16:51 <pave1> With 30 days, that looks more useful. Not too many tests there.
12:17:02 <pave1> So what do we do, simply look there before announcing a release?
12:17:36 <patersonc> Like the gitlab pipelines, we mainly cover boot tests atm ("boots"), and RT. I'm working on LTP and kselftest support.
12:19:14 <pave1> I see no tests at all for 4.19-cip-rt, for example, but as long as there's no red, I guess I'm okay.
12:19:33 <pave1> So what do we need to do? Take a look at the dashboard before announcing a release to see there's no red?
12:20:50 <patersonc> Yea something went wrong with that 4.19-rt pipeline
12:21:01 <patersonc> It makes sense to check the dashboard
12:21:30 <patersonc> Obviously it takes time to pick up the latest code and run the pipeline though. So depends on timing of the tag push vs when the release needs to be made
12:21:47 <pave1> It takes hour or a day?
12:22:02 <pave1> (And is there way to tell it is done?)
12:22:41 <patersonc> I'm not sure the dashboard shows it. Can probably work it out using the api
12:24:21 <pave1> Hmm :-)
12:24:22 <iwamatsu> Is there an email notification for that now?
12:24:28 <iwamatsu> api only?
12:25:13 <patersonc> There is, but I think the CIP mailing list ends up blocking it because all emails are blocked by default unless a sender is subscribed to the list
12:25:24 <patersonc> I'll investigate
12:25:36 <pave1> The webpage is strange, I wanted to bookmark version with i=30, and apparently that can't be done.
12:25:47 <pave1> Please don't spam the list. Or us.
12:26:14 <pave1> Perhaps the dashboard should show "testing done"? Or how is it supposed to be useful without that?
12:26:17 <iwamatsu> I see.
12:26:44 <patersonc> i=30 gets removed from the URL because it's the default
12:27:23 <pave1> patersonc: Except that it is not. Apparently i=7 is the default.
12:27:57 <pave1> i=60 version can be bookmarked, I guess that's good enough.
12:28:13 <pave1> Which points to https://dashboard.kernelci.org/tree/cip/linux-4.4.y-cip/c67c23ae791bfc624c927c9d9f02fe2c76a891b8?df%7Cts%7CFAIL=true&i=60&p=t failure. Should it be investigated?
12:28:34 <patersonc> oh very interesting. If you go to https://dashboard.kernelci.org/ the default is 7. If you go to https://dashboard.kernelci.org/tree it's 30
12:28:44 <patersonc> I'll report it :P
12:28:56 <pave1> Thanks!
12:29:48 <pave1> Anything more on testing?
12:30:40 <pave1> 3
12:30:41 <pave1> 2
12:30:42 <pave1> 1
12:30:49 <pave1> #topic AOB
12:31:28 <pave1> I got spam from hpe. If someone knows what is going on there or has a working contact, I'd like to know.
12:32:38 <pave1> Anything else?
12:32:41 <iwamatsu> I have received that email.;-)
12:33:08 <pave1> As far as I can see, they are not part of -cip.
12:33:28 <pave1> And sending email from noreply address, with no way to unsubscribe, is pretty rude (and illegal).
12:34:25 <pave1> Perhaps it will not happen again.
12:34:26 <pave1> 5
12:34:27 <pave1> 4
12:34:28 <pave1> 3
12:34:29 <pave1> 2
12:34:30 <pave1> 1
12:34:36 <pave1> #endmeeting