Thursday, 2023-03-16

*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip07:12
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip08:01
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip08:40
*** uli <uli!~uli@2001:4091:a245:8141:c1bb:8a36:e8da:83f8> has joined #cip12:15
*** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has joined #cip12:54
*** jki <jki!~jki@195.145.170.158> has joined #cip12:59
jkihi all13:00
alicefmhi13:00
patersonc[m]Hello13:00
ulihello13:00
masamihello13:00
*** pave1 <pave1!~pavel@jabberwock.ucw.cz> has joined #cip13:02
jkiok, let's go13:02
jki#startmeeting CIP IRC weekly meeting13:02
collab-meetbot`Meeting started Thu Mar 16 13:02:58 2023 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:03
*** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:03
jki1. clarify usage of .sources files in cip-kernel-config (patersonc)13:03
patersonc[m]nope13:03
jkiwasn't there some mail sent already?13:03
patersonc[m]I don't remember sending something :P13:04
jkithen I dreamt ;)13:04
jki2. reach out to Greg regarding LTS (jan)13:04
jkiok, status here:13:04
jkiI mailed to Raphael of the Debian LTS project13:04
jkino reply yet though13:04
jkibut I learned from Linaro folks yesterday that there is a broader need still13:05
jkisame motivations as for us, and maybe there is chance to partner - with whoever wants to support longer LTS again13:06
jkiwill need to follow up with them as well13:06
ulidid anybody get those slides from greg that were mentioned last time?13:07
jkiit's still just a single slide with already known content13:08
ulicould you send me a copy anyway? just for reference...13:08
jkisure13:09
ulithanks13:09
jkidone13:09
uligreat13:09
jkiok, anything else here?13:10
jki313:10
jki213:10
jki113:10
jki#topic Kernel maintenance updates13:10
*** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:10
masamiThis week reported 6 new CVEs and 7 updated CVEs.13:11
ulireviewing 5.10.17313:11
pave1reviewing 5.10.173/4/5.13:11
jkianything else?13:15
jki313:15
jki213:15
jki113:15
jki#topic Kernel release status13:15
*** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:15
jki- 4.413:15
uli4.4.302-cip73 is out13:15
jki-rt should follow, schedule-wise, right?13:16
jkiany blockers?13:16
ulinone that i'm aware of13:16
pave1'll take a look. Need to compare 4.14-rt releases.13:16
jkiok13:17
jki- 4.1913:17
pave1-rt was released, matching 4.19-cip would be nice.13:18
jkiI guess you will ping iwamatsu-san on that13:18
jkigood13:19
jki- 5.1013:19
jkiall up to date, iirc13:19
pave1Yep. He's watching -rt announcements, too.13:19
jkiok, anything else?13:20
jki313:20
jki213:20
jki113:20
jki#topic Kernel testing13:20
*** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:20
patersonc[m]Hello13:21
patersonc[m]I've got three things today.13:21
patersonc[m]1)13:21
patersonc[m]As part of improving/formalising CIP testing I've started to draft a requirements document.13:21
patersonc[m]Once the initial draft is complete I'll invite comments/review from you all, please :)13:21
patersonc[m]2)13:21
patersonc[m]I've started to monitor and report to Greg the results of our testing on all of the LTS release candidates.13:21
patersonc[m]I still need to add v6.2 support.13:21
patersonc[m]My MRs from this work still need reviewing please, to make sure we're testing what is required.13:21
patersonc[m]Please see bottom of https://lists.cip-project.org/g/cip-dev/message/1097313:21
patersonc[m]3)13:21
patersonc[m]I had a chat with Sietze (Bosch) last week about frontends for our CI.13:21
patersonc[m]The point here is that unless we want to heavily fork and modify KernelCI, it's never going to meet our non-kernel testing requirements.13:21
patersonc[m]So we'll likely always want to keep our GitLab CI approach.13:21
patersonc[m]The current apprach has drawbacks in that it's hard to track individual test case results between versions etc.13:21
patersonc[m]So we'll likely need to have some sort of front end on top of GitLab to facilitate things.13:22
patersonc[m]Sietze is going to start a survey to see what existing options there are - I'd ideally like to reuse something rather then reinvent the wheel.13:22
patersonc[m]Done. And enter discussion... ;)13:22
jkioverflow :)13:22
jkiexpressing the needs or wishes towards kernelci would still be valuable13:23
jkiat least for the purpose or recording them - and maybe triggering +1 or other remarks13:23
patersonc[m]Agreed, but they are focused on Kernel testing only13:24
jkiwhat are the non-kernel testing needs then?13:24
jkiDebian package testing? -> Debian13:24
patersonc[m]I was thinking cip-core testing, e.g. security packages etc.13:24
jkiCIP image integration -> that is our issue, indeed13:24
jkipackages should eventually all be upstream, thus enabled to be tested by Debian then as well13:25
patersonc[m]It may be that forking kernelci is the best solution for us to handle all of our testing in one place. Maybe another front end will be better. That's what we'll investigate.13:25
jkiok13:26
jkibut also the front-end needs should be clarified if they aren't also relevant beyond us13:26
patersonc[m]Sure. I'm all for reuse, whether it's by us or others13:27
jkigreat13:27
jkianything else regarding testing?13:28
patersonc[m]Any updates from the KernelCI world Arisu -san?13:29
patersonc[m]I guess not :)13:31
jkiarisut: ?13:32
jkiok, move on?13:33
jki313:33
patersonc[m]yea13:33
jki213:33
jki113:33
jki#topic AOB13:33
*** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:33
jkiany other topics for today?13:35
jki313:35
jki213:35
jki113:35
jki#endmeeting13:35
collab-meetbot`Meeting ended Thu Mar 16 13:35:50 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:35
collab-meetbot`Minutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/03/cip.2023-03-16-13.02.html13:35
collab-meetbot`Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/03/cip.2023-03-16-13.02.txt13:35
collab-meetbot`Log:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/03/cip.2023-03-16-13.02.log.html13:35
*** 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:35
jkithank you all!13:35
pave1Thank you!13:35
ulithanks13:36
masamithank you13:36
iwamatsuoh, sorry.13:36
patersonc[m]Thanks13:36
iwamatsuI just noticed this.13:37
*** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)13:37
patersonc[m]:)13:38
jkiiwamatsu: no problem!13:39
jkiunless you had an urgent topic13:39
patersonc[m]iwamatsu: Could you review the MRs in https://lists.cip-project.org/g/cip-dev/message/10973 for me?13:39
alicefmthanks yk13:40
alicefmyou13:40
alicefmpatersonc no updatds13:41
alicefmupdates13:41
patersonc[m]👍️13:41
iwamatsujki: I dont have a topic.13:43
iwamatsupatersonc[m]: OK, I will check it .13:43
patersonc[m]Thank you13:43
*** jki <jki!~jki@195.145.170.158> has quit IRC (Quit: Leaving)13:46
*** uli <uli!~uli@2001:4091:a245:8141:c1bb:8a36:e8da:83f8> has left #cip (Leaving)13:49
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection)15:30
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)20:47
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip21:02
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 256 seconds)22:51
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)23:14

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