13:02:32 <jki> #startmeeting CIP IRC weekly meeting
13:02:32 <collab-meetbot`> Meeting started Thu Feb 22 13:02:32 2024 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:02:32 <collab-meetbot`> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:02:32 <collab-meetbot`> The meeting name has been set to 'cip_irc_weekly_meeting'
13:02:40 <jki> #topic AI review
13:02:46 <jki> - prepare blog entry on SLTS kernel state and challenges [Jan]
13:03:00 <jki> not yet happy, in a rewrite...
13:03:09 <jki> other AIs?
13:03:27 <jki> 3
13:03:29 <jki> 2
13:03:30 <jki> 1
13:03:32 <jki> #topic Kernel maintenance updates
13:03:38 <pave1> I was reviewing 6.1.78 and .79.
13:03:48 <uli> done with 6.1.75, doing 4.4 next
13:03:48 <masami> This week reported 15 new CVEs and 2 updated CVEs.
13:04:37 <iwamatsu> I reviewed 6.1.78, and I am preparating 6.1.y-cip release
13:06:16 <jki> other topics here?
13:06:46 <jki> 5
13:06:48 <jki> 4
13:06:50 <jki> 3
13:06:51 <jki> 2
13:06:53 <jki> 1
13:06:56 <jki> #topic Kernel release status
13:07:06 <jki> so, only 6.1 is currently late
13:07:13 <jki> any blockers for it?
13:07:21 <iwamatsu> Yes, I am working it now.
13:07:46 <iwamatsu> no blockers
13:07:51 <jki> good
13:08:00 <jki> any other issues upcoming?
13:08:28 <jki> 5
13:08:29 <jki> 4
13:08:31 <jki> 3
13:08:33 <jki> 2
13:08:34 <jki> 1
13:08:37 <jki> #topic Kernel testing
13:09:03 <patersonc> Hello
13:09:10 <patersonc> Sorry I was away last week
13:09:29 <arisut> sorry no updates this week from me
13:09:39 <patersonc> There was some discussion on stopping kernelci emails going to cip-dev - I've actioned this now: https://github.com/kernelci/kernelci-jenkins/pull/138
13:09:51 <patersonc> Should come into effect on Monday
13:10:03 <patersonc> They will go to the test-results ML instead
13:10:10 <arisut> still need to investigate the yaml files used by kernelci core api
13:10:30 <patersonc> Thanks arisut
13:11:05 <arisut> patersonc: thanks
13:11:09 <patersonc> jki - some boards have been failing health-checks in the muc lab for a bit - could you get someone to take a look for me?
13:11:29 <patersonc> https://lava.ciplatform.org/scheduler/worker/lab-cip-siemens-muc
13:11:45 <jki> sure, will check
13:11:50 <patersonc> Thanks
13:12:16 <patersonc> Is the CIP release test report email still working okay for everyone?
13:12:55 <uli> works for me
13:13:48 <patersonc> If anyone wants to report the same on a build before the "release" email goes out, let me know. It would be nicer to have it as part of the actual release process
13:14:33 <jki> what is practically needed to move the report earlier?
13:15:25 <patersonc> All I'm doing is looking at the squad gui. I guess it takes an hour or so from push to kernel.org/gitlab to get results onto squad?
13:15:38 <patersonc> Maybe more than an hour - I'm not sure tbh
13:15:47 <pave1> It requires more coordination.
13:16:00 <jki> so, you would need a ping from a maintainer ready to release
13:16:50 <patersonc> Yea
13:16:54 <pave1> Best option from my side would be -- we mail qa team,
13:17:25 <pave1> qa team does the final announce when no problems are detected.
13:18:18 <patersonc> Or, go to the squad dashboard, click on the build with the sha you're releasing, if there are no issues, release.
13:18:36 <patersonc> e.g. https://squad.ciplatform.org/linux-cip/linux-4.19.y-cip/build/4.19.306-cip107_800dfc28d/ shows no test failures
13:18:40 <jki> https://lava.ciplatform.org/scheduler/worker/lab-cip-siemens-muc should be fine again - power control hick-up
13:18:50 <patersonc> Thanks jki
13:19:09 <jki> Quirin did it :)
13:19:25 <pave1> Well -- if squad now works well enough, we can do it.
13:19:51 <pave1> What about -- keep the same system for now
13:20:12 <pave1> and we evaluate squad in next few weeks?
13:20:18 <jki> or do one pilot, but maybe not with a late release ;)
13:20:58 <patersonc> either, or, I don't mind :)
13:21:51 <jki> what would "we evaluate" concretely mean? who would do what?
13:22:22 <pave1> next time i do releade I look at squad, and if I
13:22:42 <pave1> can understand it, we do the switch
13:23:16 <arisut> switch from what?
13:23:42 <pave1> Switch fromcurrent system where qa
13:24:06 <pave1> team reports results over email after release.
13:24:10 <arisut> curren system you are referring to is the patersonc mail review?
13:24:21 <pave1> yep.
13:24:56 <arisut> so if I understand correctly if you can work with squad, review mail are no needed anymore?
13:25:42 <jki> point is that all maintainer should check that for themselves before we do a general decision
13:25:49 <pave1> if the squad can do clear yes/no decision, we can do that.
13:27:01 <patersonc> Okay
13:27:28 <patersonc> Let's see how it goes. Just shout if there are any uncertancies/issues
13:27:37 <pave1> Ok.
13:27:59 <iwamatsu> OK
13:28:08 <pave1> In last meetings we talked about lot of testing
13:28:23 <pave1> mails on cip-dev.
13:28:36 <pave1> Can we turn them off?
13:28:56 <arisut> patersonc: currently squad is also getting kernelci information? or just discarding it?
13:29:31 <patersonc> arisut: Currently the kernelCI testing isn't feeding back into SQUAD, it's a TODO to work that out
13:30:16 <patersonc> pave1: As I said earlier, there's already an MR merged to stop the kernelCI emails going to cip-dev - they will move to the cip-testing-results ML
13:30:45 <pave1> aha, ok, thanks.
13:31:22 <jki> good - further testing topics?
13:31:37 <jki> did you see Daniels -rt kernelci improvements?
13:31:50 <patersonc> Nope
13:32:17 <jki> https://github.com/kernelci/kernelci-core/pull/2397
13:32:22 <jki> add you do CC ;)
13:32:33 <patersonc> oh yes, sorry
13:34:11 <jki> please provide further feedback if you have any - is that helpful? is more is needed?
13:34:23 <patersonc> Will do
13:34:24 <patersonc> Thanks
13:34:33 <jki> pavel: also addressing you
13:34:38 <jki> good
13:35:04 <pave1> I'll take a look at the github link.
13:35:23 <jki> other testing topics?
13:36:14 <jki> 5
13:36:15 <jki> 4
13:36:17 <jki> 3
13:36:18 <jki> 2
13:36:20 <jki> 1
13:36:22 <jki> #topic AOB
13:37:42 <jki> anything else for today?
13:38:04 <jki> 5
13:38:06 <jki> 4
13:38:07 <jki> 3
13:38:09 <jki> 2
13:38:10 <jki> 1
13:38:12 <jki> #endmeeting