Thursday, 2024-10-17

« Wednesday, 2024-10-16 Index Friday, 2024-10-18 »
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip06:25
*** prabhakalad <prabhakalad!~prabhakar@147.161.237.25> has quit IRC (Quit: Konversation terminated!)09:21
*** prabhakalad <prabhakalad!~prabhakar@147.161.237.25> has joined #cip09:21
*** cbeznea <cbeznea!~cbeznea@82.78.167.23> has joined #cip11:19
*** masami <masami!~masami@FL1-118-111-145-206.tky.mesh.ad.jp> has joined #cip12:59
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:2798:f805:7ea0:72d9> has joined #cip13:00
pave1Hi!13:00
ulihello13:00
masamihi13:01
arisuthi13:01
patersonchi13:01
iwamatsu__hello13:01
pave1Okay, lets start13:02
pave1#startmeeting CIP IRC weekly meeting13:02
collab-meetbotMeeting started Thu Oct 17 13:02:49 2024 UTC and is due to finish in 60 minutes.  The chair is pave1. Information about MeetBot at http://wiki.debian.org/MeetBot.13:02
collab-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:02
collab-meetbotThe meeting name has been set to 'cip_irc_weekly_meeting'13:02
*** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)"13:02
pave1#topic AI review13:02
*** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:02
pave1-  prepare blog entry on SLTS kernel state and challenges [Jan]13:03
pave1Jan is not here, so skip.13:03
pave1Anything else?13:03
pave1513:03
pave1413:03
pave1313:03
pave1213:03
pave1113:03
pave1#topic Kernel maintenance updates13:03
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:03
ulii'm reviewing 6.1.11313:03
masamiThis week reported 1 new CVEs and 14 updated CVEs.13:03
pave1I'm reviewing 6.1.113.13:03
iwamatsu__ I am reviewing 6.1.11313:03
pave1313:04
pave1213:04
pave1113:04
pave1#topic Kernel release status13:04
*** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:04
pave1iwamatsu, can you run the script?13:04
iwamatsu__OK13:05
pave14.19-cip-rt is due to next week, otherwise -rt should be on track.13:05
iwamatsu__Date the data is created: Thu Oct 17 12:55:37 PM UTC 202413:05
iwamatsu__linux-4.4.y-cip: interval 30 day13:05
iwamatsu__  latest version: v4.4.302-cip9213:05
iwamatsu__  latest version release date: Wed Oct  9 04:23:37 AM UTC 202413:05
iwamatsu__  limit date: Fri Nov  8 04:23:37 AM UTC 2024Status: On track13:05
iwamatsu__linux-4.4.y-cip-rt: interval 60 day13:05
iwamatsu__  latest version: v4.4.302-cip91-rt5113:05
iwamatsu__  latest version release date: Mon Sep 30 09:48:28 AM UTC 202413:05
iwamatsu__  limit date: Fri Nov 29 09:48:28 AM UTC 2024Status: On track13:05
iwamatsu__linux-4.19.y-cip: interval 30 day13:05
iwamatsu__  latest version: v4.19.322-cip11313:05
iwamatsu__  latest version release date: Tue Sep 24 09:32:37 AM UTC 202413:05
iwamatsu__  limit date: Thu Oct 24 09:32:37 AM UTC 2024Status: On track13:05
iwamatsu__linux-4.19.y-cip-rt: interval 60 day13:05
iwamatsu__  latest version: v4.19.322-cip113-rt3813:05
iwamatsu__  latest version release date: Tue Sep 24 10:34:04 AM UTC 202413:05
iwamatsu__  limit date: Sat Nov 23 10:34:04 AM UTC 2024Status: On track13:05
iwamatsu__linux-5.10.y-cip: interval 30 day13:05
pave1Hmm. Paste did not work well.13:06
pave1But I guess everything is on track?13:06
iwamatsu__https://www.nigauri.org/~iwamatsu/trash/status.txt13:06
iwamatsu__Yes, all green13:07
pave1linux-5.10.y-cip: interval 30 day13:07
pave1  latest version: v5.10.226-cip5313:07
pave1  latest version release date: Wed Oct  9 10:54:23 PM UTC 202413:07
pave1  limit date: Fri Nov  8 10:54:23 PM UTC 2024Status: On track13:07
pave1linux-5.10.y-cip-rt: interval 60 day13:07
pave1  latest version: v5.10.224-cip52-rt2213:07
pave1  latest version release date: Sat Sep  7 01:56:36 PM UTC 202413:07
pave1  limit date: Wed Nov  6 01:56:36 PM UTC 2024Status: On track13:07
pave1linux-6.1.y-cip: interval 15 day13:07
pave1  latest version: v6.1.112-cip3013:07
pave1  latest version release date: Wed Oct 16 09:40:02 PM UTC 202413:07
pave1  limit date: Thu Oct 31 09:40:02 PM UTC 2024Status: On track13:07
pave1313:07
pave1213:07
pave1113:07
pave1#topic Kernel testing13:08
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:08
patersoncI had to reboot the LAVA master again as it wasn't running the latest version - so the labs all need to be rebooted again, which may take a day or so depending on timezones - sorry13:08
patersoncThis should fix the de0-nano-soc issue though13:09
patersoncSorry about that Pave113:09
pave1No problem, thanks for fixing this!13:09
arisutkci-dev is currently working. it can currently rebuild failed jobs and check for results13:09
patersoncThanks for Iwamatsu-san for pointing out the issue13:09
patersoncThat's great, thank you arisut13:09
patersoncarisut are you going to OSS-J in a couple of weeks?13:10
arisutcurrently we are working on adding bisection13:10
arisutpatersonc, yes13:10
patersoncGreat - can we meet up and discuss various cip/kernelci things like kci-dev?13:10
arisutsure13:10
patersoncIn related news, I've started to migrate the CIP trees into the new kernelCI system13:11
arisutpatersonc, thanks13:11
arisutwhat is still missing ?13:11
patersoncIt'll just do a basic build for now. Need to work out the configs side of things and the testing side - so most of it :P13:12
arisutok13:12
pave1I'd like a feature:13:12
pave1Currently, to test a tree, I need to add .gitlab..yml file, first.13:12
pave1Which ... is not nice when bisecting.13:13
patersoncHopefully with kci-dev you won't need to do that13:13
pave1(Because I'm searching between two commits, and now I'm adding more commits, and ...)13:13
pave1Ok. :-). Looking forward.13:13
arisuthttps://kernelci.github.io/kci-dev/13:14
patersonc In the mid-term I'm investigating moving completely to kernelci and stopping our current gitlab ci approach. How exactly that will look is yet to be worked out13:14
pave1What timeline are we talking about?13:14
patersoncThe new KernelCI dashboard _should_ be much easier to use than the last one.13:14
patersoncpave1: Maybe e/202413:14
pave1Ok, sounds good, thank you!13:15
pave1Anything else?13:15
patersoncI'd like to get it in place for when we have all these new kernels to self-maintain13:15
patersoncWe need more tests done, not just boot tests imho13:15
pave1Yes, that would be nice.13:15
pave1We are going to be very busy at start of 2025.13:15
patersoncYep13:15
patersoncFun fun :)13:15
patersoncGet your estimates into Jan/the CIP board as they are planning the 2025 budget13:16
pave1Anything else?13:16
pave1313:16
pave1213:16
pave1113:16
pave1#topic AOB13:17
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:17
patersonco/      I have an AOB13:17
pave1Go ahead!13:17
patersoncCan anyone remember why we have a separate cip-kernel-config repo for the configs, rather than just add them to the linux-cip tree?13:17
pave1There's not really a good place in linux-cip.13:18
pave1We want our users to clone the kernel trees, they'll not want configs...13:18
patersoncWould they really destroy their trees that much? I guess it's a personal preference thing13:19
patersoncNot a big issue, it just would be easier to make use of them then having them in separate repos13:19
patersoncOn a different topic - iwamatsu__: Do you happen to have a spare BBB board?13:20
pave1Its kind of tradition that configs are not stored in kernel tree :-). It would also mean13:21
pave1having the configs at different branches, and we have other data we need per config -- like13:21
pave1list of files compiled for each config. It would be strange to store that in kernel tree directly.13:21
iwamatsu__Also, I think that putting your own config in the kernel tree is contrary to the stable/CIP patch rule.13:21
patersoncFair doos :)13:22
iwamatsu__patersonc: yes, I have.13:22
iwamatsu__we need more BBB?13:23
patersoncIf you have one and it's not too much effort I'd welcome it your LAVA lab13:24
patersoncDon't worry too much though13:24
iwamatsu__OK, I will connect BBB to my LAVA lab for CIP.13:24
patersoncThank you13:25
pave1Ok, anything else?13:25
pave1313:25
pave1213:25
pave1113:26
pave1#endmeeting13:26
collab-meetbotMeeting ended Thu Oct 17 13:26:13 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:26
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/10/cip.2024-10-17-13.02.html13:26
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/10/cip.2024-10-17-13.02.txt13:26
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/10/cip.2024-10-17-13.02.log.html13:26
*** 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/"13:26
iwamatsu__Thank you13:26
patersoncThanks all13:26
masamithank you13:26
ulithanks13:26
pave1Thank you! See you next week.13:26
arisutthanks13:26
*** masami <masami!~masami@FL1-118-111-145-206.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)13:28
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:2798:f805:7ea0:72d9> has quit IRC (Quit: Client closed)14:01
*** prabhakalad <prabhakalad!~prabhakar@147.161.237.25> has quit IRC (Ping timeout: 252 seconds)14:18
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection)14:25
*** prabhakalad <prabhakalad!~prabhakar@147.161.237.25> has joined #cip14:54
*** prabhakalad <prabhakalad!~prabhakar@147.161.237.25> has quit IRC (Quit: Konversation terminated!)18:56
*** prabhakalad <prabhakalad!~prabhakar@147.161.237.25> has joined #cip18:56
*** cbeznea <cbeznea!~cbeznea@82.78.167.23> has quit IRC (Ping timeout: 252 seconds)19:03
*** prabhakalad <prabhakalad!~prabhakar@147.161.237.25> has quit IRC (Ping timeout: 252 seconds)20:31
*** prabhakalad <prabhakalad!~prabhakar@147.161.237.6> has joined #cip20:31
*** prabhakalad <prabhakalad!~prabhakar@147.161.237.6> has quit IRC (Ping timeout: 246 seconds)20:39
*** prabhakalad <prabhakalad!~prabhakar@147.161.237.25> has joined #cip20:40
« Wednesday, 2024-10-16 Index Friday, 2024-10-18 »

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