13:06:23 <pave1> #startmeeting CIP IRC weekly meeting
13:06:23 <collab-meetbot`> Meeting started Thu Apr  7 13:06:23 2022 UTC and is due to finish in 60 minutes.  The chair is pave1. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:06:23 <collab-meetbot`> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:06:23 <collab-meetbot`> The meeting name has been set to 'cip_irc_weekly_meeting'
13:06:24 <brlogger> Meeting started Thu Apr  7 13:06:23 2022 UTC and is due to finish in 60 minutes.  The chair is pave1. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:06:24 <brlogger> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:06:24 <brlogger> The meeting name has been set to 'cip_irc_weekly_meeting'
13:06:54 <pave1> I see patersonc was disconnected, so lets start with kernel maintainance updates and do AIs next?
13:07:03 <pave1> #topic Kernel maintenance updates
13:07:11 <patersonc[m]> I'm still here
13:07:44 <pave1> #topic AI review
13:07:51 <pave1> 1. Resolve/filter irrelevant failures of KernelCI for 4.4-cip - patersonc & alicefm
13:08:12 <pave1> (Sorry, irc said you was disconnected).
13:09:01 <patersonc[m]> No updates from me
13:09:09 <alicef> hi
13:09:15 <alicef> no updates here
13:09:21 <pave1> Hi! and ok.
13:09:23 <pave1> 3
13:09:25 <pave1> 2
13:09:27 <pave1> 1
13:09:33 <pave1> #topic Kernel maintenance updates
13:09:44 <uli> reviewing 5.10.110
13:09:47 <pave1> I am reviewing 5.10.110.
13:10:01 <masami> This week reported 11 new CVEs.
13:10:08 <masami> Most vulnerabilities will cause local DoS.  CVE-2021-39802 may be android specific.
13:10:10 <iwamatsu___> I am reviewing 5.10.110
13:11:32 <pave1> masami: Yes, vulnerabilities did not look too bad. We probably don't care about hamradio, for example.
13:12:08 <masami> pavel: I see. thanks.
13:12:17 <iwamatsu___> And we released 4.4.y-cip with first self maintain 4.4.y tree.
13:12:26 <pave1> Thank you!
13:13:00 <masami> congratulations!
13:13:06 <pave1> I'll need to take a closer look.
13:13:22 <iwamatsu___> ;-)
13:13:35 <pave1> Anything else?
13:13:38 <pave1> 3
13:13:40 <pave1> 2
13:13:44 <pave1> 1
13:13:53 <pave1> #topic Kernel testing
13:14:28 <patersonc[m]> linux-stable-rc repo has got too big for gitlab
13:14:55 <alicef> rt preemtrt test got merged on kernelci
13:14:56 <patersonc[m]> I've deleted all the branches & tags we don't follow, hopefully that will get mirroring working again
13:15:23 <pave1> That's bad, I assume. I wonder how they account that, I'm sure we are not only ones mirroring -stable-rc.
13:16:28 <alicef> added CIP to rt preemt-rt test on kernelci
13:16:43 <pave1> But 5.10 tree is still at 5.10.110-rc1. -rc2 was not mirrored :-(.
13:17:17 <alicef> still only working on x86-64
13:17:27 <alicef> https://storage.staging.kernelci.org/cip/linux-5.10.y-cip-rt/v5.10.104-cip3-rt3/x86_64/x86_64_defconfig%2Bx86-chromebook%2Bpreempt_rt/gcc-10/
13:17:47 <alicef> https://staging.kernelci.org/test/job/cip/branch/linux-5.10.y-cip-rt/kernel/v5.10.104-cip3-rt3/plan/preempt-rt/
13:18:12 <alicef> https://staging.kernelci.org/test/plan/id/6246b8ade748c32a8b05f4c4/
13:18:44 <alicef> is getting preempt-rt measure for each cip rt branch
13:20:25 <pave1> Ok, 90us looks reasonable. One way to verify the testing would be to submit config with PREEMPT_RT disabled... to make sure it fails.
13:21:32 <alicef> also all the pr of the CIP device request I sendede to kernelCI for adding it on kernelCI got closed for problems on the device or device not available
13:21:54 <alicef> would be nice if someone can look into it and reopen such pull request on necessity
13:23:24 <pave1> I don't know nearly enough about kernelCI  to do that :-(.
13:23:29 <alicef> https://github.com/kernelci/kernelci-core/pulls?q=is%3Apr+is%3Aclosed+label%3Acip+%22test-configs.yaml%3A+Add+CIP+device%22
13:23:46 <alicef> patersonc[m]: could you give a look on this ?
13:24:41 <patersonc[m]> Yea
13:24:51 <pave1> Thank you!
13:24:53 <alicef> thanks
13:24:56 <pave1> Anything else?
13:25:02 <pave1> 3
13:25:05 <pave1> 2
13:25:08 <pave1> 1
13:25:19 <pave1> #topic AOB
13:26:08 <pave1> I'd not mind shifting weekly meeting to 12 UTC or even earlier.
13:26:24 <alicef> DST ?
13:26:37 <alicef> no problem here either
13:26:42 <uli> earlier is not so good for me. 12 is ok, though.
13:26:56 <pave1> Yes, basically so it stays at the same local time.
13:27:29 <pave1> jki?
13:27:44 <patersonc[m]> pave1: Where are you based?
13:27:54 <pave1> Europe/Prague time zone.
13:28:46 <iwamatsu___> JST is 21:00. it is good to me.
13:28:50 <jki> pavel: move during DST only, or move always (i.e. one hour earlier than before during normal time)?
13:29:30 <pave1> jki: For me, "move always" is best option, but "move during DST only" is still better than current situation.
13:30:14 <jki> how is the situation for US when we move earlier?
13:33:35 <pave1> Current invite says "USWest 6am, USEast 9am". Do we have someone in west of USA?
13:38:13 <pave1> Umm. Will we decide over email or doodle poll or something?
13:38:44 <pave1> 5
13:38:50 <jki> maybe best
13:39:10 <pave1> I don't know how to operate doodle, but perhaps that's best option?
13:39:35 <pave1> 5
13:39:41 <pave1> 4
13:39:44 <pave1> 3
13:39:47 <pave1> 2
13:39:48 <pave1> 1
13:39:57 <pave1> #endmeeting