09:00:04 <szlin> #startmeeting CIP IRC weekly meeting
09:00:04 <brlogger`> Meeting started Thu Oct 10 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:04 <brlogger`> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
09:00:04 <brlogger`> The meeting name has been set to 'cip_irc_weekly_meeting'
09:00:15 <szlin> #topic rollcall
09:00:21 <szlin> please say hi if you're around
09:00:28 <patersonc> hi
09:00:31 <masashi910> hi, this is kudo
09:00:35 <kazu> hi
09:00:36 <suzuki26> hi
09:00:37 <pave11> hi
09:00:40 <iwamatsu_> hi
09:00:53 <fujita[m]> hi
09:01:06 <szlin> #topic AI review
09:01:17 <szlin> 1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san
09:01:42 <wens> hi
09:02:49 <szlin> iwamatsu_: do you have any update on this topic?
09:02:58 <iwamatsu_> szlin: this does not finished yet, patersonc and I discuss about this yet.
09:03:30 <szlin> iwamatsu_: thank you for the update.
09:03:37 <szlin> 2. Test LTS (pre)releases directly – patersonc
09:03:59 <patersonc> I haven't done anything on this topic this week.
09:04:34 <szlin> patersonc: got it, thanks.
09:04:38 <szlin> 3. Review the proposal from Kudo-san - Kernel team
09:04:47 <szlin> masashi910: do you have any update on this topic?
09:05:19 <masashi910> I don't have updates, but I would like to get opinions.
09:05:41 <masashi910> There were mainly two comments at the TSC meeting.
09:06:06 <masashi910> The first one is to get Xilinx management and engineers involved.
09:06:37 <masashi910> The discussion already started thanks to Jan-san. So this is ok for now.
09:07:16 <masashi910> The second one is whether the target should be added as CIP reference platform.
09:08:17 <masashi910> There are pros and cons if we do so before Xilinx guys participation in CIP.
09:08:45 <masashi910> I would like to know kernel team's opinion on this.
09:09:38 <patersonc> Can you link me to the board details please?
09:10:41 <patersonc> Is the board a different arch etc. to our other reference platforms
09:10:42 <patersonc> ?
09:12:00 <masashi910> patersonc: for example, how about this? https://www.digikey.jp/catalog/ja/partgroup/xilinx-zynq-ultrascale-mpsoc-zcu102-evaluation-kit/68042
09:12:35 <patersonc> Thanks masashi910
09:12:48 <masashi910> The board is based on v8, and it has FPGA.
09:14:06 <patersonc> So is it likely that Xilinx would join the CIP project as a member? Or are you proposing this board as a reference board from your company?
09:14:06 <szlin> ok, let's discuss it after the meeting.
09:14:14 <patersonc> szlin: Okay
09:14:19 <szlin> Update the status first :-)
09:14:26 <masashi910> OK
09:14:27 <szlin> masashi910: is that ok for you?
09:14:29 <szlin> thanks
09:14:35 <szlin> #topic Kernel maintenance updates
09:14:51 <pave11> I have reviewed 4.19.77, 4.19.78.
09:15:17 <szlin> I'm preparing the kernel team slide for ELCE 2019, and looking for presenter in CIP semi-summit.
09:15:24 <szlin> pave11: thank you.
09:15:27 <iwamatsu_> szlin: I reviewed v4.4.194 and v4.4.196
09:16:12 <szlin> any other topics?
09:16:13 <iwamatsu_> And pave1 and I reviewed patches from Renesas.
09:16:18 <szlin> iwamatsu_: thank you!
09:16:30 <szlin> 3
09:16:31 <szlin> 2
09:16:32 <szlin> 1
09:16:35 <szlin> #topic Kernel testing
09:16:57 <patersonc> #info Iwamatsu-san has submitted a MR to add LTP tests to linux-cip-ci. It's not merged yet as we're just deciding the best approach.
09:17:05 <patersonc> #link https://gitlab.com/cip-project/cip-testing/linux-cip-ci/merge_requests/24
09:17:06 <patersonc> #info A complete LTP test run takes about 3 hours per board, per config. So we need to reduce the amount of test cases (not ideal), or add more boards to the labs.
09:17:20 <patersonc> #info We're also debating whether to change the GitLab pipeline setup so it doesn't wait for jobs to complete running - it just submits them. The plan being that we'd check CIP's KernelCI (setup in progress) for test results.
09:17:23 <patersonc> Does anyone have any thoughts/comments on any of the above? (We can discuss after the other status updates if needed)
09:18:05 <szlin> patersonc: thanks for the update
09:18:10 <pave11> 3 hours is bad... if we run it on every commit.
09:18:23 <pave11> but if we do full run say ... once a day? It should not be that bad.
09:18:30 <pave11> Or every saturday or something like that.
09:18:46 <pave11> (Can discuss later).
09:18:51 <szlin> patersonc: feel free to list the topics that you want to discuss in ELCE f2f meeting
09:19:04 <szlin> any other topics?
09:19:05 <szlin> 3
09:19:06 <szlin> 2
09:19:08 <szlin> 1
09:19:15 <szlin> #topic CIP Core
09:19:33 <patersonc> pave11: Yep. And that's just for 1 config. If a board has multiple configs it'll run multiple times. We could add 10x each reference board to the labs. But one of the test cases takes over an hour to run alone. Will discuss later.
09:19:43 <kazu> I've moved PDP document to cip-pkglist git reo
09:19:44 <kazu> https://gitlab.com/cip-project/cip-core/cip-pkglist/blob/master/doc/pdp.md
09:19:59 <kazu> Please review and give me comments or questions by the next TSC meeting
09:20:20 <kazu> After the review, I'm planinng to start the initial proposal using the basic package (glibc?)
09:20:23 <szlin> kazu: thank you for the update
09:20:36 <kazu> Jan & I are preparing the slide for ELCE CIP Core
09:20:51 <kazu> No other technical updates in this week...
09:20:57 <szlin> any other topics?
09:21:00 <szlin> 3
09:21:01 <szlin> 2
09:21:02 <szlin> 1
09:21:09 <szlin> #topic Software update
09:21:17 <suzuki26> I've integrated "signed update image" function that is supported by SWUpdate into my WG's ELCE demo.
09:21:26 <suzuki26> Now I'm trying to integrate "encrypted update image" function into the demo and preparing the slide for CIP Mini-summit.
09:21:36 <suzuki26> That's all from my side.
09:21:49 <szlin> suzuki26: thank you for the update
09:21:52 <szlin> any other topics?
09:21:53 <szlin> 3
09:21:55 <szlin> 2
09:21:56 <szlin> 1
09:22:04 <szlin> #topic AOB
09:22:10 <szlin> any other business?
09:22:30 <patersonc> o/
09:22:49 <patersonc> Do you think 1h for the Kernel F2F meeting at ELC-E will be enough?
09:23:15 <szlin> not sure, it depends on the agenda
09:23:38 <patersonc> True
09:23:43 <szlin> and  we did it last time.
09:23:58 <patersonc> It sounds like Neil is struggling to find us a room
09:24:40 <szlin> I will contact him later.
09:25:06 <szlin> iwamatsu_: pave11: would you like to share the kernel maintenance experience in CIP semi-summit?
09:25:38 <pave11> szlin: I'm not sure how interesting topic that is or what to talk about.
09:25:45 <pave11> szlin: I can certainly answer questions...
09:26:59 <szlin> pave11: great, we can rethink the content.
09:27:14 <szlin> any other topics?
09:27:16 <szlin> 3
09:27:17 <szlin> 2
09:27:18 <szlin> 1
09:27:25 <szlin> #endmeeting