IRC logs for #cip for Thursday, 2020-05-07

*** rajm has joined #cip06:26
*** punit has quit IRC07:56
*** masashi910 has joined #cip07:56
*** masashi910 has joined #cip07:57
*** punit has joined #cip08:01
*** tpollard has joined #cip08:07
*** pavel1 has joined #cip08:55
*** suzuki has joined #cip08:59
*** bwh has joined #cip08:59
masashi910#startmeeting CIP IRC weekly meeting09:00
brloggerMeeting started Thu May  7 09:00:01 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
brloggerUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
brloggerThe 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
szlinhi09:00
suzukihi09:00
patersonchi09:00
bwhhi09:00
pavel1hi09:00
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 - Iwamatsu-san09:01
masashi910iwamatsu: are you around?09:01
wenshi09:01
masashi910Iwamatsu-san does not seem to be here. So let's skip.09:02
masashi910Regarding the following AIs, I have no updates.09:02
masashi9102. Strengthen sustainable process to backport patches from Mainline/LTS - Kernel Team09:02
masashi9103. Upload a guideline for reference hardware platform addition - masashi91009:02
masashi910So, let's move to next.09:03
masashi910#topic Kernel maintenance updates09:03
*** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"09:03
pavel1I have reviewed 4.19.120 and 4.19.121.09:03
wensnew CVEs this week all fixed09:03
masashi910pavel1, wens: thanks for your works.09:04
masashi910All, I would like to know your opinions on two topics.09:05
masashi9101'st topic.09:05
masashi910SZ-san fixed the issue of mirroring, and now, the CIP kernel(1) and CIP-kernel-sec(2) repositories  in github are up-to-date.09:05
masashi910Regarding the CIP kernel, the current structure is like the following according to SZ-san.09:05
masashi910Main: kerne.org,  Mirror1: our gitlab repository, Mirror2: the above mirror site (1)09:05
masashi910So, we may not need two mirror sites because maitenance cost should be considered.09:06
masashi910Do you think we can stop Mirror2?09:06
pavel1I guess so. We have local copies, anyway, so...09:07
pavel1...in case of something catastrophic, we can recreate.09:07
szlinsecond09:07
masashi910pavel1, szlin: Thanks for your comments!09:07
masashi910So, in order to stop it, should we ask Yoshi-san?09:08
patersoncI guess ask in the TSC?09:08
szlinmasashi910: how about notifing everyone in the TSC meeting09:08
szlins/notifing/notifying09:09
masashi910patersonc, szlin: Thanks. Yes, that's reasonable. I will raise this in TSC meeting.09:09
szlinmasashi910: thank you.09:09
masashi910szlin: thanks!09:10
masashi910so, 2nd topic.09:10
masashi910Currently Chris-san is running LTP on the CIP reference platforms, but the outputs of LTP are not deeply examined as I understand correctly.09:10
masashi910It is time-consuming to check outputs of LTP, so it may be difficult to handle them on volunteer-basis.09:10
masashi910Do you think it makes sense to raise this issue to TSC and GB to allocate budget to hire engineers to check them?09:10
patersoncmasashi910: I've spoken to KernelCI about this a bit if you want an update now?09:10
masashi910patersonc: Yes please.09:11
patersoncThey don't currently have LTP running, but it is something they want to do. So I suggest we work with them seeing as we're members of the project.09:11
patersoncWith regards to checking the results, this is something that KernelCI can already do automatically, notifying users if there are any test regressions for individual test cases09:12
patersoncWhich is basically what we want09:12
patersoncSo we could start registering our results to kernelci.org, or maybe a CIP speicifc instance, and we can keep better track of results there09:12
patersoncDoes that sound okay?09:14
masashi910patersonc: So, your idea is to ask kernelCI team to check results?09:14
patersoncWell, the results would be checked automatically using KernelCI's s/w. We'd just need to check our emails09:15
pavel1Sounds reasonable to me.09:15
masashi910patersonc: Oh, I misunderstood. Do they have such automatic checking s/w?09:16
patersoncYes. It's already used for other test cases09:16
masashi910patersonc: I see. Then, shall we start registering our LTP results to kernelCI?09:17
patersoncI'll start working on some kind of integration with KernelCi later in the month09:18
masashi910patersonc: That's great! Thanks for checking with KernelCI and for your proposal!09:18
masashi910any other topics?09:19
masashi910309:19
masashi910209:19
masashi910109:19
masashi910#topic Kernel testing09:19
*** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"09:19
masashi910patersonc: the floor is yours.09:19
patersoncI've been discussing how we can collaborate more with KernelCI.09:20
patersoncI've also been working to upgrade our LAVA servers to the latest version of LAVA/lava-docker.09:20
patersoncI'm hoping to upgrade the master and slaves next week, so there will likely be some downtime for a day or so on Wednesday.09:20
patersonc(if the lab admins are okay with this)09:20
patersoncWould this cause any issues for anyone wanting to use the CI for testing?09:21
masashi910patersonc: looks like it's ok :)09:22
patersonc:)09:22
patersoncThat's it from me I think09:22
masashi910patersonc: thanks for your works.09:22
masashi910any other topics?09:23
masashi910309:23
masashi910209:23
masashi910109:23
masashi910#topic CIP Core09:23
*** brlogger changes topic to "CIP Core (Meeting topic: CIP IRC weekly meeting)"09:23
masashi910Daniel-san, or Punit-san, are you around?09:23
masashi910OK, let's move on.09:24
masashi910#topic Software update09:24
*** brlogger changes topic to "Software update (Meeting topic: CIP IRC weekly meeting)"09:24
suzukiHello.09:24
masashi910Suzuki-san, please.09:24
suzukiI don't have major updates since last meeting because of national holidays.09:24
suzukiThat's it from me.09:24
masashi910suzuki: Noted. thanks for joining the IRC anyway.09:24
masashi910#topic CIP Security09:25
*** brlogger changes topic to "CIP Security (Meeting topic: CIP IRC weekly meeting)"09:25
masashi910Yoshida-san is not here. So, let's skip.09:25
masashi910#topic AOB09:25
*** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"09:25
masashi910Are there any business matters to discuss?09:25
patersoncOSS-NA tickets are available09:26
patersoncIt's online only now09:26
patersoncI think CIP members can get 20% off, so only $4009:26
masashi910patersonc: thanks for this information.09:27
masashi910Then, from me.09:27
masashi910I have a session at OSS-NA.09:28
masashi910https://ossna2020.sched.com/event/c3VM/cip-kernel-team-activities-to-accomplish-super-long-term-support-masashi-kudo-cybertrust-japan-co-ltd-sz-lin-moxa-inc?iframe=yes&w=100%&sidebar=yes&bg=no#09:28
masashi910In order to create material for it, I may ask your help.09:28
masashi910It's heads-up. :)09:28
masashi910Any other business?09:29
masashi910309:29
masashi910209:29
masashi910109:29
masashi910#endmeeting09:29
brloggerMeeting ended Thu May  7 09:29:36 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:29
brloggerMinutes:        https://irclogs.baserock.org/meetings/cip/2020/05/cip.2020-05-07-09.00.html09:29
brloggerMinutes (text): https://irclogs.baserock.org/meetings/cip/2020/05/cip.2020-05-07-09.00.txt09:29
brloggerLog:            https://irclogs.baserock.org/meetings/cip/2020/05/cip.2020-05-07-09.00.log.html09:29
*** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/"09:29
masashi910Thank you! Stay safe!09:29
pavel1thank you!09:29
suzukiThank you!09:29
*** suzuki has quit IRC09:30
bwhThanks masashi91009:30
szlinthank you09:31
wensthank you09:33
*** pavel1 has quit IRC09:35
*** patersonc has quit IRC09:39
*** yoshidak[m] has quit IRC09:39
*** yoshidak[m] has joined #cip09:54
*** patersonc has joined #cip10:13
*** dl9pf_home has quit IRC10:55
*** dl9pf_home has joined #cip10:56
*** dl9pf_home has joined #cip10:56
*** masashi910 has quit IRC13:40
*** tpollard has quit IRC17:00
*** rajm has quit IRC22:12

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