| *** rajm has joined #cip | 06:25 | |
| szlin | #startmeeting CIP IRC weekly meeting | 09:00 |
|---|---|---|
| brlogger | Meeting started Thu Oct 3 09:00:04 2019 UTC and is due to finish in 60 minutes. The chair is szlin. 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 | |
| *** kazu has joined #cip | 09:00 | |
| szlin | #topic rollcall | 09:00 |
| *** brlogger changes topic to "rollcall (Meeting topic: CIP IRC weekly meeting)" | 09:00 | |
| bwh | hi | 09:00 |
| szlin | please say hi if you're around | 09:00 |
| *** vidda has joined #cip | 09:00 | |
| kazu | hi | 09:00 |
| vidda | hi | 09:00 |
| gavinlai | hi | 09:00 |
| szlin | #topic AI review | 09:00 |
| *** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 09:00 | |
| szlin | 1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san | 09:01 |
| fujita[m] | hi | 09:01 |
| szlin | iwamatsu: are you around? | 09:01 |
| wens | hi | 09:01 |
| szlin | it seems like Iwamatsu-san is not around, I will skip this topic | 09:02 |
| kazu | szlin He is not in our office, but probably working in another place | 09:02 |
| szlin | kazu: thank you for your information | 09:02 |
| szlin | 2. Test LTS (pre)releases directly – patersonc | 09:02 |
| szlin | patersonc: are you around? | 09:02 |
| *** masashi910 has joined #cip | 09:03 | |
| *** iwamatsu_ has joined #cip | 09:03 | |
| *** pave1 has joined #cip | 09:03 | |
| iwamatsu_ | hi all. | 09:03 |
| szlin | 3. Move cip-core repo to cip-project/cip-core - kazu | 09:03 |
| pave1 | hi | 09:03 |
| masashi910 | hi | 09:03 |
| kazu | szlin done https://gitlab.com/cip-project/cip-core/cip-pkglist | 09:03 |
| szlin | iwamatsu: pave1: (wave | 09:03 |
| szlin | kazu: thank you very much | 09:03 |
| szlin | 4. Review the proposal from Kudo-san - Kernel team | 09:04 |
| szlin | Pavel reviewed it. | 09:04 |
| szlin | For now, we are discussing with SoC vendor. Thanks to Jan's information. | 09:04 |
| szlin | masashi910: do you have any update on this AI? | 09:04 |
| patersonc | hi | 09:05 |
| masashi910 | At this moment, I have no update from my side. I would like to know the next step. | 09:05 |
| patersonc | Yep | 09:06 |
| patersonc | Sorry I'm late. | 09:06 |
| szlin | patersonc: no worry :) | 09:06 |
| patersonc | For my AI, I'm still waiting for feedback. | 09:06 |
| pave1 | patersonc: Feedback on testing of stable -rc releases? | 09:07 |
| patersonc | pave1: Yep. | 09:07 |
| patersonc | Is the approach I'm going with suitable? | 09:07 |
| szlin | masashi910: next step is to wait for feedback with Xilinux, and we can start to merge codes afterward | 09:07 |
| pave1 | patersonc: (they are discussing Xilinx now, lets wait). | 09:07 |
| szlin | pave1: ^ do you have any comments | 09:08 |
| pave1 | szlin: Xilinx merge? | 09:09 |
| szlin | yes | 09:09 |
| pave1 | szlin: Seems doable from my side. Next steps were outlined in the email.. | 09:09 |
| szlin | pave1: thanks, I will keep this AI | 09:09 |
| szlin | masashi910: is that ok for you? | 09:09 |
| pave1 | szlin: Identifying what is really needed for basic system was on the list... | 09:10 |
| pave1 | szlin: and moving neccessary parts from starging to kernel proper in the mainline would be good steps. | 09:10 |
| szlin | pave1: indeed. | 09:10 |
| masashi910 | The next step provided by Pavel-san is quite reasonable. | 09:10 |
| iwamatsu_ | pave1: if your are OK, please add me to discuss xilinx (to CC)? | 09:10 |
| masashi910 | My question is if Xilinx does not respond, or does not cooperate with us, what happens. | 09:11 |
| iwamatsu_ | pave1: if you are discussing by email. | 09:11 |
| pave1 | iwamatsu: I thougth I'm copying cip-dev lists; that discussion was meant to be public. | 09:11 |
| iwamatsu_ | pave1: Oh, OK. thanks. | 09:12 |
| szlin | masashi910: let's discuss after the meeting, let's check the AI first :) | 09:12 |
| szlin | since Iwamatsu-san is here, I will back to the AI which belongs him | 09:12 |
| szlin | 1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san | 09:12 |
| masashi910 | Sure! Thanks. | 09:12 |
| szlin | iwamatsu: do you have any updates on this AI? | 09:13 |
| szlin | iwamatsu: are you around? | 09:14 |
| iwamatsu_ | szlin: I have almost completed this work. Now testing. | 09:14 |
| szlin | iwamatsu_: thank you, I will keep this AI | 09:14 |
| szlin | 2. Test LTS (pre)releases directly – patersonc | 09:14 |
| szlin | patersonc: do you have any update on this AI? | 09:14 |
| patersonc | I'm just waiting to see if there is any more feedback before continuing with this | 09:15 |
| szlin | patersonc: I see, thank you. | 09:15 |
| szlin | #topic Kernel maintenance updates | 09:15 |
| *** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 09:15 | |
| szlin | Iwamatsu-san released 4.19.75-cip11 | 09:16 |
| szlin | #info https://lists.cip-project.org/pipermail/cip-dev/2019-September/003340.html | 09:16 |
| szlin | Pavel released 4.4.190-cip36-rt25 and 4.19.72-cip10-rt3 | 09:16 |
| szlin | #info https://lists.cip-project.org/pipermail/cip-dev/2019-October/003394.html | 09:16 |
| szlin | #info https://lists.cip-project.org/pipermail/cip-dev/2019-October/003393.html | 09:16 |
| szlin | iwamatsu_: pave1: do you have any updates? | 09:16 |
| patersonc | We need a better way to view results etc. | 09:16 |
| patersonc | Probably best to use something like KernelCI | 09:16 |
| iwamatsu_ | pave1: thanks for your work. | 09:16 |
| pave1 | I reviewed 4.19.76... | 09:16 |
| iwamatsu_ | szlin: I reviewed 4.4.168 | 09:17 |
| szlin | iwamatsu_: pave1: thank you for your work | 09:17 |
| iwamatsu_ | patersonc: +1 | 09:17 |
| szlin | any other topics? | 09:18 |
| szlin | patersonc: that means we need to setup kernelCI | 09:18 |
| szlin | patersonc: it might related to testing, I will jump to next topic | 09:19 |
| szlin | 3 | 09:19 |
| szlin | 2 | 09:19 |
| szlin | 1 | 09:19 |
| szlin | #topic Kernel testing | 09:19 |
| *** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 09:19 | |
| patersonc | szlin: Which I've already instructed LF to do. | 09:19 |
| pave1 | patersonc: Big thanks for testing LTS prerelases directly. | 09:20 |
| patersonc | The LAVA master had some issues yesterday where it wasn't processing jobs. | 09:20 |
| szlin | patersonc: thank you :D | 09:20 |
| patersonc | I was debugging it last night. Still ongoing. | 09:20 |
| pave1 | patersonc: I have not figured out how to tell which -rc is being tested, but I'm sure I'll find out eventually :-). | 09:20 |
| patersonc | Have an issue where one of the jobs won't end, blocking the RZ/G1E board | 09:20 |
| patersonc | So any CI runs will eventually time out | 09:21 |
| patersonc | pave1: That's one of the issues. The only way to tell at the moment is to read the build log. Near the top the Kernel version is output. | 09:21 |
| pave1 | patersonc: Aha, thanks, good to know. | 09:21 |
| patersonc | In other news... | 09:22 |
| patersonc | I'm working to improve the pipline structure of CI jobs. The changes mean that tests can run as soon as a build is done, rather than have to wait for all builds to complete | 09:22 |
| patersonc | This should speed up the total time. | 09:23 |
| patersonc | See https://gitlab.com/cip-project/cip-kernel/linux-cip/pipelines/86158976 for an example | 09:23 |
| patersonc | That's probably it from me today. | 09:23 |
| patersonc | Again, sorry for the issues with the LAVA master | 09:23 |
| patersonc | I'll try and upgrade to the newest LAVA next week, hopefully that'll make it more stable | 09:23 |
| szlin | any other topics? | 09:24 |
| szlin | 3 | 09:24 |
| szlin | 2 | 09:24 |
| szlin | 1 | 09:24 |
| pave1 | patersonc: That sounds like a good idea. It also means that we'll see "arm64 | 09:24 |
| szlin | #topic CIP Core | 09:24 |
| *** brlogger changes topic to "CIP Core (Meeting topic: CIP IRC weekly meeting)" | 09:24 | |
| pave1 | patersonc: tests failed" and not "all tests failed" ... which looks better. | 09:24 |
| kazu | 1. I've updated PDP (v2.1), I'll get the final confirmation in cip-members about this | 09:24 |
| kazu | https://docs.google.com/document/d/1Ce4G6cTIY3IGXESlJQfVZ9r-V0kOPkxKDocpb4Ob_AY/ | 09:24 |
| patersonc | pave1: Agreed. | 09:24 |
| kazu | Discussions toward the package proposal in CIP security WG are now on-going | 09:25 |
| kazu | 2. Regarding Debian 8 packages, Toshiba & Renesas shared the package list that they want to maintain longer term (in cip-members) | 09:25 |
| kazu | I'm agree that CIP Core keep maintenance of Tiny profile (deby) for Debian 8, but the problem is maintenance of source packages | 09:25 |
| kazu | Before we propose this info to CIP, it would be better to get cost estimation from Debian ELTS | 09:25 |
| kazu | 3. Planning to hold a CIP Core WG meeting during ELCE, please reply in Doodle if you are interested in | 09:26 |
| kazu | No other update from me | 09:26 |
| szlin | kazu: thanks | 09:26 |
| szlin | any other topics? | 09:26 |
| szlin | 3 | 09:26 |
| szlin | 2 | 09:26 |
| szlin | 1 | 09:26 |
| szlin | #topic Software update | 09:26 |
| *** brlogger changes topic to "Software update (Meeting topic: CIP IRC weekly meeting)" | 09:26 | |
| szlin | kazu: do you have any updates on this topic? | 09:27 |
| kazu | Sorry, I could not get the detailed info from Suzuki-san but, | 09:27 |
| kazu | [ON-GOING] Add some basic security features | 09:27 |
| kazu | This seems to be the current focus | 09:27 |
| szlin | kazu: thanks. | 09:27 |
| kazu | (from TSC minute) | 09:28 |
| szlin | any other topics? | 09:28 |
| szlin | 3 | 09:28 |
| szlin | 2 | 09:28 |
| szlin | 1 | 09:28 |
| szlin | #topic AOB | 09:28 |
| *** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 09:28 | |
| szlin | any other business? | 09:28 |
| szlin | 3 | 09:28 |
| szlin | 2 | 09:28 |
| szlin | 1 | 09:28 |
| szlin | #endmeeting | 09:28 |
| brlogger | Meeting ended Thu Oct 3 09:28:50 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:28 |
| brlogger | Minutes: https://irclogs.baserock.org/meetings/cip/2019/10/cip.2019-10-03-09.00.html | 09:28 |
| brlogger | Minutes (text): https://irclogs.baserock.org/meetings/cip/2019/10/cip.2019-10-03-09.00.txt | 09:28 |
| brlogger | Log: https://irclogs.baserock.org/meetings/cip/2019/10/cip.2019-10-03-09.00.log.html | 09:28 |
| *** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/" | 09:28 | |
| szlin | thank you all | 09:28 |
| kazu | Thank you | 09:29 |
| iwamatsu_ | thanks | 09:29 |
| masashi910 | Thanks! | 09:29 |
| szlin | kazu: could you invite suzuki-san to join the meeting next week? | 09:29 |
| pave1 | thank you! | 09:29 |
| kazu | szlin OK, I will ask | 09:29 |
| fujita[m] | thank you | 09:30 |
| szlin | kazu: thank you | 09:30 |
| pave1 | Minutes do not seem to be available? | 09:31 |
| pave1 | Neither of the links from brlogger works for me :-( | 09:31 |
| pave1 | Patersonc: is there some easy way to retrigger the tests? | 09:32 |
| pave1 | patersonc: for example https://gitlab.com/cip-project/cip-kernel/linux-cip/pipelines/86143896 was cancelled, but it would be interesting to re-run the tests... | 09:33 |
| szlin | pave1: it works now. | 09:34 |
| szlin | I mean, meeting minutes | 09:34 |
| pave1 | szlin: Thansk! Yes, it works now. I guess it needs few seconds for processing. | 09:35 |
| szlin | pave1: do you have any suggestion with current situation in xilinux? | 09:35 |
| patersonc | pave1: Sorry, I'll be back in 5 | 09:36 |
| szlin | In case they don't reply us, just as Kudo-san mentioned. | 09:36 |
| pave1 | iwamatsu: my mails on Xilinx mpsoc should be on cip-dev, in "Xiling MPSOC -- was Re: CIP IRC weekly meeting today" thread | 09:38 |
| pave1 | iwamatsu: Sorry for spelling mistake. | 09:38 |
| masashi910 | SZ-san, we started the discussion with Xilinx thanks to Jan-san. | 09:39 |
| pave1 | iwamatsu: There's additional thread from "Jan Kiszka" that was not cc-ed to cip-dev. | 09:39 |
| szlin | masashi910: yes, I've received the reply few hours ago | 09:40 |
| masashi910 | Also I understand that the involvement of Xilinx kernel team would be much better. | 09:40 |
| masashi910 | Our intention is, however, to start the contribution from Mainline to CIP in parallel with this discussion with Xilinx folks. | 09:41 |
| *** kazu has quit IRC | 09:41 | |
| masashi910 | Because it may take a long time for Xilinx to decide whether they may want to cooperate with us. | 09:41 |
| szlin | pave1: do you have any concern to merge the codes from Cybertrust before confirming with Xilinux? | 09:42 |
| pave1 | szlin: From my side it looks like reasonable way forward. | 09:43 |
| masashi910 | Do you think the Xilinx involvement is the gating factor? | 09:43 |
| szlin | pave1: sure, let's do it. | 09:43 |
| szlin | masashi910: No. | 09:43 |
| pave1 | szlin: Of course, it all depends on how patches look like. | 09:43 |
| masashi910 | szlin: Thanks. I am relived. :) | 09:43 |
| szlin | pave1: thank you. | 09:43 |
| patersonc | pave1: I'm back. I'll chat to you once the xilinx discussion is done | 09:44 |
| masashi910 | s/relived/relieved/ | 09:44 |
| pave1 | szlin: But promoting patches from staging to mainline proper and separating basic changes needed for boot is not something that needs Xilinx involvement. | 09:44 |
| szlin | masashi910: thank you for your understanding, let's move forward :) | 09:44 |
| masashi910 | pave1: Definitely. Their involvement in that case is needed. I agree. | 09:45 |
| masashi910 | szlin: Thanks! | 09:45 |
| pave1 | masashi910: I was trying to say that you can submit patches to mainline, too. It does _not_ need Xilinx involvement. | 09:46 |
| pave1 | masashi910: Except they probably need to be cc-ed, let me check the maintainers :-). | 09:46 |
| masashi910 | pave1: I see. Regarding this, I would like to continue to discuss with you. In somehow, there might be areas SoC vendors should be involved. | 09:48 |
| masashi910 | pave1: Anyway, thanks for your consideration. | 09:48 |
| masashi910 | So, thanks all for the discussion for code contribution. I am leaving today. | 09:49 |
| pave1 | masashi910: Of course, if you can get SoC vendor involved, that's a good thing :-). | 09:49 |
| masashi910 | pave1: Thanks for your comments! Very helpful! | 09:50 |
| pave1 | masashi910: You are welcome, good luck with the project. | 09:50 |
| masashi910 | pave1: Thanks! | 09:50 |
| pave1 | patersonc: It seems channel is ours :-) | 09:53 |
| *** masashi910 has quit IRC | 09:53 | |
| patersonc | pave1: Wooo | 09:56 |
| patersonc | There is a way to re-submit jobs, yes | 09:56 |
| patersonc | But maybe you don't have the power? | 09:57 |
| patersonc | If you go to the pipeline screen: https://gitlab.com/cip-project/cip-kernel/linux-cip/pipelines | 09:57 |
| patersonc | If a pipeline wasn't successful there will be a "restart" button on the right. | 09:58 |
| patersonc | A circular arrow | 09:58 |
| pave1 | Aha, I see it. | 09:58 |
| patersonc | If you go into the pipeline itself you can also do this on a per job basis | 09:58 |
| pave1 | Aha, I wsa at the pipeline itself, and did not see the button. | 09:59 |
| patersonc | Both options only retry jobs that didn't complete - no need to re-run jobs that were successful | 09:59 |
| pave1 | hmm. Now I see it even on the pipeline itself. | 10:00 |
| patersonc | pave1: You'll find from pipeline 86143896 that it will fail. The tests on the G1E boards won't be able to run due to the problems I mentioned earlier | 10:00 |
| pave1 | Aha. | 10:00 |
| patersonc | The rest of the boards will be tested though | 10:00 |
| *** toscalix has joined #cip | 10:01 | |
| patersonc | Feel free to run it. I just cancelled it last night because I was doing lots of reboots on the lava master | 10:01 |
| pave1 | Ok, let me try to run it anyway. If it fails elsewhere it will be good to know. | 10:01 |
| pave1 | Is it safe to queue more than one job for testing? | 10:01 |
| pave1 | afc | 10:02 |
| patersonc | Sure | 10:02 |
| patersonc | Sure. Just the more that are running the bigger the queue will be :) | 10:05 |
| patersonc | pave1: Maybe the job will pass - LAVA ignores the job request because I put the RZ/G1E board into retirement. | 10:11 |
| patersonc | Huzzah. LAVA master is back up and running properly. | 10:15 |
| pave1 | patersonc: Yep, now it says passed. Thanks! | 10:18 |
| pave1 | patersonc: But there's like 60 minutes timeouts on the jobs, so if I queue way too many, eventually it will timeout and fail, right? | 10:18 |
| patersonc | Yep | 10:19 |
| patersonc | Hopefully an hour is enough though - although we'll have to rethink it when we start running LTS tests etc. | 10:20 |
| patersonc | Some of them take an hour on their own | 10:20 |
| patersonc | s/LTS/LTP | 10:20 |
| pave1 | patersonc: Yes. Maybe running _such_ long tests only makes sense on manual request. | 10:21 |
| pave1 | patersonc: Are we running realtime tests (cyclictest?) at the moment? | 10:22 |
| patersonc | pave1: Not yet. I was working on it before all the LAVA master issues. | 10:24 |
| pave1 | patersonc: That makes sense. Thanks! | 10:24 |
| patersonc | At the moment we're running a boot test and the spectre/meltdown checker test | 10:24 |
| patersonc | To be honest, if we're running other tests, maybe we don't also need a boot test :) | 10:25 |
| patersonc | We'll get there | 10:25 |
| patersonc | I just wish I could work on this 100% of the time, rather than about 10% | 10:25 |
| pave1 | patersonc: And I guess spectre/meltdown test would not be the most important test I'd select. | 10:26 |
| pave1 | patersonc: But knowing that the board boots is always good thing. | 10:27 |
| patersonc | Indeed | 10:28 |
| pave1 | bye for now... | 10:31 |
| patersonc | ttfn | 10:38 |
| *** vidda has quit IRC | 10:44 | |
| *** pave1 has quit IRC | 10:51 | |
| *** masashi910 has joined #cip | 12:09 | |
| *** masashi910 has quit IRC | 12:13 | |
| *** toscalix has quit IRC | 18:10 | |
| *** iwamatsu_ has quit IRC | 20:06 | |
| *** iwamatsu_ has joined #cip | 20:18 | |
| *** iwamatsu_ has quit IRC | 20:30 | |
| *** rajm has quit IRC | 22:06 | |
| *** iwamatsu_ has joined #cip | 22:19 | |
| *** iwamatsu_ has quit IRC | 23:59 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!