Thursday, 2023-02-09

« Wednesday, 2023-02-08 Index Friday, 2023-02-10 »
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip04:16
*** uli <uli!~uli@175.176.15.134> has joined #cip10:28
*** alicefm <alicefm!~alicefm@user/alicefm> has quit IRC (Quit: Bridge terminating on SIGTERM)11:37
*** toscalix[m] <toscalix[m]!~toscalixm@2001:470:69fc:105::157a> has quit IRC (Quit: Bridge terminating on SIGTERM)11:37
*** patersonc[m] <patersonc[m]!~patersonc@2001:470:69fc:105::aaf> has quit IRC (Quit: Bridge terminating on SIGTERM)11:37
*** alicefm <alicefm!~alicefm@user/alicefm> has joined #cip11:42
*** patersonc[m] <patersonc[m]!~patersonc@2001:470:69fc:105::aaf> has joined #cip12:01
*** toscalix[m] <toscalix[m]!~toscalixm@2001:470:69fc:105::157a> has joined #cip12:01
*** ironfoot_ is now known as ironfoot12:03
*** toscalix[m] <toscalix[m]!~toscalixm@2001:470:69fc:105::157a> has quit IRC (Ping timeout: 246 seconds)12:14
*** alicefm <alicefm!~alicefm@user/alicefm> has quit IRC (Ping timeout: 248 seconds)12:14
*** patersonc[m] <patersonc[m]!~patersonc@2001:470:69fc:105::aaf> has quit IRC (Ping timeout: 246 seconds)12:14
*** patersonc[m] <patersonc[m]!~patersonc@2001:470:69fc:105::aaf> has joined #cip12:25
*** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has joined #cip12:54
*** jki <jki!~jki@88.215.103.113> has joined #cip13:00
jkihi!13:00
iwamatsu`hello13:00
ulihello13:00
masamihi13:01
pave1hi!13:01
alicefhi13:01
patersonc[m]Hello13:02
jkilet's go then13:02
jki#startmeeting CIP IRC weekly meeting13:02
collab-meetbot`Meeting started Thu Feb  9 13:02:47 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:02
*** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:02
jki1. enable more stable trees for testing (patersonc)13:03
*** patersonc <patersonc!~patersonc@212.132.163.107> has joined #cip13:04
jkipatersonc: any comment on the AT?13:05
patersoncSorry, Matrix doesn't seem to be working with this channel, I've just switched to a different client13:05
pave1(it was 1. enable more stable trees for testing (patersonc))13:05
patersoncThanks Pavel13:06
patersoncNo, I haven't done it yet, sorry13:06
*** alicefm <alicefm!~alicefm@user/alicefm> has joined #cip13:06
jki2. report 6.1 test plan to LKML (?)13:06
jkidespite the 6.1 LTS announcement, this is not fully obsolete, I think13:06
jkididn't recall if someone took that AI already13:07
pave1Do you have link to the announcement?13:07
*** toscalix[m] <toscalix[m]!~toscalixm@2001:470:69fc:105::157a> has joined #cip13:07
jkihttps://kernel.org/category/releases.html13:07
pave1Thanks!13:07
jkinot sure if there was an email as well13:07
patersoncI missed that. Thanks jki13:09
iwamatsu`it is a good news.13:09
pave1Interesting note is that projected EOL is same for 5.10 and 6.1.13:10
pave1That will be rather busy December for us.13:10
jkiyes13:10
jkiOTOH, the value of the CIP kernel increases again13:10
pave1I guess the testing team should do the emailing? Alternatively I can do it if I know what to write there.13:11
pave1"We'll likely maintain 6.1 in future, so we'll start testing it in near future?" :-)13:12
jkieven better would be if we started already13:12
jki"we will likely select 6.1 as the next CIP kernel"13:13
jkiso, does this AI effective depend on the first AI?13:14
patersoncWe'll get the testing in place, then start reporting back on the stable-rc reviews13:14
patersoncThe project can announce support for 6.1-cip when it's ready to officially decide13:15
jkionce we do the reporting, it is still valuable to highlight this13:15
jkiok13:15
jkianything else?13:16
jki313:16
jki213:16
jki113:16
jki#topic Kernel maintenance updates13:16
*** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:16
ulinow reviewing 5.10.16813:17
pave1I did reviews on 5.10.166, 167, 168.13:17
masamiThis week reported 4 new CVEs and 2 updated CVEs.13:17
pave1I'll be travelling next week, so may not make it to the meetings.13:17
iwamatsu`I reviewed 5.10.166 and 167.13:17
jkianything else?13:19
jki313:20
jki213:20
jki113:20
jki#topic Kernel release status13:20
*** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:20
jki- 4.413:20
ulipave1 released 4.4.302-cip72-rt4213:21
jkiok13:22
jki- 4.1913:22
iwamatsu`About RT, RT team had been released v4.19.271-rt120. We can sync this version13:23
pave1I believe RT is due to next month, so no need to do anything now?13:24
jkiformally correct13:25
iwamatsu`Yes, I think so.13:25
jkithen we are on schedule13:26
jki- 5.1013:26
iwamatsu`And LTS is 272. I will release cip version with this.13:26
iwamatsu`about 5.10, on schedule.13:27
pave1Last -rt was on Jan 19, so we have few more days.13:28
iwamatsu`I will release cip version with 5.10.167 in this week.13:28
jkiok13:28
jkigood13:28
jki#topic Kernel testing13:28
*** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:28
patersonc[m]I've spent some more time this week on sorting out our LAVA version upgrade13:29
alicefupdate the PR on kernelci for using cip-kernel-config both with 5.10.y-cip and 4.4.y-cip13:30
patersonc[m]I've seen a few instances where it doesn't load properly though with some of the database migrations. I'm still investigating this.13:30
alicefhttps://github.com/kernelci/kernelci-core/pull/170513:30
patersonc[m]Here's a question for you all - how long do we want to keep test job logs for on LAVA?13:30
ulihow long are they kept now?13:32
patersonc[m]Currently forever13:32
patersonc[m]And the database/logs are over 6GB, which is a bit big13:32
patersonc[m]I'd like to cut it all down, but it depends on what our requirements are13:33
pave1Forever is good :-). Could we move them to some kind of archive after a year, for example?13:33
patersonc[m]We can keep a backup of the database/logs, but it wouldn't be browsable from within LAVA13:34
patersonc[m]We'd have to either manually untar the logs and search, or load it back up in another LAVA instance13:34
iwamatsu`Perhaps it is not the period, but the question of which log to record.13:34
pave1I'd say that browsable for year is enough, but I would keep the tars...13:35
uli+113:35
patersonc[m]The database/logs get backed up to AWS every night, so we have that13:35
patersonc[m]I'll set up a cron to cull jobs older than a year from the "production" database13:35
iwamatsu`I see.13:36
patersonc[m]That should speed things up a lot when taking/restoring backups13:36
patersonc[m]We can adjust the time period in future if we change our mind13:36
patersonc[m]Thanks all13:36
iwamatsu`OK. one year is enough, I think.13:37
patersonc[m]Okie Dokie13:39
jkianything else on testing?13:39
patersonc[m]Not from me13:39
jki313:42
jki213:42
jki113:42
jki#topic AOB13:42
*** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:42
*** patersonc <patersonc!~patersonc@212.132.163.107> has quit IRC (Quit: Connection closed)13:43
jkianyone any topic?13:45
jki313:46
jki213:46
jki113:46
jki#endmeeting13:46
collab-meetbot`Meeting ended Thu Feb  9 13:46:30 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:46
collab-meetbot`Minutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/02/cip.2023-02-09-13.02.html13:46
collab-meetbot`Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/02/cip.2023-02-09-13.02.txt13:46
collab-meetbot`Log:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/02/cip.2023-02-09-13.02.log.html13:46
*** 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:46
jkithank you all!13:46
ulithanks13:46
pave1thank you!13:46
patersonc[m]Thanks. Sorry again I missed last week13:46
masamithank you13:46
*** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)13:46
alicefthanks you13:47
iwamatsu`thank you13:47
*** uli <uli!~uli@175.176.15.134> has left #cip (Leaving)13:48
*** jki <jki!~jki@88.215.103.113> has quit IRC (Quit: Leaving)14:07
*** rynofinn____ <rynofinn____!sid362734@id-362734.lymington.irccloud.com> has quit IRC (Ping timeout: 252 seconds)14:19
*** rynofinn____ <rynofinn____!sid362734@id-362734.lymington.irccloud.com> has joined #cip14:22
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)17:54
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 252 seconds)22:45
« Wednesday, 2023-02-08 Index Friday, 2023-02-10 »

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