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

*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip06:51
*** toscalix <toscalix!~toscalix@251.red-83-52-125.dynamicip.rima-tde.net> has joined #cip09:57
*** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has joined #cip11:39
*** uli <uli!~uli@55d421e5.access.ecotel.net> has joined #cip12:17
*** masami <masami!~masami@FL1-110-233-204-67.tky.mesh.ad.jp> has joined #cip12:35
*** pave1 <pave1!~pavel@88.103.227.180> has joined #cip12:59
*** jki <jki!~jki@165.225.27.13> has joined #cip13:00
jki#startmeeting CIP IRC weekly meeting13:01
brloggerMeeting started Thu Feb 24 13:01:43 2022 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.13:01
brloggerUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
brloggerThe meeting name has been set to 'cip_irc_weekly_meeting'13:01
*** brlogger changes topic to " (Meeting topic: CIP IRC weekly meeting)"13:01
collab-meetbotMeeting started Thu Feb 24 13:01:43 2022 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.13:01
collab-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
collab-meetbotThe meeting name has been set to 'cip_irc_weekly_meeting'13:01
jkihi everyone13:01
patersonc[m]Hello13:01
ulihello13:02
pave1Hi!13:02
masamihi13:02
alicefhi13:02
*** josiah <josiah!~kvirc@pool-100-16-211-90.bltmmd.fios.verizon.net> has joined #cip13:03
jkinot yet everyone around, but let's start13:04
jki#topic AI review13:04
*** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:04
jki1. Try out KernelCI branches for CIP maintainers - pavel & iwamatsu13:04
jkithere was some blocker last week - resolved?13:04
patersonc[m]Should be13:05
patersonc[m]https://linux.kernelci.org/job/cip-gitlab/13:05
patersonc[m]Email notifications should also start being sent soon: https://github.com/kernelci/kernelci-jenkins/pull/7513:05
pave1Ok, so I randomly clicked on some links, and I see lot of failures but I don't believe they are real.13:07
pave1Example: https://linux.kernelci.org/build/id/62176ce806d6ce40ebc62976/logs/13:07
pave1https://linux.kernelci.org/build/id/62176c59577e4d6986c6299e/logs/13:07
pave15.10 has less failures, but some too: https://linux.kernelci.org/build/id/6213dc7954fc8a7036c629be/logs/13:08
jkiarmv3???13:08
pave1I'm not the one who configured kernelci :-)13:08
jkiwho can help understanding this? or filtering it if its uninteresting?13:10
patersonc[m]Maybe we can filter out a few things we don't care about13:11
pave1I'd actually preffer the other way around. Someone who points us "hey, this is a real bug you should be fixing".13:12
patersonc[m]No one is manually go through CIP's' test results to tell us what needs addressing. That's CIP's job.13:14
patersonc[m]If there are legacy things that always kick of build errors for things we don't care about, e.g. mips, then we should just not build for mips13:15
pave1Yes, and someone needs to do that. And kernelci is too confusing for me, so I am not volunteering for the job.13:15
jkiare those failures related to our kernel build or where they present with LTS as well?13:19
jkiI thought we had that ground truth13:20
pave1I believe there are different configs between -stable and -cip, so that results are not easy to compare :-(.13:20
jkiso, are we lacking time to sort this out step by step?13:22
jkior the understanding of what is built how here?13:22
pave1I believe we are missing a volunteer :-).13:23
patersonc[m]4.4.302 results are here: https://linux.kernelci.org/build/stable-rc/branch/linux-4.4.y/kernel/v4.4.302/13:23
patersonc[m]Pavel's test branch version here: https://linux.kernelci.org/build/cip-gitlab/branch/ci%2Fpavel%2Flinux-test/kernel/v4.4.302-1101-gc2ab5f3d8331/13:23
patersonc[m]Look to be the same issues13:23
jkiso, first thing would be to get rid of those mips reports - or even builds13:25
jkiand "Acron RiscPC" is also predating our focus13:26
patersonc[m]Could you guys create tickets on https://github.com/orgs/kernelci/projects/11 with your change requests? Easy to track that way13:26
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC13:27
jkiwho needs to do that where? under https://github.com/kernelci/kernelci-core/issues?13:30
patersonc[m]Yea I guess add them there if they can't be added directly to the project board13:31
patersonc[m]Add a CIP label13:32
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip13:33
jkiand that will solve our volunteers issue as well? :)13:34
jkiok, seems we are not making progress here - would be a pity, though, if this block kernelci usage, after all the investments so far13:35
patersonc[m]If there are tickets Alice and I will gradually get to them13:36
jkiand https://github.com/kernelci/kernelci-core/issues/new/choose does not really fit as well...13:36
jkilooks as if kernelci knows no bugs ;)13:37
jkiok - move on?13:38
jki313:38
jki213:38
alicefmWe also have the KernelCI cip project board https://github.com/orgs/kernelci/projects/1113:38
jki113:38
jkibut that board permits no issue submission to my understanding13:39
jkionce you have an issue, you can add it there, no?13:39
alicefmWhen add a new issue you have to select cip project with label13:39
alicefmAnd will be added in the project board13:40
jkiI don't have the rights to select labels13:40
alicefmYes13:40
alicefmIs just under the label selection13:40
jkiyes, and I don't have the rights to edit anything there13:41
jkialicef: please do that, you likely have as project member13:41
alicefmAlso on your issues?13:41
alicefmI understand others issues but your?13:41
jkiI have the editor open - do I need to submit first?13:42
alicefmI think you should be able to select it during submission13:42
jkiand that is not the case here13:42
alicefmOk I will check this13:43
jkiI can submit a short placeholder issue nevertheless ("CIP: ...")13:44
jkidone13:44
jkihttps://github.com/kernelci/kernelci-core/issues/105313:44
jkiok, next topic13:44
jki2. Send CIP follow-up on 4.4 discontinuation notice - pavel13:45
pave1Done.13:45
jkiI've seen the message on RT13:45
jkion LKML as well then?13:45
jkiperfect!13:45
pave1I have also asked about using 4.4.345 namespace, but Greg was not too happy about that.13:45
jkii was expecting this13:46
jkiyeah, then we either don't tag the non-cip branch or invent something different for the "baseline"13:46
pave1I'll check....13:47
pave1Here's Greg's reply, it shows original mail went to lkml, too.13:47
pave1https://lore.kernel.org/all/Yg8%2FvxWzcc%2Fetxp+@kroah.com/13:47
pave1https://lore.kernel.org/all/20220217205550.GA21004@duo.ucw.cz/13:47
jkifine13:48
jkinext topic13:48
jki3. Draft press announcement about 5.10 release and 4.4 self-maintenance - jan13:48
jkidraft shared with most of you (privately, editing link...)13:49
jkithanks for feedback so far already!13:49
jkiI'll start discussing next steps with Neal - meanwhile further comments are welcome, of course13:50
jkianything else?13:50
jki313:51
jki213:51
jki113:51
jki#topic Kernel maintenance updates13:51
*** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:51
ulireviewed 5.10.10213:52
pave1I was reviewing 5.10.102, did 5.10.100-rt release and am preparing 4.4-stable tree.13:52
masamiThere was 7 new CVEs this week.13:52
jkiany of them already affecting our 4.4?13:55
pave1At least 2, yes.13:55
jkifixes in 4.9 in sight?13:55
masami4.4 is affected by CVE-2022-25258, CVE-2022-25375.13:57
masamiboth CVEs are already fixed in the mainline and all stable kernels13:57
masamiThese patches are able to apply 4.4.13:57
jkiok, still easy ones, good13:58
pave1Both are USB gadget issues. I'd not lose sleep over those for now.13:58
jkiyeah :)13:58
jkianything else regarding maintenance?13:59
jki313:59
jki213:59
jki113:59
jki#topic Kernel testing13:59
*** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:59
jki...besides what we discussed already14:00
alicefmno updates from me14:00
patersonc[m]Nothing else from me14:01
jkigood - then move on14:01
jki#topic AOB14:01
*** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"14:01
jkithe LF bot is... not working14:01
jkiNeal is already informed14:02
jkiat least the logs are not shared - maybe it is recording14:02
jkianyway, we still have both options14:02
jkianything else from anyone?14:03
jki314:03
jki214:03
jki114:03
jki#endmeeting14:03
brloggerMeeting ended Thu Feb 24 14:03:56 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:03
brloggerMinutes:        https://irclogs.baserock.org/meetings/cip/2022/02/cip.2022-02-24-13.01.html14:03
brloggerMinutes (text): https://irclogs.baserock.org/meetings/cip/2022/02/cip.2022-02-24-13.01.txt14:03
brloggerLog:            https://irclogs.baserock.org/meetings/cip/2022/02/cip.2022-02-24-13.01.log.html14:03
*** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/"14:03
collab-meetbotMeeting ended Thu Feb 24 14:03:56 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:03
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/cip_irc_weekly_meeting/cip-cip_irc_weekly_meeting.2022-02-24-13.01.html14:03
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/cip_irc_weekly_meeting/cip-cip_irc_weekly_meeting.2022-02-24-13.01.txt14:03
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/cip_irc_weekly_meeting/cip-cip_irc_weekly_meeting.2022-02-24-13.01.log.html14:03
pave1Thank you, stay safe!14:04
jkithank you all14:04
ulithanks14:04
masamithank you14:04
alicefmThanks you14:04
jkistay safe - also on this sad day14:04
jkibye!14:04
*** josiah <josiah!~kvirc@pool-100-16-211-90.bltmmd.fios.verizon.net> has quit IRC14:05
*** jki <jki!~jki@165.225.27.13> has quit IRC14:05
*** pave1 <pave1!~pavel@88.103.227.180> has quit IRC14:07
*** masami <masami!~masami@FL1-110-233-204-67.tky.mesh.ad.jp> has quit IRC14:25
*** toscalix_ <toscalix_!~toscalix@251.red-83-52-125.dynamicip.rima-tde.net> has joined #cip14:52
*** toscalix <toscalix!~toscalix@251.red-83-52-125.dynamicip.rima-tde.net> has quit IRC14:53
*** alicef <alicef!~none@gentoo/developer/alicef> has quit IRC15:24
*** alicef <alicef!~none@gentoo/developer/alicef> has joined #cip15:25
*** alicef_ <alicef_!~none@gentoo/developer/alicef> has joined #cip15:27
*** alicef <alicef!~none@gentoo/developer/alicef> has quit IRC15:29
*** alicef <alicef!~none@gentoo/developer/alicef> has joined #cip15:36
*** alicef_ <alicef_!~none@gentoo/developer/alicef> has quit IRC15:36
*** alicef <alicef!~none@gentoo/developer/alicef> has quit IRC15:39
*** alicef <alicef!~none@gentoo/developer/alicef> has joined #cip15:40
*** uli <uli!~uli@55d421e5.access.ecotel.net> has left #cip16:53
*** toscalix_ <toscalix_!~toscalix@251.red-83-52-125.dynamicip.rima-tde.net> has quit IRC16:53
*** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has quit IRC19:02
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC19:05
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC23:04

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