*** rajm has joined #cip | 06:26 | |
*** punit has quit IRC | 07:56 | |
*** masashi910 has joined #cip | 07:56 | |
*** masashi910 has joined #cip | 07:57 | |
*** punit has joined #cip | 08:01 | |
*** tpollard has joined #cip | 08:07 | |
*** pavel1 has joined #cip | 08:55 | |
*** suzuki has joined #cip | 08:59 | |
*** bwh has joined #cip | 08:59 | |
masashi910 | #startmeeting CIP IRC weekly meeting | 09:00 |
---|---|---|
brlogger | Meeting 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 |
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 rollcall | 09:00 |
*** brlogger changes topic to "rollcall (Meeting topic: CIP IRC weekly meeting)" | 09:00 | |
masashi910 | please say hi if you're around | 09:00 |
szlin | hi | 09:00 |
suzuki | hi | 09:00 |
patersonc | hi | 09:00 |
bwh | hi | 09:00 |
pavel1 | hi | 09:00 |
masashi910 | #topic AI review | 09:01 |
*** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 09:01 | |
masashi910 | 1. Combine root filesystem with kselftest binary - Iwamatsu-san | 09:01 |
masashi910 | iwamatsu: are you around? | 09:01 |
wens | hi | 09:01 |
masashi910 | Iwamatsu-san does not seem to be here. So let's skip. | 09:02 |
masashi910 | Regarding the following AIs, I have no updates. | 09:02 |
masashi910 | 2. Strengthen sustainable process to backport patches from Mainline/LTS - Kernel Team | 09:02 |
masashi910 | 3. Upload a guideline for reference hardware platform addition - masashi910 | 09:02 |
masashi910 | So, let's move to next. | 09:03 |
masashi910 | #topic Kernel maintenance updates | 09:03 |
*** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 09:03 | |
pavel1 | I have reviewed 4.19.120 and 4.19.121. | 09:03 |
wens | new CVEs this week all fixed | 09:03 |
masashi910 | pavel1, wens: thanks for your works. | 09:04 |
masashi910 | All, I would like to know your opinions on two topics. | 09:05 |
masashi910 | 1'st topic. | 09:05 |
masashi910 | SZ-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 |
masashi910 | Regarding the CIP kernel, the current structure is like the following according to SZ-san. | 09:05 |
masashi910 | Main: kerne.org, Mirror1: our gitlab repository, Mirror2: the above mirror site (1) | 09:05 |
masashi910 | So, we may not need two mirror sites because maitenance cost should be considered. | 09:06 |
masashi910 | Do you think we can stop Mirror2? | 09:06 |
pavel1 | I guess so. We have local copies, anyway, so... | 09:07 |
pavel1 | ...in case of something catastrophic, we can recreate. | 09:07 |
szlin | second | 09:07 |
masashi910 | pavel1, szlin: Thanks for your comments! | 09:07 |
masashi910 | So, in order to stop it, should we ask Yoshi-san? | 09:08 |
patersonc | I guess ask in the TSC? | 09:08 |
szlin | masashi910: how about notifing everyone in the TSC meeting | 09:08 |
szlin | s/notifing/notifying | 09:09 |
masashi910 | patersonc, szlin: Thanks. Yes, that's reasonable. I will raise this in TSC meeting. | 09:09 |
szlin | masashi910: thank you. | 09:09 |
masashi910 | szlin: thanks! | 09:10 |
masashi910 | so, 2nd topic. | 09:10 |
masashi910 | Currently 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 |
masashi910 | It is time-consuming to check outputs of LTP, so it may be difficult to handle them on volunteer-basis. | 09:10 |
masashi910 | Do you think it makes sense to raise this issue to TSC and GB to allocate budget to hire engineers to check them? | 09:10 |
patersonc | masashi910: I've spoken to KernelCI about this a bit if you want an update now? | 09:10 |
masashi910 | patersonc: Yes please. | 09:11 |
patersonc | They 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 |
patersonc | With 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 cases | 09:12 |
patersonc | Which is basically what we want | 09:12 |
patersonc | So we could start registering our results to kernelci.org, or maybe a CIP speicifc instance, and we can keep better track of results there | 09:12 |
patersonc | Does that sound okay? | 09:14 |
masashi910 | patersonc: So, your idea is to ask kernelCI team to check results? | 09:14 |
patersonc | Well, the results would be checked automatically using KernelCI's s/w. We'd just need to check our emails | 09:15 |
pavel1 | Sounds reasonable to me. | 09:15 |
masashi910 | patersonc: Oh, I misunderstood. Do they have such automatic checking s/w? | 09:16 |
patersonc | Yes. It's already used for other test cases | 09:16 |
masashi910 | patersonc: I see. Then, shall we start registering our LTP results to kernelCI? | 09:17 |
patersonc | I'll start working on some kind of integration with KernelCi later in the month | 09:18 |
masashi910 | patersonc: That's great! Thanks for checking with KernelCI and for your proposal! | 09:18 |
masashi910 | any other topics? | 09:19 |
masashi910 | 3 | 09:19 |
masashi910 | 2 | 09:19 |
masashi910 | 1 | 09:19 |
masashi910 | #topic Kernel testing | 09:19 |
*** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 09:19 | |
masashi910 | patersonc: the floor is yours. | 09:19 |
patersonc | I've been discussing how we can collaborate more with KernelCI. | 09:20 |
patersonc | I've also been working to upgrade our LAVA servers to the latest version of LAVA/lava-docker. | 09:20 |
patersonc | I'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 |
patersonc | Would this cause any issues for anyone wanting to use the CI for testing? | 09:21 |
masashi910 | patersonc: looks like it's ok :) | 09:22 |
patersonc | :) | 09:22 |
patersonc | That's it from me I think | 09:22 |
masashi910 | patersonc: thanks for your works. | 09:22 |
masashi910 | any other topics? | 09:23 |
masashi910 | 3 | 09:23 |
masashi910 | 2 | 09:23 |
masashi910 | 1 | 09:23 |
masashi910 | #topic CIP Core | 09:23 |
*** brlogger changes topic to "CIP Core (Meeting topic: CIP IRC weekly meeting)" | 09:23 | |
masashi910 | Daniel-san, or Punit-san, are you around? | 09:23 |
masashi910 | OK, let's move on. | 09:24 |
masashi910 | #topic Software update | 09:24 |
*** brlogger changes topic to "Software update (Meeting topic: CIP IRC weekly meeting)" | 09:24 | |
suzuki | Hello. | 09:24 |
masashi910 | Suzuki-san, please. | 09:24 |
suzuki | I don't have major updates since last meeting because of national holidays. | 09:24 |
suzuki | That's it from me. | 09:24 |
masashi910 | suzuki: Noted. thanks for joining the IRC anyway. | 09:24 |
masashi910 | #topic CIP Security | 09:25 |
*** brlogger changes topic to "CIP Security (Meeting topic: CIP IRC weekly meeting)" | 09:25 | |
masashi910 | Yoshida-san is not here. So, let's skip. | 09:25 |
masashi910 | #topic AOB | 09:25 |
*** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 09:25 | |
masashi910 | Are there any business matters to discuss? | 09:25 |
patersonc | OSS-NA tickets are available | 09:26 |
patersonc | It's online only now | 09:26 |
patersonc | I think CIP members can get 20% off, so only $40 | 09:26 |
masashi910 | patersonc: thanks for this information. | 09:27 |
masashi910 | Then, from me. | 09:27 |
masashi910 | I have a session at OSS-NA. | 09:28 |
masashi910 | https://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 |
masashi910 | In order to create material for it, I may ask your help. | 09:28 |
masashi910 | It's heads-up. :) | 09:28 |
masashi910 | Any other business? | 09:29 |
masashi910 | 3 | 09:29 |
masashi910 | 2 | 09:29 |
masashi910 | 1 | 09:29 |
masashi910 | #endmeeting | 09:29 |
brlogger | Meeting ended Thu May 7 09:29:36 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:29 |
brlogger | Minutes: https://irclogs.baserock.org/meetings/cip/2020/05/cip.2020-05-07-09.00.html | 09:29 |
brlogger | Minutes (text): https://irclogs.baserock.org/meetings/cip/2020/05/cip.2020-05-07-09.00.txt | 09:29 |
brlogger | Log: https://irclogs.baserock.org/meetings/cip/2020/05/cip.2020-05-07-09.00.log.html | 09:29 |
*** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/" | 09:29 | |
masashi910 | Thank you! Stay safe! | 09:29 |
pavel1 | thank you! | 09:29 |
suzuki | Thank you! | 09:29 |
*** suzuki has quit IRC | 09:30 | |
bwh | Thanks masashi910 | 09:30 |
szlin | thank you | 09:31 |
wens | thank you | 09:33 |
*** pavel1 has quit IRC | 09:35 | |
*** patersonc has quit IRC | 09:39 | |
*** yoshidak[m] has quit IRC | 09:39 | |
*** yoshidak[m] has joined #cip | 09:54 | |
*** patersonc has joined #cip | 10:13 | |
*** dl9pf_home has quit IRC | 10:55 | |
*** dl9pf_home has joined #cip | 10:56 | |
*** dl9pf_home has joined #cip | 10:56 | |
*** masashi910 has quit IRC | 13:40 | |
*** tpollard has quit IRC | 17:00 | |
*** rajm has quit IRC | 22:12 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!