13:02:30 <jki> #startmeeting CIP IRC weekly meeting
13:02:30 <collab-meetbot`> Meeting started Thu Feb 15 13:02:30 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:30 <collab-meetbot`> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:02:30 <collab-meetbot`> The meeting name has been set to 'cip_irc_weekly_meeting'
13:02:38 <jki> #topic AI review
13:02:47 <jki> - prepare blog entry on SLTS kernel state and challenges [Jan]
13:02:48 <pave1> hi!
13:03:07 <jki> started, but still some way - will request feedback when ready
13:03:14 <jki> other AIs?
13:03:39 <jki> 3
13:03:40 <jki> 2
13:03:42 <jki> 1
13:03:44 <jki> #topic Kernel maintenance updates
13:04:07 <masami> This week reported 7 new CVEs and 2 updated CVEs.
13:04:09 <uli> i'm still reviewing 6.1.75
13:04:15 <pave1> I was reviewing 6.1.77 and .78
13:05:04 <iwamatsu> I reviewed 6.1.77, and preparating release 4.19.y-cip tree
13:06:44 <jki> anything else?
13:07:01 <jki> 5
13:07:03 <jki> 4
13:07:05 <jki> 3
13:07:06 <jki> 2
13:07:08 <jki> 1
13:07:11 <jki> #topic Kernel release status
13:07:29 <jki> so, just 4.19-cip is delayed, but under preparation, right?
13:07:44 <iwamatsu> yes
13:08:12 <jki> ok, then we could already move on...
13:08:19 <jki> 5
13:08:20 <jki> 4
13:08:22 <jki> 3
13:08:23 <jki> 2
13:08:24 <jki> 1
13:08:26 <jki> #topic Kernel testing
13:09:56 <jki> nothing?
13:09:57 <pave1> From the last meetin -- could we stop broadcasting testing emails
13:09:59 <arisut> I look into the kernelci api and pratically for working is getting a yaml file like in the example: https://github.com/kernelci/kernelci-pipeline/blob/e79e3743c2caeb106b99e7eaabd5904d0bca950f/config/pipeline.yaml#L200
13:11:25 <arisut> the way is working is same to the current kernelci configuration but I couldn't reproduce anything useful yet
13:11:33 <jki> pavel: as chris is not here, we will have to reschedule this topic again
13:11:42 <arisut> I got the staging acctount today and will try with that
13:12:32 <jki> arisut: what was the goal again? sorry, forgot about that
13:13:30 <arisut> see if we can use kernelci api for requesting new build directly from the api with a cip account
13:13:46 <jki> ah, ok
13:14:23 <arisut> and see what we can do with the new kernelci core api as is yet on development
13:15:09 <arisut> so that we can maybe send request for making it better
13:15:46 <arisut> but my task is just see if we can use it and see what we can do with it
13:16:56 <jki> great, I'm sure they will like to hear early feedback as well!
13:17:38 <arisut> so if someone else want to try it feel free to send a account request on github
13:17:47 <jki> I've chatted these days with Daniel W. about kernelci and -rt testing
13:17:52 <arisut> https://kernelci.org/docs/api/early-access/
13:18:03 <jki> there is still not much, as I've noticed (again)
13:18:19 <jki> but two improvements are insight:
13:18:33 <jki> - he wants to enable more rt-tests soon
13:18:34 <arisut> feel free to open issues on the github
13:18:39 <arisut> about that
13:19:11 <jki> - kernelci is working on UX improvements that should once allow to show trends in measurements
13:19:45 <jki> https://kernelci.org/blog/posts/2023/ux-analysis/
13:20:32 <jki> once we can collect those, it will also be important to improve the background stress for -rt
13:20:38 <jki> it's just hackbench...
13:21:06 <jki> what are we doing in the CIP labs?
13:24:32 <jki> probably only chris knows ;)
13:24:47 <jki> ok - anything else on testing?
13:25:53 <jki> 5
13:25:55 <jki> 4
13:25:56 <jki> 3
13:25:58 <jki> 2
13:26:00 <jki> 1
13:26:05 <jki> #topic AOB
13:26:26 <jki> kernel is now CNA, more CVE assignments to come - any impact for us expected?
13:27:00 <jki> I mean on workflows and daily business
13:27:34 <masami> I think it doesn't change our workflow.
13:28:14 <pave1> I don't think so.
13:28:30 <pave1> I mean -- I don't expect impact.
13:28:36 <jki> good - was my expectation as well
13:29:01 <jki> the fuzz will be elsewhere - popcorn time, as lwn.net wrote
13:30:57 <jki> found our -rt test case by now: https://gitlab.com/cip-project/cip-testing/linux-cip-ci/-/blob/master/lava_templates/test_cyclictest+hackbench.yaml
13:31:06 <jki> not that different from kernelci
13:31:41 <jki> anyway, we arent't alone here
13:31:49 <jki> any other business for today?
13:32:40 <jki> 5
13:32:42 <jki> 4
13:32:44 <jki> 3
13:32:45 <jki> 2
13:32:47 <jki> 1
13:32:49 <jki> #endmeeting