IRC logs for #cip for Thursday, 2020-06-18

*** masashi910 has joined #cip00:12
*** toscalix has joined #cip05:33
*** toscalix has quit IRC05:40
*** rajm has joined #cip06:20
*** tpollard has joined #cip08:39
*** paveltest has joined #cip08:52
*** suzuki has joined #cip08:58
*** fujita3 has joined #cip08:59
masashi910#startmeeting CIP IRC weekly meeting09:00
brlogger`Meeting started Thu Jun 18 09:00:19 2020 UTC and is due to finish in 60 minutes.  The chair is masashi910. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
brlogger`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
brlogger`The meeting name has been set to 'cip_irc_weekly_meeting'09:00
*** brlogger` changes topic to " (Meeting topic: CIP IRC weekly meeting)"09:00
masashi910#topic rollcall09:00
*** brlogger` changes topic to "rollcall (Meeting topic: CIP IRC weekly meeting)"09:00
masashi910please say hi if you're around09:00
patersoncHello09:00
fujita3hi09:00
suzukihi09:01
paveltestHI09:01
masashi910#topic AI review09:01
*** brlogger` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"09:01
masashi9101. Combine root filesystem with kselftest binary - iwamatsu09:01
masashi910Quote from Iwamatsu-san "No update."09:01
wenshi09:01
masashi9102. Post LTP results to KernelCI - patersonc09:01
patersoncProbably won't get to this for a few weeks09:01
masashi910patersonc: OK. Do you think we can keep this AI for the time being?09:02
patersoncI don't mind. I've got it tracked elsewhere anyway09:03
masashi910patersonc: OK. Then I will keep it.09:03
masashi9103. Ask board owners to review reference platform configs to optimize backporting - masashi91009:03
masashi910I sent the following email to cip-dev. Due date is June 25th.09:03
masashi910https://lore.kernel.org/cip-dev/TY2PR01MB497253E7217AED2CA0952E47A0850@TY2PR01MB4972.jpnprd01.prod.outlook.com/09:04
masashi9104. Check CVE and Patch, Bluetooth BAIS attack (CVE-2020-10135) - iwamatsu09:04
masashi910Quote from Iwamatsu-san "No update. No update/work can be seen even in Upstream etc."09:04
masashi9105. Issues to be fixed for swupdate "copyright correction and salsa CI testing" - iwamatsu09:04
masashi910Regarding this, I didn't receive his update.09:04
masashi910any other topics?09:04
masashi910309:05
masashi910209:05
masashi910109:05
masashi910#topic Kernel maintenance updates09:05
*** brlogger` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"09:05
masashi910Quote from Iwamatsu-san "I reviewed LTS-rc. I send a comment."09:05
wensI reviewed MRs from bwh and did a round of updates for cip-kernel-sec: new CVE-2020-10773 fixed in all branches, and the three new Spectre related CVEs, CVE-2020-1076[678], are now fixed in mainline09:05
paveltestI have reviewed patches queued for 4.19.129.09:05
masashi910wens, paveltest: Thanks for your updates.09:06
masashi910any other topics?09:06
masashi910309:06
masashi910209:06
masashi910109:06
masashi910#topic Kernel testing09:06
*** brlogger` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"09:06
masashi910patersonc: the floor is yours.09:07
patersoncinfo: Started to link up KernelCI with CIP's LAVA setup. We've tested it with staging.kernelci.org and it works.09:07
patersoncinfo: This means that KernelCI can submit test jobs to the CIP reference platforms for mainline/stable Kernels etc.09:07
patersonce.g. https://staging.kernelci.org/test/job/kernelci/branch/staging.kernelci.org/kernel/staging-20200615.2/plan/baseline/09:07
patersoncHopefully it'll all be merged before ELC-NA.09:07
patersoncNext step is to look into LTP and other test integration etc.09:07
patersoncThat's about it from me this week, unless there are any queries?09:08
masashi910patersonc: Please let me clarify this.09:09
*** dineshk[m] has joined #cip09:09
masashi910I thought CIP testing team posts test results to KernelCI.09:09
patersoncThat's part of the next step09:10
masashi910But your thought is for KernelCI to submit test jobs to CIP reference platforms at first.09:10
patersoncWe need to update KCI to work with our CI setup, as the build jobs won't be triggered by KernelCI.09:10
patersoncSo there are 2 approaches. 1) KernelCI builds the kernel and submits test jobs to our LAVA labs. 2) CIP builds kernels, tests them and submit the results to KCI. I'm planning to support both methods09:11
patersoncOption 1) is easy and quick to do, so we're doing that first in time for ELC-NA09:11
patersonc2) will be done over the coming weeks (I hope)09:12
masashi910patersonc: I see. Option 1 is not using CIP kernel, but it will be a basis for the next step.09:12
masashi910patersonc: Thanks for your works!09:13
masashi910are there any other topics?09:13
masashi910or queries?09:13
patersoncYes. And the debate is still ongoing as to whether KernelCI would be willing to build/test the SLTS Kernels as part of kernelci.org or not09:13
masashi910patersonc: I see. Thanks for this clarification.09:13
masashi910any other topics or queries?09:14
masashi910309:14
masashi910209:14
masashi910109:14
masashi910#topic Software update09:14
*** brlogger` changes topic to "Software update (Meeting topic: CIP IRC weekly meeting)"09:14
suzukiHello09:14
masashi910suzuki: the floor is yours.09:14
suzukiSorry, I don't have any updates this week.09:14
suzukiI still work on the task which is to add a safe update demo to cip-sw-updates-demo repository: https://gitlab.com/cip-project/cip-sw-updates/cip-sw-updates-tasks/-/issues/409:14
suzukiThat's it from me.09:15
masashi910suzuki: Thanks for your report.09:15
masashi910are their any other topics or queries?09:15
masashi910309:15
masashi910209:15
masashi910109:15
masashi910#topic CIP Security09:15
*** brlogger` changes topic to "CIP Security (Meeting topic: CIP IRC weekly meeting)"09:15
masashi910Dinesh-san, are you going to report on behalf of Yoshida-san?09:16
masashi910Or can I skip this part?09:17
masashi910309:17
masashi910209:17
masashi910109:17
masashi910#topic AOB09:17
*** brlogger` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"09:17
masashi910Are there any business matters to discuss?09:18
masashi910309:18
masashi910209:18
masashi910109:18
masashi910#endmeeting09:18
brlogger`Meeting ended Thu Jun 18 09:18:29 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:18
brlogger`Minutes:        https://irclogs.baserock.org/meetings/cip/2020/06/cip.2020-06-18-09.00.html09:18
brlogger`Minutes (text): https://irclogs.baserock.org/meetings/cip/2020/06/cip.2020-06-18-09.00.txt09:18
brlogger`Log:            https://irclogs.baserock.org/meetings/cip/2020/06/cip.2020-06-18-09.00.log.html09:18
*** brlogger` changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/"09:18
masashi910Thanks, Bye!09:18
wensthanks!09:18
paveltestThank you!09:18
suzukiThank you!09:18
fujita3Thank you!09:19
*** fujita3 has quit IRC09:19
*** suzuki has quit IRC09:21
dineshk[m]Hi All, I am sorry, I got some urgent call and could not participate. From next week I am planning to join this meeting regularly.09:48
*** tpollard has quit IRC10:00
*** tpollard has joined #cip10:00
*** masashi910 has quit IRC10:40
*** paveltest has quit IRC13:15
*** tpollard has quit IRC16:20
*** rajm has quit IRC22:02

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!