13:01:43 <jki> #startmeeting CIP IRC weekly meeting
13:01:43 <collab-meetbot> Meeting 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:43 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:01:43 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting'
13:01:43 <brlogger> Meeting 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:43 <brlogger> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:01:43 <brlogger> The meeting name has been set to 'cip_irc_weekly_meeting'
13:01:48 <jki> hi everyone
13:01:59 <patersonc[m]> Hello
13:02:00 <uli> hello
13:02:03 <pave1> Hi!
13:02:06 <masami> hi
13:02:07 <alicef> hi
13:04:01 <jki> not yet everyone around, but let's start
13:04:23 <jki> #topic AI review
13:04:29 <jki> 1. Try out KernelCI branches for CIP maintainers - pavel & iwamatsu
13:04:47 <jki> there was some blocker last week - resolved?
13:05:13 <patersonc[m]> Should be
13:05:17 <patersonc[m]> https://linux.kernelci.org/job/cip-gitlab/
13:05:42 <patersonc[m]> Email notifications should also start being sent soon: https://github.com/kernelci/kernelci-jenkins/pull/75
13:07:02 <pave1> Ok, so I randomly clicked on some links, and I see lot of failures but I don't believe they are real.
13:07:05 <pave1> Example: https://linux.kernelci.org/build/id/62176ce806d6ce40ebc62976/logs/
13:07:36 <pave1> https://linux.kernelci.org/build/id/62176c59577e4d6986c6299e/logs/
13:08:20 <pave1> 5.10 has less failures, but some too: https://linux.kernelci.org/build/id/6213dc7954fc8a7036c629be/logs/
13:08:24 <jki> armv3???
13:08:34 <pave1> I'm not the one who configured kernelci :-)
13:10:10 <jki> who can help understanding this? or filtering it if its uninteresting?
13:11:20 <patersonc[m]> Maybe we can filter out a few things we don't care about
13:12:56 <pave1> I'd actually preffer the other way around. Someone who points us "hey, this is a real bug you should be fixing".
13:14:46 <patersonc[m]> No one is manually go through CIP's' test results to tell us what needs addressing. That's CIP's job.
13:15:20 <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 mips
13:15:32 <pave1> Yes, and someone needs to do that. And kernelci is too confusing for me, so I am not volunteering for the job.
13:19:57 <jki> are those failures related to our kernel build or where they present with LTS as well?
13:20:08 <jki> I thought we had that ground truth
13:20:36 <pave1> I believe there are different configs between -stable and -cip, so that results are not easy to compare :-(.
13:22:45 <jki> so, are we lacking time to sort this out step by step?
13:22:49 <jki> or the understanding of what is built how here?
13:23:07 <pave1> I believe we are missing a volunteer :-).
13:23:19 <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:46 <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:57 <patersonc[m]> Look to be the same issues
13:25:17 <jki> so, first thing would be to get rid of those mips reports - or even builds
13:26:43 <jki> and "Acron RiscPC" is also predating our focus
13:26:50 <patersonc[m]> Could you guys create tickets on https://github.com/orgs/kernelci/projects/11 with your change requests? Easy to track that way
13:30:42 <jki> who needs to do that where? under https://github.com/kernelci/kernelci-core/issues?
13:31:58 <patersonc[m]> Yea I guess add them there if they can't be added directly to the project board
13:32:06 <patersonc[m]> Add a CIP label
13:34:09 <jki> and that will solve our volunteers issue as well? :)
13:35:56 <jki> ok, seems we are not making progress here - would be a pity, though, if this block kernelci usage, after all the investments so far
13:36:40 <patersonc[m]> If there are tickets Alice and I will gradually get to them
13:36:44 <jki> and https://github.com/kernelci/kernelci-core/issues/new/choose does not really fit as well...
13:37:23 <jki> looks as if kernelci knows no bugs ;)
13:38:29 <jki> ok - move on?
13:38:51 <jki> 3
13:38:52 <jki> 2
13:38:53 <alicefm> We also have the KernelCI cip project board https://github.com/orgs/kernelci/projects/11
13:38:54 <jki> 1
13:39:10 <jki> but that board permits no issue submission to my understanding
13:39:24 <jki> once you have an issue, you can add it there, no?
13:39:53 <alicefm> When add a new issue you have to select cip project with label
13:40:11 <alicefm> And will be added in the project board
13:40:18 <jki> I don't have the rights to select labels
13:40:34 <alicefm> Yes
13:40:48 <alicefm> Is just under the label selection
13:41:00 <jki> yes, and I don't have the rights to edit anything there
13:41:16 <jki> alicef: please do that, you likely have as project member
13:41:24 <alicefm> Also on your issues?
13:41:44 <alicefm> I understand others issues but your?
13:42:04 <jki> I have the editor open - do I need to submit first?
13:42:19 <alicefm> I think you should be able to select it during submission
13:42:28 <jki> and that is not the case here
13:43:01 <alicefm> Ok I will check this
13:44:06 <jki> I can submit a short placeholder issue nevertheless ("CIP: ...")
13:44:40 <jki> done
13:44:43 <jki> https://github.com/kernelci/kernelci-core/issues/1053
13:44:53 <jki> ok, next topic
13:45:04 <jki> 2. Send CIP follow-up on 4.4 discontinuation notice - pavel
13:45:19 <pave1> Done.
13:45:21 <jki> I've seen the message on RT
13:45:30 <jki> on LKML as well then?
13:45:37 <jki> perfect!
13:45:48 <pave1> I have also asked about using 4.4.345 namespace, but Greg was not too happy about that.
13:46:05 <jki> i was expecting this
13:46:45 <jki> yeah, then we either don't tag the non-cip branch or invent something different for the "baseline"
13:47:08 <pave1> I'll check....
13:47:27 <pave1> Here's Greg's reply, it shows original mail went to lkml, too.
13:47:33 <pave1> https://lore.kernel.org/all/Yg8%2FvxWzcc%2Fetxp+@kroah.com/
13:47:44 <pave1> https://lore.kernel.org/all/20220217205550.GA21004@duo.ucw.cz/
13:48:31 <jki> fine
13:48:46 <jki> next topic
13:48:52 <jki> 3. Draft press announcement about 5.10 release and 4.4 self-maintenance - jan
13:49:13 <jki> draft shared with most of you (privately, editing link...)
13:49:31 <jki> thanks for feedback so far already!
13:50:18 <jki> I'll start discussing next steps with Neal - meanwhile further comments are welcome, of course
13:50:52 <jki> anything else?
13:51:19 <jki> 3
13:51:21 <jki> 2
13:51:23 <jki> 1
13:51:26 <jki> #topic Kernel maintenance updates
13:52:14 <uli> reviewed 5.10.102
13:52:39 <pave1> I was reviewing 5.10.102, did 5.10.100-rt release and am preparing 4.4-stable tree.
13:52:49 <masami> There was 7 new CVEs this week.
13:55:05 <jki> any of them already affecting our 4.4?
13:55:21 <pave1> At least 2, yes.
13:55:36 <jki> fixes in 4.9 in sight?
13:57:00 <masami> 4.4 is affected by CVE-2022-25258, CVE-2022-25375.
13:57:16 <masami> both CVEs are already fixed in the mainline and all stable kernels
13:57:34 <masami> These patches are able to apply 4.4.
13:58:09 <jki> ok, still easy ones, good
13:58:29 <pave1> Both are USB gadget issues. I'd not lose sleep over those for now.
13:58:42 <jki> yeah :)
13:59:09 <jki> anything else regarding maintenance?
13:59:49 <jki> 3
13:59:50 <jki> 2
13:59:52 <jki> 1
13:59:54 <jki> #topic Kernel testing
14:00:20 <jki> ...besides what we discussed already
14:00:58 <alicefm> no updates from me
14:01:10 <patersonc[m]> Nothing else from me
14:01:31 <jki> good - then move on
14:01:44 <jki> #topic AOB
14:01:54 <jki> the LF bot is... not working
14:02:00 <jki> Neal is already informed
14:02:37 <jki> at least the logs are not shared - maybe it is recording
14:02:57 <jki> anyway, we still have both options
14:03:06 <jki> anything else from anyone?
14:03:48 <jki> 3
14:03:50 <jki> 2
14:03:53 <jki> 1
14:03:56 <jki> #endmeeting