Thursday, 2024-02-15

*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip06:32
*** rajm <rajm!~robert@82.27.50.32> has joined #cip06:55
*** frieder <frieder!~frieder@i577B9367.versanet.de> has joined #cip07:37
*** prabhakar <prabhakar!~prabhakar@217.163.141.2> has joined #cip08:46
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has joined #cip08:46
*** prabhakar <prabhakar!~prabhakar@217.163.141.2> has quit IRC (Ping timeout: 260 seconds)09:45
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has quit IRC (Ping timeout: 250 seconds)09:45
*** prabhakar <prabhakar!~prabhakar@217.163.141.2> has joined #cip09:57
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has joined #cip09:57
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 252 seconds)09:58
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has quit IRC (Ping timeout: 250 seconds)10:16
*** prabhakar <prabhakar!~prabhakar@217.163.141.2> has quit IRC (Ping timeout: 255 seconds)10:16
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip11:25
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has joined #cip11:38
*** prabhakar <prabhakar!~prabhakar@217.163.141.2> has joined #cip11:38
*** hunter <hunter!~hunter@d4jvmbldn6sx56dfyhp-4.rev.dnainternet.fi> has joined #cip12:18
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has quit IRC (Quit: Client closed)12:26
*** hunter <hunter!~hunter@d4jvmbldn6sx56dfyhp-4.rev.dnainternet.fi> has quit IRC (Remote host closed the connection)12:41
*** hunter <hunter!~hunter@d4jvmbldn6sx56dfyhp-4.rev.dnainternet.fi> has joined #cip12:41
*** hunter <hunter!~hunter@d4jvmbldn6sx56dfyhp-4.rev.dnainternet.fi> has quit IRC (Remote host closed the connection)12:47
*** prabhakar48 <prabhakar48!~prabhakar@217.163.141.2> has joined #cip12:50
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has joined #cip12:50
*** prabhakar <prabhakar!~prabhakar@217.163.141.2> has quit IRC (Ping timeout: 264 seconds)12:51
*** prabhakar48 <prabhakar48!~prabhakar@217.163.141.2> has quit IRC (Ping timeout: 260 seconds)12:54
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has quit IRC (Ping timeout: 250 seconds)12:54
*** sietze <sietze!~sietze_va@msw-v.fe.bosch.de> has joined #cip12:56
*** hunter <hunter!~hunter@d4jvmbldn6sx56dfyhp-4.rev.dnainternet.fi> has joined #cip12:57
*** masami <masami!~masami@FL1-219-107-72-235.tky.mesh.ad.jp> has joined #cip12:58
*** jki <jki!~jki@62.156.206.57> has joined #cip12:58
jkihey all!13:00
iwamatsuhi13:00
masamihi13:00
sietzeHelloo!13:01
hunterhello!13:01
ulihello13:01
jkilet's go13:02
jki#startmeeting CIP IRC weekly meeting13:02
collab-meetbot`Meeting started Thu Feb 15 13:02:30 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
collab-meetbot`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:02
collab-meetbot`The 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
jki#topic AI review13:02
*** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:02
jki- prepare blog entry on SLTS kernel state and challenges [Jan]13:02
pave1hi!13:02
jkistarted, but still some way - will request feedback when ready13:03
jkiother AIs?13:03
jki313:03
jki213:03
jki113:03
jki#topic Kernel maintenance updates13:03
*** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:03
masamiThis week reported 7 new CVEs and 2 updated CVEs.13:04
ulii'm still reviewing 6.1.7513:04
pave1I was reviewing 6.1.77 and .7813:04
iwamatsuI reviewed 6.1.77, and preparating release 4.19.y-cip tree13:05
jkianything else?13:06
jki513:07
jki413:07
jki313:07
jki213:07
jki113:07
jki#topic Kernel release status13:07
*** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:07
jkiso, just 4.19-cip is delayed, but under preparation, right?13:07
iwamatsuyes13:07
jkiok, then we could already move on...13:08
jki513:08
jki413:08
jki313:08
jki213:08
jki113:08
jki#topic Kernel testing13:08
*** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:08
jkinothing?13:09
pave1From the last meetin -- could we stop broadcasting testing emails13:09
arisutI look into the kernelci api and pratically for working is getting a yaml file like in the example: https://github.com/kernelci/kernelci-pipeline/blob/e79e3743c2caeb106b99e7eaabd5904d0bca950f/config/pipeline.yaml#L20013:09
*** prabhakar <prabhakar!~prabhakar@217.163.141.2> has joined #cip13:10
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has joined #cip13:10
arisutthe way is working is same to the current kernelci configuration but I couldn't reproduce anything useful yet13:11
jkipavel: as chris is not here, we will have to reschedule this topic again13:11
arisutI got the staging acctount today and will try with that13:11
jkiarisut: what was the goal again? sorry, forgot about that13:12
arisutsee if we can use kernelci api for requesting new build directly from the api with a cip account13:13
jkiah, ok13:13
arisutand see what we can do with the new kernelci core api as is yet on development13:14
arisutso that we can maybe send request for making it better13:15
arisutbut my task is just see if we can use it and see what we can do with it13:15
jkigreat, I'm sure they will like to hear early feedback as well!13:16
arisutso if someone else want to try it feel free to send a account request on github13:17
jkiI've chatted these days with Daniel W. about kernelci and -rt testing13:17
arisuthttps://kernelci.org/docs/api/early-access/13:17
jkithere is still not much, as I've noticed (again)13:18
jkibut two improvements are insight:13:18
jki- he wants to enable more rt-tests soon13:18
arisutfeel free to open issues on the github13:18
arisutabout that13:18
jki- kernelci is working on UX improvements that should once allow to show trends in measurements13:19
jkihttps://kernelci.org/blog/posts/2023/ux-analysis/13:19
jkionce we can collect those, it will also be important to improve the background stress for -rt13:20
jkiit's just hackbench...13:20
jkiwhat are we doing in the CIP labs?13:21
jkiprobably only chris knows ;)13:24
jkiok - anything else on testing?13:24
jki513:25
jki413:25
jki313:25
jki213:25
jki113:26
jki#topic AOB13:26
*** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:26
jkikernel is now CNA, more CVE assignments to come - any impact for us expected?13:26
jkiI mean on workflows and daily business13:27
masamiI think it doesn't change our workflow.13:27
pave1I don't think so.13:28
pave1I mean -- I don't expect impact.13:28
jkigood - was my expectation as well13:28
jkithe fuzz will be elsewhere - popcorn time, as lwn.net wrote13:29
jkifound our -rt test case by now: https://gitlab.com/cip-project/cip-testing/linux-cip-ci/-/blob/master/lava_templates/test_cyclictest+hackbench.yaml13:30
jkinot that different from kernelci13:31
jkianyway, we arent't alone here13:31
jkiany other business for today?13:31
jki513:32
jki413:32
jki313:32
jki213:32
jki113:32
jki#endmeeting13:32
collab-meetbot`Meeting ended Thu Feb 15 13:32:49 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:32
collab-meetbot`Minutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/02/cip.2024-02-15-13.02.html13:32
collab-meetbot`Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/02/cip.2024-02-15-13.02.txt13:32
collab-meetbot`Log:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/02/cip.2024-02-15-13.02.log.html13:32
*** 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:32
jkithanks, all!13:32
iwamatsuthank you13:32
hunterthanks everyone!13:32
masamithank you13:33
*** masami <masami!~masami@FL1-219-107-72-235.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)13:33
ulithanks13:33
sietzeThanks!!13:33
*** sietze <sietze!~sietze_va@msw-v.fe.bosch.de> has quit IRC (Quit: Leaving)13:33
*** hunter <hunter!~hunter@d4jvmbldn6sx56dfyhp-4.rev.dnainternet.fi> has quit IRC (Remote host closed the connection)13:33
*** jki <jki!~jki@62.156.206.57> has quit IRC (Remote host closed the connection)13:35
pave1thanks!13:37
*** prabhakar <prabhakar!~prabhakar@217.163.141.2> has quit IRC (Ping timeout: 255 seconds)14:20
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has quit IRC (Ping timeout: 250 seconds)14:20
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.10> has joined #cip14:40
*** prabhakar <prabhakar!~prabhakar@217.163.141.10> has joined #cip14:40
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection)19:10
*** frieder <frieder!~frieder@i577B9367.versanet.de> has quit IRC (Remote host closed the connection)19:52
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.10> has quit IRC (Quit: Client closed)22:28
*** rajm <rajm!~robert@82.27.50.32> has quit IRC (Ping timeout: 264 seconds)22:46

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