IRC logs for #cip for Thursday, 2022-02-17

« Wednesday, 2022-02-16 Index Friday, 2022-02-18 »
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC00:54
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip02:35
*** brlogger <brlogger!~supybot@45.114.123.168> has joined #cip08:53
*** ChanServ sets mode: +o brlogger08:53
*** toscalix <toscalix!~toscalix@251.red-83-52-125.dynamicip.rima-tde.net> has joined #cip09:01
*** uli <uli!~uli@55d42a10.access.ecotel.net> has joined #cip11:41
*** masami <masami!~masami@FL1-110-233-204-67.tky.mesh.ad.jp> has joined #cip12:43
*** josiah <josiah!~kvirc@pool-100-16-211-90.bltmmd.fios.verizon.net> has joined #cip12:56
pave1   /quit13:01
*** pave1 <pave1!~pavel@jabberwock.ucw.cz> has quit IRC13:01
*** jki <jki!~jki@165.225.26.242> has joined #cip13:02
*** pav31 <pav31!~pavel@88.103.227.205> has joined #cip13:02
*** jki <jki!~jki@165.225.26.242> has quit IRC13:02
patersonc[m]Hello?13:04
*** jki <jki!~jki@88.215.87.132> has joined #cip13:04
iwamatsuhi13:04
jki#startmeeting CIP IRC weekly meeting13:04
collab-meetbotMeeting started Thu Feb 17 13:04:24 2022 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.13:04
collab-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:04
collab-meetbotThe meeting name has been set to 'cip_irc_weekly_meeting'13:04
brloggerMeeting started Thu Feb 17 13:04:25 2022 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.13:04
brloggerUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:04
brloggerThe meeting name has been set to 'cip_irc_weekly_meeting'13:04
*** brlogger changes topic to " (Meeting topic: CIP IRC weekly meeting)"13:04
jkihi all13:04
masamihi13:04
ulihello13:04
iwamatsuhi13:04
pav31hi13:04
jkiand hi to all our bots ;)13:04
alicefmhi13:04
patersonc[m]Bonjour13:04
josiahHi13:05
jki#topic AI review13:05
*** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:05
jki1. Try out KernelCI branches for CIP maintainers - pavel & iwamatsu13:06
pav31It looks like kernelci is monitoring kernel.org, and I'm using gitlab for temporary work. I'll ask patersonc to update it.13:06
patersonc[m]Do you want to monitor the RC/test branches only on gitlab?13:07
pav31Yes, please.13:08
patersonc[m]Okay. Sorry about that. I forgot we didn't push those to kernel.org13:08
patersonc[m]Will get fixed13:08
alicefmi will review the MR13:08
pav31Thank you!13:09
jkiother than that, it's working now? or was this a blocker?13:10
patersonc[m]Blocker13:10
jkiok, then let's see - soon13:10
pav31I'll need more help understanding the results -- I tried to go through 4.4 and could find a lot of failures, but no kernel problems I could debug.13:11
jkiwho can help?13:12
patersonc[m]Maybe it's best to ask on #kernelci for help interpreting their results?13:13
patersonc[m]They'd value the feedback as they are looking to improve13:14
pav31I'd really hope someone here would help.13:14
patersonc[m]I'll also look13:15
pav31Thank you.13:15
jkiok, anything else on this?13:16
jki2. Send CIP follow-up on 4.4 discontinuation notice - pavel13:17
pav31Yes, will do. I'll use the wording that was previewed on the mailing list.13:19
jkisounds good to me13:19
jkiTIA!13:19
jki3. Draft press announcement about 5.10 release and 4.4 self-maintenance - jan13:19
jkiunfortunately, still a todo - need to make an appointment with me13:20
jkianything else?13:21
jki313:21
jki213:21
jki113:21
jki#topic Kernel maintenance updates13:21
*** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:21
ulireviewed 5.10.10113:22
masamiThere was 9 new CVEs this week.13:22
iwamatsuI reviewed 5.10.101 and reviewing 5.10.9413:23
masamiworking on to fix CVE-2022-0492.13:23
pav31Reviews: 5.10.101. I started looking at 4.4.X tree.13:23
pav31Would it make sense if I took over formatting patch lists for the wiki?13:24
pav31That's wiki/5.10.y$.13:24
pav31I'm doing it anyway, and it is a bit of manual work.13:25
iwamatsu+113:26
uli+113:26
pav31Ok, thanks :-).13:26
pav31I may add few more fields to the table to make scripting easier.13:26
jkicoordination via the wiki works otherwise?13:27
pav31It is starting to.13:27
jkigood :)13:28
pav31I'd like to talk about 4.4 self-maintainance.13:28
pav31I believe we should start testing 4.9.X in the same way we were testing 4.4.X; if there's breakage pending we should catch it ASAP.13:29
iwamatsuit is good idea.13:30
jkiyet another build and test run, or more effort needed?13:30
pav31Just switch existing 4.4.X testing to run 4.9.X. 4.4.302 was likely the last update.13:31
iwamatsuDoes the test do the same as 4.4.y on reference hw?13:31
patersonc[m]Maybe more reference hardware is natively supported in v4.913:32
patersonc[m]Would we need to create a v4.9 version of cip-kernel-configs?13:32
patersonc[m]Not every config is a defconfig13:32
pav31So the first priority would be to run the existing 4.4 board tests on 4.9.13:32
pav31If there's more hardware that can run, that would be a bonus.13:33
iwamatsuhaha13:33
pav31And yes, that means we probably should add directories in cip-kernel-configs.13:33
iwamatsuWould you like to regenerate it for 4.9?13:35
pav31I have not done it before. I'd be inclined to just cp -a and see what breaks :-).13:35
iwamatsuThe config is specified by path in config files for build framework, so we can control it with the config file, if we do not need to regenerate13:36
jkiwho can pick this topic up?13:39
iwamatsuI see.13:39
iwamatsuI can do first servay13:40
iwamatsusurvey13:40
pav31Thank you.13:40
jkithanks!13:40
patersonc[m]Once the configs are in place I can update linux-stable-rc-ci13:40
pav31Plus, we should probably start reviewing 4.9.X the way we used to review 4.4.X.13:41
iwamatsuOK13:41
jkiindeed13:41
pav31And we should decide branch names and release names for 4.4-stable.13:41
jkijust continue with official style?13:44
iwamatsu+113:44
jkilocation is different, branch name need not be IMHO13:44
pav31Ok. And will we simply name our release "4.4.303"?13:44
jkiif we appended "cip", it would be confusing13:45
iwamatsuI am preferred.13:45
jkiwe would otherwise have to invent a new suffix13:45
pav31Yep. We could append "-stable".13:45
pav31I'm okay with using 4.4.303, but wonder if we should ask Greg if that's okay with him...?13:46
jki+1, better ask first13:46
pav31Ok, cool :-).13:46
jkigives also the chance to explain to him upfront what this branch will be13:46
patersonc[m]We're only pushing to our own repo, so he probably won't care13:47
jkiprobably13:47
patersonc[m]Worth asking just to raise awareness though13:47
jkibut less surprises are better13:47
pav31+1. We may want to publish both stable release and a queue that is considered for testing.13:47
pav31So he was using the namespace first, I guess he will not care but I'd ask.13:48
jkiok - anything else regarding 4.4?13:50
pav31That was everything from my side.13:51
jkiquestion: what is the timeline for a next 5.10-cip release?13:51
iwamatsuSince the GCC problem has been solved, I will be released new 5.10.Y-cip.13:52
iwamatsupav31: 5.10.100-rt has been released, so I would like to based on 5.10.100. is it OK?13:53
pav31Ok with me. That should make my life easy.13:53
iwamatsu;-)13:54
pav31Last 5.10-rt was in 12/2021, so it is time.13:54
jkiyep, that would be great13:54
jkicool - anything else for kernel maintenance?13:54
jki313:54
jki213:55
jki113:55
jki#topic Kernel testing13:55
*** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:55
patersonc[m]GCC issue has been fixed13:55
patersonc[m]Thank you Iwamatsu-san for your help13:55
jkiyeah!13:55
patersonc[m]e.g. https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/47275563713:55
patersonc[m]https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/47317142613:55
patersonc[m]I've also created the MR for adding the gitlab mirror to kernelci: https://github.com/kernelci/kernelci-core/pull/104213:55
patersonc[m]That's probably it from me13:56
jkiany further topics here?13:57
jki313:57
jki213:57
jki113:57
jki#topic AOB13:57
*** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:57
jkinew bot!13:57
jkiold logs have been migrated, new logs should now be generated13:58
jkiwe will see after this meeting13:58
patersonc[m]\o/13:58
jkithen we could actually ask to shut down the previous bot, I think13:58
jkijust the question would be: who to ask?13:59
jkipatersonc[m]: our previous contact had no access anymore, right?13:59
patersonc[m]I think ironfoot does, but not officially14:00
patersonc[m]I have to leave, sorry. Chat to you all soon14:00
jkiok14:01
jkithen let's ask him once we a fine with the new one14:01
jkianything else?14:01
ironfootPing me whenever needed14:01
jkioh, thanks! :)14:02
jkiso, no further topics, let's close in14:02
jki314:02
jki214:02
jki114:02
jki#endmeeting14:02
collab-meetbotMeeting ended Thu Feb 17 14:02:50 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:02
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/cip_irc_weekly_meeting/cip-cip_irc_weekly_meeting.2022-02-17-13.04.html14:02
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/cip_irc_weekly_meeting/cip-cip_irc_weekly_meeting.2022-02-17-13.04.txt14:02
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/cip_irc_weekly_meeting/cip-cip_irc_weekly_meeting.2022-02-17-13.04.log.html14:02
brloggerMeeting ended Thu Feb 17 14:02:50 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:02
brloggerMinutes:        https://irclogs.baserock.org/meetings/cip/2022/02/cip.2022-02-17-13.04.html14:02
brloggerMinutes (text): https://irclogs.baserock.org/meetings/cip/2022/02/cip.2022-02-17-13.04.txt14:02
brloggerLog:            https://irclogs.baserock.org/meetings/cip/2022/02/cip.2022-02-17-13.04.log.html14:02
*** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/"14:02
*** josiah <josiah!~kvirc@pool-100-16-211-90.bltmmd.fios.verizon.net> has quit IRC14:02
jkithank you all!14:03
pav31Thank you... and stay safe!14:03
iwamatsuthank you!14:03
jkilogs look good so far :)14:03
ulithanks14:03
masamithank you14:03
jkihave a nice day!14:03
*** jki <jki!~jki@88.215.87.132> has quit IRC14:04
alicefmthanks14:04
*** pav31 <pav31!~pavel@88.103.227.205> has quit IRC14:33
*** uli <uli!~uli@55d42a10.access.ecotel.net> has left #cip15:26
*** masami <masami!~masami@FL1-110-233-204-67.tky.mesh.ad.jp> has quit IRC16:02
*** lfam <lfam!~lfam@user/lfam> has joined #cip16:12
*** toscalix <toscalix!~toscalix@251.red-83-52-125.dynamicip.rima-tde.net> has quit IRC16:56
*** gavinlai <gavinlai!~gavin@139.59.249.25> has quit IRC18:39
patersonc[m]lwn article on 4.4 stable stats: https://lwn.net/SubscriberLink/884787/d5bf26e46b1c996d/19:41
*** pav31 <pav31!~pavel@88.103.226.233> has joined #cip19:50
*** pav31 <pav31!~pavel@88.103.226.233> has quit IRC20:48
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC23:03
« Wednesday, 2022-02-16 Index Friday, 2022-02-18 »

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