*** yamamodo has joined #cip | 03:02 | |
*** yamamodo has left #cip | 03:03 | |
*** yamamodo has joined #cip | 03:07 | |
*** yamamodo has left #cip | 03:12 | |
*** Johnson has joined #cip | 03:12 | |
*** Johnson has left #cip | 03:12 | |
*** yamamodo has joined #cip | 03:18 | |
*** yamamodo_ has joined #cip | 06:11 | |
*** yamamodo_ has left #cip | 06:12 | |
*** yamamodo has quit IRC | 06:12 | |
*** johnsonch_chen has joined #cip | 06:12 | |
*** johnsonch_chen has left #cip | 06:13 | |
*** yamamodo has joined #cip | 06:13 | |
*** rajm has joined #cip | 06:43 | |
*** yamamodo has quit IRC | 07:05 | |
*** kane has joined #cip | 07:51 | |
*** kane is now known as Guest86457 | 07:51 | |
*** Guest86457 has left #cip | 07:52 | |
*** yamamodo has joined #cip | 08:09 | |
*** toscalix has joined #cip | 08:11 | |
*** pave1 has joined #cip | 08:56 | |
*** vidda has joined #cip | 08:59 | |
szlin | #startmeeting CIP IRC weekly meeting | 09:00 |
---|---|---|
brlogger | Meeting started Thu Jun 20 09:00:03 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 | |
szlin | #topic rollcall | 09:00 |
*** brlogger changes topic to "rollcall (Meeting topic: CIP IRC weekly meeting)" | 09:00 | |
patersonc | hi | 09:00 |
szlin | please say hi if you're here | 09:00 |
vidda | hi | 09:00 |
bwh | hi | 09:00 |
*** yamamodo has quit IRC | 09:00 | |
fujita[m] | hi | 09:00 |
pave1 | hi | 09:00 |
szlin | #topic AI review | 09:01 |
*** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 09:01 | |
*** yamamodo has joined #cip | 09:01 | |
yamamodo | hi | 09:01 |
iwamatsu | hi | 09:01 |
szlin | 1. Send investigating email for kernel-testing lab to cip-dev - patersonc | 09:01 |
patersonc | I think we can remove this action. I've created requirements for the lab and sent them to a vendor for quote. | 09:01 |
patersonc | When I know more about costs I'll update the TSC | 09:02 |
szlin | patersonc: thanks. | 09:02 |
szlin | 2. Provide the script for CIP kernel config collection - bwh | 09:02 |
bwh | This is nearly ready. I will push it to Gitlab shortly. | 09:02 |
szlin | bwh: thanks. | 09:03 |
szlin | 3. List some questions to ask Daniel Wagner - szlin | 09:03 |
szlin | This AI is still ongoing, | 09:03 |
pave1 | Ok, let me chime in. | 09:04 |
pave1 | I took a look at -cip-rt tree... and it is scary, but not that scary. | 09:04 |
pave1 | I guess best course of action is to simply try updating -cip-rt to 4.19.50, and gather any questions that arise while doing that. | 09:05 |
*** kazu_ has joined #cip | 09:05 | |
kazu_ | hi | 09:05 |
pave1 | Would it be ok for me to try that? | 09:05 |
szlin | no objection here | 09:05 |
szlin | iwamatsu: bwh any comments? | 09:06 |
bwh | No | 09:06 |
iwamatsu | pave1: ok | 09:06 |
szlin | #action Update CIP RT kernel to 4.19.50 - Pavel | 09:07 |
pave1 | I guess I'll have some (stupid) questions about rt after the meeting, if interested parties could stay for a while after that... | 09:07 |
szlin | pave1: please keep us posted after the updating :-) | 09:07 |
pave1 | szlin: I'd formulate that as "Try updating", but ok ;-). | 09:07 |
szlin | pave1: I see | 09:08 |
szlin | #topic Kernel maintenance updates | 09:08 |
*** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 09:08 | |
szlin | iwamatsu: pave1 bwh do you have any updates on kernel maintenance updates? | 09:09 |
iwamatsu | szlin: I released 4.4.181-cip33 and 4.19.50-cip3, and I reviewed v4.4.161 and v4.4.162. | 09:09 |
pave1 | I reviewed 4.19.51 and 4.19.53. | 09:10 |
szlin | iwamatsu: thank you for your work. | 09:10 |
szlin | pave1: thank you! | 09:10 |
pave1 | There was question on the mailing list: | 09:10 |
pave1 | 4.19.52 contains fixes for remote crash. | 09:10 |
bwh | It might be worth doig out-of-cycle updates to incorporate that | 09:11 |
pave1 | It is just a crash, but it got wide publicity. | 09:11 |
pave1 | Exactly. | 09:11 |
iwamatsu | pave1: I already upldated to lastet kernel in my local repo. | 09:11 |
szlin | Jan raised a question in SACK issue | 09:12 |
pave1 | iwamatsu: If that's okay with you, I believe releasing it soon would make sense. | 09:13 |
szlin | #info https://lists.cip-project.org/pipermail/cip-dev/2019-June/002496.html | 09:13 |
iwamatsu | I can release new cip kernel soon to fix SNAK issue. | 09:13 |
iwamatsu | pave1: OK, I will release after this meeting | 09:13 |
szlin | iwamatsu: thank you very much. so this new release will be at next Friday? | 09:14 |
szlin | iwamatsu: it's ok to reply me after the meeting | 09:16 |
*** kazu_ has quit IRC | 09:16 | |
szlin | any other topics? | 09:16 |
szlin | 3 | 09:16 |
szlin | 2 | 09:16 |
szlin | 1 | 09:16 |
*** kazu_ has joined #cip | 09:16 | |
szlin | #topic Kernel testing | 09:16 |
*** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 09:16 | |
patersonc | Hello | 09:17 |
patersonc | Issues with LAVA master (login issues, email notification issues) have been resolved. | 09:17 |
patersonc | I'm not sure if Mentor have made any more progress on their lab, I'll check. | 09:17 |
patersonc | LF are still working out if/how they can give us SSH access to the LAVA master. | 09:17 |
patersonc | Questions: | 09:17 |
patersonc | Regarding Renesas RZ/G boards, what maintainers already have access to a physical board? | 09:17 |
patersonc | And do any maintainers need a physical board if they don't already have one? | 09:17 |
patersonc | Is remote access using LAVA enough for maintenance needs? | 09:17 |
szlin | patersonc: do you mean "kernel" maintainer ? | 09:18 |
patersonc | Yes, sorry | 09:18 |
patersonc | Basically I want to know if Renesas needs to provide any more boards | 09:19 |
pave1 | No access, but I don't think I urgently need one. You are providing patches and testing, so there's not much development I need to do there | 09:19 |
patersonc | pave1: Okay. Thank you. | 09:20 |
szlin | bwh: iwamatsu: ^ do you have any comments? | 09:20 |
bwh | No | 09:20 |
iwamatsu | I dont have any comment. | 09:21 |
szlin | thanks. | 09:21 |
patersonc | Okay | 09:21 |
szlin | any other topics? | 09:21 |
patersonc | I guess that's it from me, unless there are any questions? | 09:21 |
szlin | 3 | 09:21 |
szlin | 2 | 09:21 |
szlin | 1 | 09:21 |
szlin | #topic CIP Core | 09:22 |
*** brlogger changes topic to "CIP Core (Meeting topic: CIP IRC weekly meeting)" | 09:22 | |
szlin | kazu_: give the floor to you | 09:22 |
kazu_ | Hello | 09:22 |
kazu_ | Held the second CIP-Core meeting to discuss the package decision process | 09:22 |
kazu_ | There are topics remaining that should be discussed more | 09:22 |
kazu_ | I'm clarifying the action items, then will report the summay to CIP members ML | 09:23 |
kazu_ | today or tomorrow | 09:23 |
szlin | kazu_: thanks, have you decided to have CIP-core F2F meeting in OSS-J? | 09:23 |
kazu_ | Sorry, not yet | 09:24 |
kazu_ | I would like to propose this topic to the ML as well | 09:24 |
szlin | kazu_: got it, please keep us posted if you make the decision :) | 09:24 |
kazu_ | Thank you | 09:25 |
szlin | any other topics? | 09:25 |
szlin | 3 | 09:25 |
szlin | 2 | 09:25 |
kazu_ | There are several technical updates from Daniel, but he doesn't attend ? | 09:25 |
szlin | kazu_: yes, he is not here | 09:25 |
kazu_ | OK, please go ahead | 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_: since Daniel is not here, would you like to update this topic? | 09:26 |
szlin | or he can update these topics via cip-dev afterwards | 09:28 |
kazu_ | Sorry, I don't summarize the updates of this topic... | 09:28 |
szlin | kazu_: never mind :) | 09:28 |
kazu_ | I think so | 09:28 |
szlin | any other updates? | 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:29 |
brlogger | Meeting ended Thu Jun 20 09:29:07 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:29 |
brlogger | Minutes: https://irclogs.baserock.org/meetings/cip/2019/06/cip.2019-06-20-09.00.html | 09:29 |
brlogger | Minutes (text): https://irclogs.baserock.org/meetings/cip/2019/06/cip.2019-06-20-09.00.txt | 09:29 |
brlogger | Log: https://irclogs.baserock.org/meetings/cip/2019/06/cip.2019-06-20-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 | |
szlin | thank you all | 09:29 |
kazu_ | Thank you | 09:29 |
yamamodo | Thanks | 09:29 |
bwh | Thanks | 09:29 |
iwamatsu | thanks | 09:29 |
fujita[m] | Thank you | 09:29 |
pave1 | thank you. | 09:29 |
iwamatsu | szlin: about kernel release, I plan to release it today or tomorrow. | 09:30 |
*** vidda has quit IRC | 09:30 | |
pave1 | About realtime... | 09:30 |
pave1 | Do we want to support all the hardware we support in cip? | 09:31 |
pave1 | Do we automatically take patches from -cipX to -cipX-rt? | 09:31 |
iwamatsu | pave1: | 09:32 |
iwamatsu | CIP-RT applies RT patch to CIP kernel. | 09:32 |
patersonc | pave1: At the moment we do. The -rt version get's rebased on top of the latest CIP Kernel each release. | 09:33 |
pave1 | Ok, so all hardware and all changes should automatically be incorporated. | 09:33 |
pave1 | patersonc: If I do changes to -cipX-rt, but won't release a new version, will you be able to test it? | 09:34 |
patersonc | It can be tested in the LAVA lab, yes. | 09:35 |
pave1 | Ok, good. I'll see what I can do. | 09:35 |
patersonc | pave1: Have you used the LAVA lab before? | 09:35 |
pave1 | I did run some test jobs, yes. | 09:36 |
patersonc | Great | 09:36 |
pave1 | I can't really imagine using it... it is complex. | 09:36 |
pave1 | But I guess I can get changes commited and ask for testing... | 09:37 |
iwamatsu | pave1: if you need to help, let me know. | 09:38 |
*** kazu_ has quit IRC | 09:38 | |
pave1 | iwamatsu: Thanks! | 09:39 |
patersonc | pave1: Okay. We need to work on a set of test cases that should be run. Then all the maintainer will need to do is modify the test job to specify where the Kernel to be tested is stored. | 09:39 |
patersonc | When the GitLab CI setup is complete this can be done automatically on branches/merge requests pushed to GitLab. | 09:39 |
pave1 | patersonc: Yes, that would be good. Get tests running on current -cipX-rt, so it is obvious when I break things. | 09:40 |
iwamatsu | creating test case is very important. I am building lava lab at my office and my house now. | 09:40 |
pave1 | patersonc: It would be good if some testing of actual latencies was performed. | 09:41 |
patersonc | iwamatsu: Great. Is this independent of CIP? | 09:41 |
patersonc | pave1: This is possible. | 09:41 |
patersonc | wagi started on this. | 09:42 |
patersonc | Cyclic test is one example, this is one of the tests that the RT project uses. | 09:42 |
iwamatsu | patersonc: Yes, | 09:42 |
iwamatsu | It is now independent. However, I am planning to connect to CIP lava network. | 09:42 |
pave1 | patersonc: Do you have pointer to wagi's git trees? I believe it was mentioned before, but I can't find the link. | 09:42 |
patersonc | https://github.com/igaw?tab=repositories | 09:43 |
pave1 | Thank you! | 09:44 |
patersonc | https://github.com/igaw/test-definitions/blob/preempt-rt/plans/rt/rt-performance.yaml | 09:44 |
szlin | pave1: I've maintained RT test tool for Daniel | 09:45 |
szlin | https://tracker.debian.org/pkg/jitterdebugger | 09:45 |
pave1 | patersonc: Would it be possible to get that running on -cipX-rt on some board you care about? | 09:46 |
patersonc | I'll have a go | 09:48 |
pave1 | Thanks! | 09:48 |
pave1 | szlin: Ok, I'll take a look, but I'm not sure I have suitable hardware for testing. | 09:49 |
*** CTtpollard has quit IRC | 09:50 | |
*** CTtpollard has joined #cip | 09:50 | |
*** yamamodo has quit IRC | 10:32 | |
*** tpollard has joined #cip | 10:48 | |
*** CTtpollard has quit IRC | 10:50 | |
*** pave1 has quit IRC | 12:14 | |
*** toscalix has quit IRC | 15:07 | |
*** tpollard has quit IRC | 15:59 | |
*** rajm has quit IRC | 17:40 | |
*** rajm has joined #cip | 21:41 | |
*** rajm has quit IRC | 22:33 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!