13:03:34 <jki> #startmeeting CIP IRC weekly meeting
13:03:34 <collab-meetbot`> Meeting started Thu Jan  9 13:03:34 2025 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:03:34 <collab-meetbot`> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:03:34 <collab-meetbot`> The meeting name has been set to 'cip_irc_weekly_meeting'
13:03:40 <jki> #topic AI review
13:03:45 <jki> - prepare blog entry on SLTS kernel state and challenges [Jan]
13:04:11 <jki> basically done, will trigger the publication soon
13:04:38 <jki> were there other AIs in the past weeks?
13:05:07 <jki> 5
13:05:09 <jki> 4
13:05:11 <jki> 3
13:05:13 <jki> 2
13:05:15 <jki> 1
13:05:17 <jki> #topic Kernel maintenance updates
13:05:38 <masami> This week reported 32 new CVEs and 5 updated CVEs.
13:05:55 <uli_> no updates from me
13:06:10 <pave1> I was reviewing 6.1.123 and .124
13:06:51 <iwamatsu__> I did not review this week.
13:07:41 <jki> anything else?
13:08:15 <jki> 5
13:08:15 <jki> 4
13:08:15 <jki> 3
13:08:15 <jki> 2
13:08:15 <jki> 1
13:08:15 <jki> #topic Kernel release status
13:08:32 <jki> 4.19 is late
13:09:54 <jki> would be our first own release, right? any blockers?
13:09:56 <iwamatsu__> We need to decide how often to update 4.19 and change the script.
13:10:07 <pave1> That's where the self-mainainance fun starts.
13:10:42 <jki> 4.19 is once per month already
13:10:48 <jki> just like 4.4
13:11:12 <iwamatsu__> aha, OK
13:11:12 <pave1> I believe we should do full release based on last 4.19 and then start preparing next one.
13:11:19 <jki> what did we do for 4.4 back then?
13:14:07 <jki> and roles will remain the same for 4.19?
13:14:52 <iwamatsu__> We checked the patches to be included in 4.9 and applied the necessary patches. 4.19 should do the same.
13:15:36 <pave1> Dunno. I guess that depends if Iwamatsu-san has enough time for that?
13:16:51 <iwamatsu__> Just as Uli is in charge of 4.4, it may be necessary to assign 4.19 as well...
13:17:08 <uli_> i wonder how much synergy there is between 4.4 and 4.19
13:17:20 <uli_> i suppose 4.19 will act as a filter for the patch torrent from stable
13:17:28 <iwamatsu__> Hmmm, I will have to check with my boss (Yoshi).
13:17:51 <pave1> uli: yes. 4.4 should be easier to maintain from that point.
13:18:02 <jki> please clarify, ideally before next TSC so that we can report or start discussing alternatives
13:18:07 <uli_> i have the process of ingesting stable patches dialed in, i wouldn't mind taking on 4.19.
13:18:22 <pave1> uli: if it does not apply to 4.19 and is not critical, it will be filtered out.
13:18:43 <pave1> I can also help.
13:19:23 <iwamatsu__> Me too.
13:20:16 <jki> ok, then the next 4.19 will be from uli
13:20:27 <uli_> maybe iwamatsu__ can do the last 4.19 release, following the existing process
13:20:31 <uli_> then i'll take over
13:21:08 <pave1> I guess that would be better.
13:21:42 <jki> iwamatsu__: fine for you as well?
13:22:51 <iwamatsu__> OK, I will release -cip with 4.19.325.
13:23:10 <uli_> thank you!
13:23:32 <jki> perfect, thanks!
13:24:10 <jki> then let's move on
13:24:11 <jki> 5
13:24:14 <jki> 4
13:24:15 <jki> 3
13:24:17 <jki> 2
13:24:19 <jki> 1
13:24:21 <jki> #topic Kernel testing
13:24:47 <arisut> Currently adding a experimental option to kci-dev, `kci-dev results`
13:25:15 <arisut> `kci-dev results` is able to check informations from the current folder and if we are into a git repository, like linux-cip, and give in formations about the current status on KernelCI
13:26:24 <arisut> give informations about the current status on KernelCI of a linux repository folder
13:26:24 <arisut> like on this examples https://gist.github.com/aliceinwire/c00388a318b84ce5fe4ba595623ccc5e
13:26:40 <jki> btw, are our maintainers using kci-dev already?
13:27:53 <arisut> I know internally KernelCI is using kci-dev daily
13:29:09 <pave1> Not yet, but its on my todo list.
13:29:09 <arisut> not sure if some maintainer started already to use kci-dev, I know some maintainer is interested on kci-dev but I don't have yet detailed information about usage
13:30:00 <arisut> on new year kci-dev 0.1.1 as been released
13:30:36 <arisut> https://pypi.org/project/kci-dev/
13:30:46 <arisut> that is the first "stable" release
13:31:24 <arisut> but the getting results directory from the git repository folder is still in development and I hope it will get in the next release
13:31:52 <arisut> s/directory/directly/
13:32:54 <arisut> documentation is here https://docs.kernelci.org/kci-dev/
13:33:57 <jki> was just a reminder to us to check it out as well :)
13:34:16 <arisut> yes would be nice to get some feedback
13:34:43 <arisut> also from CIP
13:35:59 <arisut> any question?
13:36:56 <arisut> if there are no question I have another topic today
13:37:47 <jki> I would have an unrelated problem report:
13:37:52 <jki> "requests.exceptions.HTTPError: 502 Server Error: Bad Gateway for url: https://api.kernelci.org/upload"
13:37:57 <jki> https://gitlab.com/cip-project/cip-core/isar-cip-core/-/jobs/8807718502
13:38:11 <jki> anyone any ideas? kernelci hick-up?
13:38:26 <arisut> jki, yes
13:38:28 <arisut> I was just talking today with denys about that problem
13:38:53 <arisut> KernelCI is changing the storage api but the new api are still in progress
13:39:13 <arisut> will fix when we have the new storage api
13:39:35 <jki> is that going to happen in the next days, likely?
13:40:19 <jki> pipeline is red now, and that comes with the risk of papering over real issues
13:40:39 <arisut> I think it will take some week, we are in the process of deprecating legacy and making the new api
13:41:14 <jki> then we should probably disable the futile deployment attempts for now
13:41:17 <jki> will write a patch
13:41:21 <arisut> ok
13:41:45 <arisut> my other topic is about lava-docker.
13:42:06 <arisut> anyone using lava-docker?
13:42:30 <arisut> lava-docker as been recently moved to baylibre
13:43:09 <jki> I was just recommending it internally as quick-start tool
13:43:09 <jki> what does that mean for it?
13:44:04 <arisut> As been just moved, and I'm not aware of the maintaining process of baylibre
13:44:52 <arisut> montjoie, the creator and co-maintainer will keep maintaining lava-docker
13:45:10 <arisut> on the baylibre github account
13:45:49 <arisut> but I don't have any more detail on this topic
13:46:20 <jki> will the URL change or be forwarded?
13:46:42 <jki> I think we have a reference in some project to the original repo
13:46:51 <arisut> the idea was at first that lava gitlab organization would take lava-docker
13:47:00 <arisut> https://docs.kernelci.org/org/maintainers/#lava-docker-interim
13:48:21 <jki> hmm, it comes from github, that prevents easy forwarding
13:48:33 <jki> anyway, we will see
13:48:37 <jki> thanks for the heads-up
13:48:42 <arisut> but now is on baylibre that is on github
13:48:44 <arisut> https://github.com/BayLibre/lava-docker
13:49:05 <arisut> not sure what have happened since that email
13:49:40 <jki> and it is here: https://github.com/kernelci/lava-docker
13:49:45 <jki> confusing
13:49:57 <arisut> yes
13:50:03 <jki> hope they will sort that out properly
13:50:12 <arisut> hope too
13:51:11 <jki> ok, other testing topics?
13:51:13 <arisut> no that was the last one from me
13:51:26 <jki> good - anyone else?
13:52:05 <jki> 5
13:52:07 <jki> 4
13:52:09 <jki> 3
13:52:10 <jki> 2
13:52:12 <jki> 1
13:52:14 <jki> #topic AOB
13:52:57 <jki> anything else for today?
13:53:29 <jki> 5
13:53:31 <jki> 4
13:53:33 <jki> 3
13:53:35 <jki> 2
13:53:37 <jki> 1
13:53:41 <jki> #endmeeting