IRC logs for #cip for Thursday, 2021-12-16

« Wednesday, 2021-12-15 Index Friday, 2021-12-17 »
*** alicef <alicef!~none@gentoo/developer/alicef> has quit IRC00:00
*** iwamatsu <iwamatsu!~iwamatsu@www1015ue.sakura.ne.jp> has quit IRC00:00
*** helmut <helmut!helmut@subdivi.de> has quit IRC00:00
*** brlogger <brlogger!~supybot@45.114.123.168> has joined #cip00:02
*** ChanServ sets mode: +o brlogger00:02
*** alicef <alicef!~none@gentoo/developer/alicef> has joined #cip00:03
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip03:13
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip06:56
*** alicef_ <alicef_!~none@gentoo/developer/alicef> has joined #cip08:47
*** alicef <alicef!~none@gentoo/developer/alicef> has quit IRC08:48
*** alicef_ <alicef_!~none@gentoo/developer/alicef> has quit IRC09:06
*** alicef <alicef!~none@gentoo/developer/alicef> has joined #cip09:08
*** alicef <alicef!~none@gentoo/developer/alicef> has quit IRC09:13
*** alicef <alicef!~none@gentoo/developer/alicef> has joined #cip09:42
*** alicef <alicef!~none@gentoo/developer/alicef> has quit IRC09:54
*** alicef <alicef!~none@gentoo/developer/alicef> has joined #cip09:59
*** alicef <alicef!~none@gentoo/developer/alicef> has quit IRC10:00
*** alicef <alicef!~none@gentoo/developer/alicef> has joined #cip10:01
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC11:04
*** uli <uli!~uli@55d405d2.access.ecotel.net> has joined #cip11:24
*** masami <masami!~masami@FL1-110-233-204-67.tky.mesh.ad.jp> has joined #cip12:15
*** jki <jki!~jki@165.225.27.25> has joined #cip12:47
jki#startmeeting CIP IRC weekly meeting13:00
brloggerMeeting 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
brloggerUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
brloggerThe meeting name has been set to 'cip_irc_weekly_meeting'13:00
*** brlogger changes topic to " (Meeting topic: CIP IRC weekly meeting)"13:00
*** alicefm <alicefm!~alicefm@user/alicefm> has joined #cip13:00
jkihi everyone!13:00
*** pav31 <pav31!~mobian@78-80-25-253.customers.tmcz.cz> has joined #cip13:00
ulihello13:00
masamihi13:00
pav31hi13:00
patersonc[m]hi13:01
alicefo/13:02
*** josiah <josiah!~kvirc@pool-100-16-211-90.bltmmd.fios.verizon.net> has joined #cip13:02
jkiok, let's get started13:03
jki#topic AI review13:03
*** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:03
jki1. Combine root filesystem with kselftest binary (finishing) - alicef13:03
alicefI had the presentation the other day, I'm starting now to send update13:04
jkiperfect!13:04
alicefjki: can I send you some question by email, if I have any ?13:04
jkisure!13:04
alicefok13:04
jki2. Propose tweet on KernelCI-CIP collaboration progress - alicef13:05
alicefskip13:05
alicefstill working on this13:05
jki3. Clarify with KernelCI whether CIP maintainers can get accounts - alicef13:05
jki(all AI's are yours today, alicef ;)13:05
alicefI pinged TSC for this.13:05
alicefwe are still deciding how to give you permission.13:06
jkibut our use case is considered valid?13:06
alicefyes13:07
jkiok, then let's wait for an answer13:08
jkianything else AI-related?13:08
alicefone 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-kernelci13:08
alicefand with specified labs and board where will be tested13:08
aliceflooks like this can be done on kernelci-core code directly without any account13:09
alicefbut this is still a open discussion with kernelci13:09
alicefiwamatsu: would be enough to have a branch that is tested for anychange by kernelci ?13:10
alicefsomething like for-kernelci13:10
jkihe's not online today13:10
alicefah13:10
alicefanyway is still a dicussion topic13:10
alicefI will come back when we have a more clear answer13:11
jkiok, good13:11
pav31for-kernelci branch is good start, yes13:11
alicefand that for-kernelci branch will be build on only lab-cip so that it will take less time13:13
alicefalso everything will be build on the azure high spec machine that kernelci is using13:13
jkinice13:14
*** toscalix <toscalix!~toscalix@245.red-80-29-66.staticip.rima-tde.net> has joined #cip13:15
jkianything else on this?13:15
alicefno for me, is still a working on13:16
jkiok, then move on13:16
jki#topic Kernel maintenance updates13:16
*** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:16
ulireviewing 5.10.8613:16
masamiThis week reported ten new CVEs and two of them aren't fixed in the mainline yet.13:16
masamiiwamatsu-san backported a patch for CVE-2021-39648 to stable/4.4.13:17
pav31I have reviewed 5.10.8513:17
jkihow is the work-split organization working by now?13:18
jkialso /wrt those incoming backports13:18
uliiwamatsu-san wrote he'd have something by tomorrow, iirc13:19
jkiah, ok13:20
jkithen let's check this in the next meeting13:21
jkianything else here?13:21
jki313:22
jki213:22
jki113:22
jki#topic Kernel testing13:22
*** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:22
patersonc[m]  I'm not sure I have any updates this week13:22
alicefI made a presentation about CIP testing integration with KernelCI if you are interested13:23
alicefat Open Source Summit Japan 202113:23
alicefwill be shared in around 1 month on youtube13:24
jkislides already online?13:24
jkinice13:24
aliceflet me see13:24
alicefhttps://ossalsjp21.sched.com/event/pedu/merging-an-existing-framework-into-kernelci-alice-ferrazzi-miracle-linux-powered-by-cybertrust-japan-co-ltd?iframe=no13:24
alicefyou could be able to download from here13:25
alicefyou should13:25
jkiyep13:25
jkihow was the feedback?13:26
alicefwe had not much feedback this year but there was around 60 people listening13:27
alicefnow I'm preparing for Linux conf au 2022 that is in january13:28
*** pave1 <pave1!~pavel@88.103.226.45> has joined #cip13:28
jkifollow-up on this talk or a different topic?13:29
aliceffollow-up on this topic13:29
*** pav31 <pav31!~mobian@78-80-25-253.customers.tmcz.cz> has quit IRC13:30
jkiok - that's all for testing, I assume13:31
aliceffrom me yes13:31
patersonc[m]yep13:32
jkigood, then move on13:32
jki#topic AOB13:32
*** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:32
jkivacations... :)13:32
pave1...and lockdowns :-).13:32
jkinot compatible as we know ;)13:33
jkiI'm OOO the next two weeks13:33
jkiwell, strictly spoken, Jan 6 is public holiday here as well13:34
jkibut I can run that one again13:34
jkihow about next week? anyone interested to host this?13:34
pave1Chris knows how to operate the bot :-).13:35
patersonc[m]:)13:35
patersonc[m]I'll be out for the next two thursdays but will be back by the 6th13:35
pave1I can run the next one, I guess.13:36
pave1I suggest to skip the one on Dec 30th.13:36
alicefI'm also able to operate the bot, I think13:36
pave1You got the job! :-)13:36
alicefpave1: lol13:37
alicefwe actually want to run next the Agenda next week?13:37
pave1Our holidays normally start at 24th afternoon, so I assumed so.13:39
pave1But it does not make sense if noone has time.13:39
alicefI can test if the bot listen to my command?13:39
jkiyou could close the meeting today13:40
alicefoh right is not closed yet13:40
jkijust write "#endmeeting"13:40
pave1I guess we want to decide which meetings we want before closing it.13:40
alicefbut I think closing is reserved only for the meeting chair13:40
pave1So it ends up in the log.13:40
alicefcurrent meeting chair13:41
jkibot will react or not - give it a try later on13:41
alicefok13:41
jkianyway - no meeting on the 30th, did we settle on that already?13:41
alicefpave1: I agree13:41
alicefjki: yep13:41
jkiand next week, alicef will run the show13:42
pave1And 6th, jki is back. Looks good to me.13:42
jkiyep13:42
alicef#startvote having a meeting on the 30th?13:42
brloggerOnly the meeting chair may start a vote.13:42
jkialicef: you were right, you aren't the chair...13:43
jki#startvote having a meeting on the 30th?13:43
brloggerBegin voting on: having a meeting on the 30th? Valid vote options are Yes, No.13:43
brloggerVote using '#vote OPTION'. Only your last vote counts.13:43
alicefjki: that is because the chair got selected at start13:43
uli#vote No13:43
alicef#vote no13:43
pave1#vote no13:44
masami#vote no13:44
patersonc[m]#vote no13:44
josiah#vote no13:44
jki#endvote13:44
brloggerVoted on "having a meeting on the 30th?" Results are13:44
jkiwhere are the results?13:44
alicefresults are ??? lol13:44
jkianyway, we have them above :)13:44
patersonc[m]:D13:44
alicefa mistery13:45
jkie-elections...13:45
jkiok, then let's close for today13:45
jki313:45
jki213:45
jki113:45
jki#endmeeting13:45
brloggerMeeting ended Thu Dec 16 13:45:47 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:45
brloggerMinutes:        https://irclogs.baserock.org/meetings/cip/2021/12/cip.2021-12-16-13.00.html13:45
brloggerMinutes (text): https://irclogs.baserock.org/meetings/cip/2021/12/cip.2021-12-16-13.00.txt13:45
brloggerLog:            https://irclogs.baserock.org/meetings/cip/2021/12/cip.2021-12-16-13.00.log.html13:45
*** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/"13:45
pave1Thank you.... and stay safe!13:45
alicef#startmeeting test13:46
brloggerMeeting started Thu Dec 16 13:46:11 2021 UTC and is due to finish in 60 minutes.  The chair is alicef. Information about MeetBot at http://wiki.debian.org/MeetBot.13:46
brloggerUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:46
brloggerThe meeting name has been set to 'test'13:46
*** brlogger changes topic to " (Meeting topic: test)"13:46
jkihave a nice vacation, x-mas, new year etc. and stay safe!13:46
alicef#endmeeting13:46
brloggerMeeting ended Thu Dec 16 13:46:19 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:46
brloggerMinutes:        https://irclogs.baserock.org/meetings/cip/2021/12/cip.2021-12-16-13.46.html13:46
brloggerMinutes (text): https://irclogs.baserock.org/meetings/cip/2021/12/cip.2021-12-16-13.46.txt13:46
brloggerLog:            https://irclogs.baserock.org/meetings/cip/2021/12/cip.2021-12-16-13.46.log.html13:46
*** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/"13:46
masamithank you13:46
alicefyup looks like it work13:46
pave1:-)13:46
alicefthanks you13:46
jkibye13:46
ulibye13:46
*** josiah <josiah!~kvirc@pool-100-16-211-90.bltmmd.fios.verizon.net> has quit IRC13:46
*** masami <masami!~masami@FL1-110-233-204-67.tky.mesh.ad.jp> has quit IRC13:46
pave1bye!13:46
*** pave1 <pave1!~pavel@88.103.226.45> has quit IRC13:47
*** jki <jki!~jki@165.225.27.25> has quit IRC13:47
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip14:19
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC15:58
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip16:24
*** toscalix <toscalix!~toscalix@245.red-80-29-66.staticip.rima-tde.net> has quit IRC18:17
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC19:02
*** toscalix_ <toscalix_!~agustinbe@245.red-80-29-66.staticip.rima-tde.net> has joined #cip22:06
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC22:47
« Wednesday, 2021-12-15 Index Friday, 2021-12-17 »

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!