13:02:23 <jki> #startmeeting CIP IRC weekly meeting
13:02:23 <collab-meetbot`> Meeting started Thu Mar 23 13:02:23 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:23 <collab-meetbot`> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:02:23 <collab-meetbot`> The meeting name has been set to 'cip_irc_weekly_meeting'
13:02:33 <jki> #topic AI review
13:03:01 <jki> 1. clarify usage of .sources files in cip-kernel-config (patersonc)
13:03:21 <jki> I saw some emails...
13:03:26 <patersonc[m]> Yep
13:04:28 <jki> are we done? clarified?
13:05:07 <patersonc[m]> I think Pavel said that the sources files etc. are still used
13:05:11 <patersonc[m]> So the repo should probably be updated to regenerate the latest set for the SLTS kernels
13:05:23 <jki> who can do that?
13:05:29 <pave1> Nothing needs to be done for slts.
13:05:51 <pave1> But we use them for reviews; we may want them for 6.1.x at some point.
13:05:53 <iwamatsu> Sorry, I do not read it yet.
13:06:13 <pave1> I believe we don't need to do anything at the moment.
13:06:29 <patersonc[m]> I can't see any .sources files in the 5.10.y-cip directories?
13:07:46 <iwamatsu> Probably because it has not been processed for source.
13:08:11 <pave1> Those might be useful. I guess we are using 4.19.X sources at the mmoment.
13:08:57 <iwamatsu> I will take over this AI, patersonc[m], is it OK?
13:09:10 <patersonc[m]> Sure
13:09:11 <patersonc[m]> Thanks
13:09:16 <jki> great, noted
13:09:24 <jki> next?
13:10:47 <jki> 2. reach out to Greg regarding LTS (jan)
13:10:52 <jki> ok, status update:
13:11:07 <jki> got a first reply from Raphael (Debian LTS)
13:11:17 <jki> there is also interest but also questions
13:11:27 <jki> replied, waiting for follow up
13:11:59 <jki> I'm now away for a week, don't think I will manage to write a first email to Greg anymore
13:12:25 <jki> also, regard target address(es) for that, I received no further update
13:12:47 <jki> maybe I will manage to write a quick follow-up to Linaro still today
13:12:55 <jki> all on that from me
13:13:15 <jki> anything else?
13:13:34 <jki> 3
13:13:36 <jki> 2
13:13:38 <jki> 1
13:13:41 <jki> #topic Kernel maintenance updates
13:14:12 <masami> This week reported 6 new CVEs and 2 updated CVEs.
13:14:14 <uli> reviewing/backporting patches from 4.14
13:14:25 <pave1> I did reviews on 5.10.176.
13:14:49 <iwamatsu> I am reviewing 5.10.176.
13:17:13 <jki> anything else?
13:17:46 <jki> 3
13:17:48 <jki> 2
13:17:50 <jki> 1
13:17:53 <jki> #topic Kernel release status
13:17:56 <jki> -4.4
13:18:08 <uli> on track; patch quality seems to be unchanged :)
13:18:56 <jki> still great? :)
13:19:02 <jki> good
13:19:16 <jki> -4.19
13:19:34 <pave1> 4.19-cip-rt was released. Next in two months.
13:19:38 <iwamatsu> on track.
13:19:43 <jki> perfect
13:19:44 <iwamatsu> thanks, pave1.
13:19:59 <pave1> I thank you -- matching -cip releases are really helpful.
13:20:51 <jki> -5.10
13:21:13 <pave1> 5.10-cip-rt was released, next in a month.
13:21:19 <iwamatsu> ;-)
13:21:36 <jki> and regular ones are working as well
13:21:41 <jki> perfect
13:21:48 <jki> #topic Kernel testing
13:22:05 <patersonc[m]> Hello
13:22:06 <patersonc[m]> I've now added build/test support for linux-6.2.y, completing the complete stable-rc set.
13:22:44 <patersonc[m]> My MRs for the stable-rc testing configs work still need reviewing please, to make sure we're testing what is required.
13:22:52 <patersonc[m]> Although Iwamatsu-san has started looking I believe
13:23:07 <patersonc[m]> I've also added support for GitLab unit test cases, meaning we have a much friendlier top-level view of test results
13:23:21 <patersonc[m]> e.g. https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/810411346/test_report
13:23:21 <patersonc[m]> Thanks to Sietze for the pointer
13:23:39 <sietze> Happy to help!
13:23:56 <patersonc[m]> That's about it from me this week
13:24:57 <pave1> From ... for example https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/814932089
13:25:07 <pave1> ...how can I get to the summary?
13:25:14 <arisut> I'm updating KernelCI, i'm following warnings on KernelCI and
13:25:26 <patersonc[m]> pave1: Click on the "Tests" tab
13:25:36 <pave1> Aha, Appending "/test_report" also works.
13:26:14 <pave1> On 5.10.x stable (for example), we have errors, including on qemu.
13:26:28 <patersonc[m]> Yea
13:26:35 <patersonc[m]> Mostly they are SMC "errors"
13:26:43 <arisut> working on it
13:27:06 <pave1> Aha, ok, thanks. Let me know if you see something that smells like kernel problem.
13:27:10 <fbezdeka> Didn't we already conclude that running SMC test on qemu has no value?
13:27:37 <arisut> KernelCI have disabled smc on qemu
13:28:06 <patersonc[m]> fbezdeka: Good point. We didn't stop that test on the gitlab ci setup. I'll add it to my todos
13:28:56 <patersonc[m]> Oh, I have one more test related topic - the gitlab runners have been upgraded. Let me know if anyone sees any issues
13:30:02 <jki> that's the disadvantage of having two types of test descriptions...
13:30:13 <patersonc[m]> yep
13:32:05 <jki> anything else on testing?
13:33:06 <jki> 3
13:33:08 <jki> 2
13:33:10 <jki> 1
13:33:13 <jki> #topic AOB
13:33:30 <jki> one topic from: who can run the meeting next week? I'm on vacation
13:35:12 <patersonc[m]> I can
13:35:21 <pave1> Thank you!
13:35:29 <jki> thanks a lot!
13:35:38 <pave1> On a related note, we'll have dst shift in europe.
13:35:49 <jki> jep, this weekend
13:35:50 <pave1> I guess meeting stays at 13utc?
13:38:06 <jki> I think we followed CEST in the past, checking...
13:38:17 <patersonc[m]> Fine with me
13:38:30 <pave1> So for the record 12utc would be prefferable for me.
13:38:54 <patersonc[m]> And perhaps more preferable for Japan...
13:38:57 <iwamatsu> both ok for me
13:39:15 <masami> me too. both ok.
13:39:18 <patersonc[m]> I can do 12utc during the summer
13:40:12 <patersonc[m]> And actually, by the time we hit winter this year it'll be okay for me as well,
13:40:21 <jki> yeah, we where on 12 UTC in summer times
13:40:34 <arisut> Ok for me
13:40:52 <jki> but we shifted due to request of some special contributor
13:41:24 <jki> actually that was the reason, not the DST switch
13:41:46 <patersonc[m]> Yea that was my fault
13:41:52 <jki> anyway, we are flexible depending on everyone's availability
13:42:26 <jki> 12 UTC from next week on? if so, chris is in charge adjusting things for that
13:42:37 <patersonc[m]> Woo
13:42:40 <jki> I "only" then have to recall it next but one week ;)
13:43:41 <patersonc[m]> Another topic: Does anyone happen to have an old beaglebone black board they don't want?
13:43:59 <patersonc[m]> I want to get another one into a lab, as we only have 3 at the moment
13:44:13 <jki> are they no only obtainable?
13:44:17 <jki> no longer
13:44:51 <patersonc[m]> They probably are. I'm not sure on the exact variant we use though?
13:45:08 <jki> BeagleBone Black IIRC
13:45:55 <patersonc[m]> I guess one of these then? https://uk.farnell.com/seeed-studio/102110420/beaglebone-black/dp/3520081
13:46:12 <jki> looks very familiar
13:46:22 <patersonc[m]> Okay
13:46:26 <jki> that's at least the one I tested isar-cip-core on
13:46:35 <patersonc[m]> Maybe CIP can buy one and I'll put it in my lab at home
13:47:05 <jki> no one here has budget authority ;)
13:47:26 <jki> but I would support such a request
13:47:41 <patersonc[m]> Thanks
13:48:41 <jki> just bring it up on the next TSC (where I can't support this myself, though) as Testing WG chair
13:48:50 <patersonc[m]> sure
13:49:05 <jki> any other AOBs?
13:49:25 <pave1> Nothing from me. I assume we meet next week at 12utc?
13:50:01 <patersonc[m]> yep
13:50:14 <jki> :thumbsup:
13:50:32 <jki> good, then closing in...
13:50:38 <jki> 3
13:50:40 <jki> 2
13:50:42 <jki> 1
13:50:44 <jki> #endmeeting