Thursday, 2026-10-01

« Wednesday, 2026-09-30 Index Friday, 2026-10-02 »
*** prabhakalad <prabhakalad!~prabhakar@97e54365.skybroadband.com> has quit IRC (Ping timeout: 255 seconds)02:40
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip05:53
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 264 seconds)05:57
*** prabhakalad <prabhakalad!~prabhakar@97e54365.skybroadband.com> has joined #cip10:14
*** masami <masami!~masami@FL1-111-168-44-134.tky.mesh.ad.jp> has joined #cip12:00
pave1Hi!12:00
ulihello12:00
masamihello12:00
pave1#startmeeting CIP IRC weekly meeting12:00
collab-meetbotMeeting 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
collab-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:00
collab-meetbotThe meeting name has been set to 'cip_irc_weekly_meeting'12:00
*** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)"12:00
iwamatsuhello12:00
pave1#topic AI review12:00
*** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"12:00
pave1None.12:00
pave1312:00
pave1212:01
pave1112:01
pave1#topic Kernel maintenance updates12:01
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"12:01
masamiThis week reported 608 new CVEs and 4 updated CVEs.12:01
ulino update from me this week12:01
pave1I'm reviewing 6.12.111 and 4.4-st.12:01
iwamatsuI reivewed 6.12.105.12:01
pave1312:02
pave1212:02
pave1112:02
pave1#topic Kernel release status12:02
*** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"12:02
pave1Can someone run the script? :-)12:02
iwamatsuDate the data is created: Wed Sep 30 09:00:01 PM UTC 202612:02
iwamatsulinux-4.4.y-cip: interval 30 day12:02
iwamatsu  latest version: v4.4.302-cip11412:02
iwamatsu  latest version release date: Wed Aug 19 08:54:45 AM UTC 202612:02
iwamatsu  limit date: Fri Sep 18 08:54:45 AM UTC 202612:02
iwamatsu  Status: late12:02
iwamatsulinux-4.4.y-cip-rt: interval 60 day12:02
iwamatsu  latest version: v4.4.302-cip113-rt6212:02
iwamatsu  latest version release date: Thu Jul 30 09:07:13 AM UTC 202612:02
iwamatsu  limit date: Mon Sep 28 09:07:13 AM UTC 202612:02
iwamatsu  Status: late12:02
iwamatsulinux-4.19.y-cip: interval 30 day12:02
iwamatsu  latest version: v4.19.325-cip13612:02
iwamatsu  latest version release date: Fri Sep 11 08:53:07 AM UTC 202612:02
iwamatsu  limit date: Sun Oct 11 08:53:07 AM UTC 202612:02
iwamatsu  Status: On track12:03
iwamatsulinux-4.19.y-cip-rt: interval 60 day12:03
iwamatsu  latest version: v4.19.325-cip136-rt5012:03
iwamatsu  latest version release date: Wed Sep 16 09:32:17 PM UTC 202612:03
iwamatsu  limit date: Sun Nov 15 09:32:17 PM UTC 202612:03
iwamatsu  Status: On track12:03
iwamatsulinux-5.10.y-cip: interval 30 day12:03
iwamatsu  latest version: v5.10.268-cip7712:03
iwamatsu  latest version release date: Fri Sep 11 06:54:50 AM UTC 202612:03
iwamatsu  limit date: Sun Oct 11 06:54:50 AM UTC 202612:03
iwamatsu  Status: On track12:03
iwamatsulinux-5.10.y-cip-rt: interval 60 day12:03
iwamatsu  latest version: v5.10.268-cip77-rt3412:03
iwamatsu  latest version release date: Thu Sep 17 09:59:47 AM UTC 202612:03
iwamatsu  limit date: Mon Nov 16 09:59:47 AM UTC 202612:03
iwamatsu  Status: On track12:03
iwamatsulinux-6.1.y-cip: interval 30 day12:03
iwamatsu  latest version: v6.1.187-cip6012:03
iwamatsu  latest version release date: Fri Sep 11 10:35:49 PM UTC 202612:03
iwamatsu  limit date: Sun Oct 11 10:35:49 PM UTC 202612:03
iwamatsu  Status: On track12:03
iwamatsulinux-6.1.y-cip-rt: interval 60 day12:03
iwamatsu  latest version: v6.1.182-cip59-rt3112:03
iwamatsu  latest version release date: Wed Aug 19 06:16:01 PM UTC 202612:03
iwamatsu  limit date: Sun Oct 18 06:16:01 PM UTC 202612:03
iwamatsu  Status: On track12:03
iwamatsulinux-6.12.y-cip: interval 15 day12:03
iwamatsu  latest version: v6.12.111-cip3212:03
iwamatsu  latest version release date: Mon Sep 28 09:54:38 PM UTC 202612:04
iwamatsu  limit date: Tue Oct 13 09:54:38 PM UTC 202612:04
iwamatsu  Status: On track12:04
iwamatsuPlease see; https://www.nigauri.org/~iwamatsu/cip-release-term.html12:04
iwamatsulinux-4.4.y-cip-* are late.12:04
pave1Thank you!12:04
pave1Yep, 4.4-cip is being reviewed, so this should be ok.12:04
pave1312:04
pave1212:04
pave1112:04
pave1#topic Kernel testing12:04
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"12:04
patersoncKernelCI had an update yesterday which should fix some things for us12:05
patersoncIs there any code ready to be applied and pushed to our kernel repo on kernel.org?12:05
pave1So I took a look at kernelci, https://dashboard.kernelci.org/tree?i=7&ts=cip12:06
pave1Currently it does not look too useful.12:06
arisutI 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
arisuta example plugin12:06
arisutusing github workflows for creating a website showing kernel versions comparisons12:07
pave1patersonc: We have a series pending, so we should get commits to 5.10 in few days.12:07
patersoncThanks12:08
arisutis doing also cip comparisons but some of cip kernel are outside of the 30 days storage window12:08
pave1arisut: 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:09
patersoncpave1: 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
patersonce.g. https://dashboard.kernelci.org/tree/cip/linux-5.10.y-cip-rt/3b7760683935418d3cb432901da8dea50e970a29?i=6012:10
patersoncThe kci-dev tool can also pull the same information12:10
pave1patersonc: 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:11
patersoncSo what information is currently missing? We can feed this back12:12
pave1patersonc: So what we currently have there is ... 6 build tests?12:12
pave1patersonc: linux-5.10.y-cip-rt -- 6 build tests?12:12
pave1patersonc: https://dashboard.kernelci.org/tree?i=7&ts=cip -- showing all the -cip branches would be good first step.12:13
patersoncYes 6. 2 per arch using the cip merged config, one set with and one without RT configs12:13
patersoncIncrease the interval beyond the last 7 days, e.g 30: https://dashboard.kernelci.org/tree?i=30&ts=cip12:14
patersoncarisut: Didn't there use to be field to select the interval in the GUI?12:14
pave1patersonc: And no runtime tests? I see stable-rc having 7000+ tests, 500 of them failing. Well, that's not too useful, either :-(.12:15
patersoncClick the "tests" tab to see the tests12:15
patersoncAnd the "boots" tab to see boots12:16
pave1With 30 days, that looks more useful. Not too many tests there.12:16
pave1So what do we do, simply look there before announcing a release?12:17
patersoncLike the gitlab pipelines, we mainly cover boot tests atm ("boots"), and RT. I'm working on LTP and kselftest support.12:17
pave1I 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
pave1So what do we need to do? Take a look at the dashboard before announcing a release to see there's no red?12:19
patersoncYea something went wrong with that 4.19-rt pipeline12:20
patersoncIt makes sense to check the dashboard12:21
patersoncObviously 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 made12:21
pave1It takes hour or a day?12:21
pave1(And is there way to tell it is done?)12:22
patersoncI'm not sure the dashboard shows it. Can probably work it out using the api12:22
pave1Hmm :-)12:24
iwamatsuIs there an email notification for that now?12:24
iwamatsuapi only?12:24
patersoncThere 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 list12:25
patersoncI'll investigate12:25
pave1The webpage is strange, I wanted to bookmark version with i=30, and apparently that can't be done.12:25
pave1Please don't spam the list. Or us.12:25
pave1Perhaps the dashboard should show "testing done"? Or how is it supposed to be useful without that?12:26
iwamatsuI see.12:26
patersonci=30 gets removed from the URL because it's the default12:26
pave1patersonc: Except that it is not. Apparently i=7 is the default.12:27
pave1i=60 version can be bookmarked, I guess that's good enough.12:27
pave1Which 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
patersoncoh 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 3012:28
patersoncI'll report it :P12:28
pave1Thanks!12:28
pave1Anything more on testing?12:29
pave1312:30
pave1212:30
pave1112:30
pave1#topic AOB12:30
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"12:30
pave1I got spam from hpe. If someone knows what is going on there or has a working contact, I'd like to know.12:31
pave1Anything else?12:32
iwamatsuI have received that email.;-)12:32
pave1As far as I can see, they are not part of -cip.12:33
pave1And sending email from noreply address, with no way to unsubscribe, is pretty rude (and illegal).12:33
pave1Perhaps it will not happen again.12:34
pave1512:34
pave1412:34
pave1312:34
pave1212:34
pave1112:34
pave1#endmeeting12:34
collab-meetbotMeeting ended Thu Oct  1 12:34:36 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:34
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/10/cip.2026-10-01-12.00.html12:34
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/10/cip.2026-10-01-12.00.txt12:34
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/10/cip.2026-10-01-12.00.log.html12:34
*** collab-meetbot changes topic to "Civil Infrastructure Platform Project. CIP mailing list at https://lists.cip-project.org/g/cip-dev | CIP kernel meeting every Thursday at 13:00 UTC | Find the meeting logs at https://ircbot.wl.linuxfoundation.org/meetings/cip/ and chat logs at https://ircbot.wl.linuxfoundation.org/logs/%23cip/"12:34
pave1Thank you!12:34
ulithanks12:34
masamithank you12:34
iwamatsuThank you12:34
patersoncSee you next week!12:35
pave1Yep, looking forward! :-)12:36
patersoncLooking at cip-dev - we do get KernelCI emails - but only for regressions12:37
patersoncWhich is probably what we want?12:37
*** masami <masami!~masami@FL1-111-168-44-134.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)12:37
pave10 mails so far, IIRC. That's acceptable :-)12:38
patersonce.g. https://lore.kernel.org/cip-dev/177241674295.4931.1639151501403818844@d14e337afe00/12:39
patersonchttps://lists.cip-project.org/g/cip-dev/message/22996?p=%2C%2C%2C100%2C0%2C0%2C0%3A%3Arecentpostdate%2Fsticky%2C%2Ckernelci%2C100%2C2%2C0%2C11943659612:39
pave1Still acceptable, I'd say.12:42
patersoncpave1: Would an email like this be useful for CIP? https://groups.io/g/kernelci-results/topic/status_next_master/12152086213:22
patersoncThen you wouldn't need to use the dashboard unless you wanted to dig into more detail13:22
« Wednesday, 2026-09-30 Index Friday, 2026-10-02 »

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!