13:00:22 #startmeeting CIP IRC weekly meeting 13:00:22 Meeting started Thu Dec 16 13:00:22 2021 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:22 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:00:22 The meeting name has been set to 'cip_irc_weekly_meeting' 13:00:27 hi everyone! 13:00:42 hello 13:00:45 hi 13:00:48 hi 13:01:05 hi 13:02:09 o/ 13:03:26 ok, let's get started 13:03:29 #topic AI review 13:03:38 1. Combine root filesystem with kselftest binary (finishing) - alicef 13:04:18 I had the presentation the other day, I'm starting now to send update 13:04:34 perfect! 13:04:37 jki: can I send you some question by email, if I have any ? 13:04:44 sure! 13:04:49 ok 13:05:01 2. Propose tweet on KernelCI-CIP collaboration progress - alicef 13:05:16 skip 13:05:25 still working on this 13:05:28 3. Clarify with KernelCI whether CIP maintainers can get accounts - alicef 13:05:42 (all AI's are yours today, alicef ;) 13:05:44 I pinged TSC for this. 13:06:17 we are still deciding how to give you permission. 13:06:47 but our use case is considered valid? 13:07:01 yes 13:08:02 ok, then let's wait for an answer 13:08:19 anything else AI-related? 13:08:26 one of the idea is to have some dev tree that are considered stable-rc branches with changes that are considered not stable yet. and test for each change with a branch something like for-kernelci 13:08:50 and with specified labs and board where will be tested 13:09:17 looks like this can be done on kernelci-core code directly without any account 13:09:36 but this is still a open discussion with kernelci 13:10:09 iwamatsu: would be enough to have a branch that is tested for anychange by kernelci ? 13:10:21 something like for-kernelci 13:10:35 he's not online today 13:10:42 ah 13:10:55 anyway is still a dicussion topic 13:11:10 I will come back when we have a more clear answer 13:11:20 ok, good 13:11:43 for-kernelci branch is good start, yes 13:13:15 and that for-kernelci branch will be build on only lab-cip so that it will take less time 13:13:56 also everything will be build on the azure high spec machine that kernelci is using 13:14:35 nice 13:15:43 anything else on this? 13:16:00 no for me, is still a working on 13:16:14 ok, then move on 13:16:19 #topic Kernel maintenance updates 13:16:44 reviewing 5.10.86 13:16:51 This week reported ten new CVEs and two of them aren't fixed in the mainline yet. 13:17:03 iwamatsu-san backported a patch for CVE-2021-39648 to stable/4.4. 13:17:09 I have reviewed 5.10.85 13:18:33 how is the work-split organization working by now? 13:18:46 also /wrt those incoming backports 13:19:56 iwamatsu-san wrote he'd have something by tomorrow, iirc 13:20:20 ah, ok 13:21:42 then let's check this in the next meeting 13:21:47 anything else here? 13:22:28 3 13:22:29 2 13:22:30 1 13:22:32 #topic Kernel testing 13:22:53 I'm not sure I have any updates this week 13:23:20 I made a presentation about CIP testing integration with KernelCI if you are interested 13:23:48 at Open Source Summit Japan 2021 13:24:05 will be shared in around 1 month on youtube 13:24:16 slides already online? 13:24:27 nice 13:24:32 let me see 13:24:52 https://ossalsjp21.sched.com/event/pedu/merging-an-existing-framework-into-kernelci-alice-ferrazzi-miracle-linux-powered-by-cybertrust-japan-co-ltd?iframe=no 13:25:09 you could be able to download from here 13:25:15 you should 13:25:50 yep 13:26:41 how was the feedback? 13:27:46 we had not much feedback this year but there was around 60 people listening 13:28:45 now I'm preparing for Linux conf au 2022 that is in january 13:29:13 follow-up on this talk or a different topic? 13:29:32 follow-up on this topic 13:31:30 ok - that's all for testing, I assume 13:31:47 from me yes 13:32:01 yep 13:32:08 good, then move on 13:32:19 #topic AOB 13:32:31 vacations... :) 13:32:56 ...and lockdowns :-). 13:33:13 not compatible as we know ;) 13:33:22 I'm OOO the next two weeks 13:34:09 well, strictly spoken, Jan 6 is public holiday here as well 13:34:26 but I can run that one again 13:34:51 how about next week? anyone interested to host this? 13:35:11 Chris knows how to operate the bot :-). 13:35:26 :) 13:35:42 I'll be out for the next two thursdays but will be back by the 6th 13:36:01 I can run the next one, I guess. 13:36:13 I suggest to skip the one on Dec 30th. 13:36:16 I'm also able to operate the bot, I think 13:36:29 You got the job! :-) 13:37:16 pave1: lol 13:37:57 we actually want to run next the Agenda next week? 13:39:12 Our holidays normally start at 24th afternoon, so I assumed so. 13:39:25 But it does not make sense if noone has time. 13:39:54 I can test if the bot listen to my command? 13:40:12 you could close the meeting today 13:40:29 oh right is not closed yet 13:40:36 just write "#endmeeting" 13:40:47 I guess we want to decide which meetings we want before closing it. 13:40:50 but I think closing is reserved only for the meeting chair 13:40:51 So it ends up in the log. 13:41:00 current meeting chair 13:41:14 bot will react or not - give it a try later on 13:41:21 ok 13:41:46 anyway - no meeting on the 30th, did we settle on that already? 13:41:49 pave1: I agree 13:41:58 jki: yep 13:42:08 and next week, alicef will run the show 13:42:36 And 6th, jki is back. Looks good to me. 13:42:44 yep 13:42:45 #startvote having a meeting on the 30th? 13:42:45 Only the meeting chair may start a vote. 13:43:11 alicef: you were right, you aren't the chair... 13:43:28 #startvote having a meeting on the 30th? 13:43:28 Begin voting on: having a meeting on the 30th? Valid vote options are Yes, No. 13:43:28 Vote using '#vote OPTION'. Only your last vote counts. 13:43:34 jki: that is because the chair got selected at start 13:43:58 #vote No 13:43:59 #vote no 13:44:00 #vote no 13:44:05 #vote no 13:44:06 #vote no 13:44:12 #vote no 13:44:29 #endvote 13:44:29 Voted on "having a meeting on the 30th?" Results are 13:44:43 where are the results? 13:44:49 results are ??? lol 13:44:54 anyway, we have them above :) 13:44:55 :D 13:45:00 a mistery 13:45:13 e-elections... 13:45:28 ok, then let's close for today 13:45:41 3 13:45:42 2 13:45:44 1 13:45:47 #endmeeting