09:00:04 <szlin> #startmeeting CIP IRC weekly meeting
09:00:04 <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: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:17 <bwh> hi
09:00:20 <szlin> please say hi if you're around
09:00:22 <kazu> hi
09:00:23 <vidda> hi
09:00:41 <gavinlai> hi
09:00:51 <szlin> #topic AI review
09:01:02 <szlin> 1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san
09:01:03 <fujita[m]> hi
09:01:09 <szlin> iwamatsu: are you around?
09:01:58 <wens> hi
09:02:03 <szlin> it seems like Iwamatsu-san is not around, I will skip this topic
09:02:06 <kazu> szlin He is not in our office, but probably working in another place
09:02:24 <szlin> kazu: thank you for your information
09:02:29 <szlin> 2. Test LTS (pre)releases directly – patersonc
09:02:36 <szlin> patersonc: are you around?
09:03:32 <iwamatsu_> hi all.
09:03:35 <szlin> 3. Move cip-core repo to cip-project/cip-core - kazu
09:03:35 <pave1> hi
09:03:42 <masashi910> hi
09:03:45 <kazu> szlin done https://gitlab.com/cip-project/cip-core/cip-pkglist
09:03:45 <szlin> iwamatsu: pave1:  (wave
09:03:52 <szlin> kazu: thank you very much
09:04:03 <szlin> 4. Review the proposal from Kudo-san - Kernel team
09:04:18 <szlin> Pavel reviewed it.
09:04:48 <szlin> For now, we are discussing with SoC vendor. Thanks to Jan's information.
09:04:59 <szlin> masashi910: do you have any update on this AI?
09:05:25 <patersonc> hi
09:05:52 <masashi910> At this moment, I have no update from my side. I would like to know the next step.
09:06:01 <patersonc> Yep
09:06:05 <patersonc> Sorry I'm late.
09:06:12 <szlin> patersonc: no worry :)
09:06:27 <patersonc> For my AI, I'm still waiting for feedback.
09:07:05 <pave1> patersonc: Feedback on testing of stable -rc releases?
09:07:27 <patersonc> pave1: Yep.
09:07:34 <patersonc> Is the approach I'm going with suitable?
09:07:37 <szlin> masashi910: next step is to wait for feedback with Xilinux, and we can start to merge codes afterward
09:07:54 <pave1> patersonc: (they are discussing Xilinx now, lets wait).
09:08:25 <szlin> pave1: ^ do you have any comments
09:09:01 <pave1> szlin: Xilinx merge?
09:09:04 <szlin> yes
09:09:34 <pave1> szlin: Seems doable from my side. Next steps were outlined in the email..
09:09:44 <szlin> pave1: thanks, I will keep this AI
09:09:49 <szlin> masashi910: is that ok for you?
09:10:00 <pave1> szlin: Identifying what is really needed for basic system was on the list...
09:10:20 <pave1> szlin: and moving neccessary parts from starging to kernel proper in the mainline would be good steps.
09:10:35 <szlin> pave1: indeed.
09:10:36 <masashi910> The next step provided by Pavel-san is quite reasonable.
09:10:45 <iwamatsu_> pave1: if your are OK, please add me to discuss xilinx (to CC)?
09:11:09 <masashi910> My question is if Xilinx does not respond, or does not cooperate with us, what happens.
09:11:27 <iwamatsu_> pave1: if you are discussing by email.
09:11:50 <pave1> iwamatsu: I thougth I'm copying cip-dev lists; that discussion was meant to be public.
09:12:33 <iwamatsu_> pave1: Oh, OK. thanks.
09:12:38 <szlin> masashi910: let's discuss after the meeting, let's check the AI first :)
09:12:53 <szlin> since Iwamatsu-san is here, I will back to the AI which belongs him
09:12:56 <szlin> 1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san
09:12:57 <masashi910> Sure! Thanks.
09:13:30 <szlin> iwamatsu: do you have any updates on this AI?
09:14:23 <szlin> iwamatsu: are you around?
09:14:28 <iwamatsu_> szlin: I have almost completed this work. Now testing.
09:14:39 <szlin> iwamatsu_: thank you, I will keep this AI
09:14:40 <szlin> 2. Test LTS (pre)releases directly – patersonc
09:14:48 <szlin> patersonc: do you have any update on this AI?
09:15:35 <patersonc> I'm just waiting to see if there is any more feedback before continuing with this
09:15:50 <szlin> patersonc: I see, thank you.
09:15:53 <szlin> #topic Kernel maintenance updates
09:16:01 <szlin> Iwamatsu-san released 4.19.75-cip11
09:16:02 <szlin> #info https://lists.cip-project.org/pipermail/cip-dev/2019-September/003340.html
09:16:02 <szlin> Pavel released 4.4.190-cip36-rt25 and 4.19.72-cip10-rt3
09:16:02 <szlin> #info https://lists.cip-project.org/pipermail/cip-dev/2019-October/003394.html
09:16:02 <szlin> #info https://lists.cip-project.org/pipermail/cip-dev/2019-October/003393.html
09:16:37 <szlin> iwamatsu_: pave1: do you have any updates?
09:16:43 <patersonc> We need a better way to view results etc.
09:16:44 <patersonc> Probably best to use something like KernelCI
09:16:53 <iwamatsu_> pave1: thanks for your work.
09:16:58 <pave1> I reviewed 4.19.76...
09:17:16 <iwamatsu_> szlin: I reviewed 4.4.168
09:17:30 <szlin> iwamatsu_: pave1: thank you for your work
09:17:47 <iwamatsu_> patersonc: +1
09:18:06 <szlin> any other topics?
09:18:54 <szlin> patersonc: that means we need to setup kernelCI
09:19:24 <szlin> patersonc: it might related to testing, I will jump to next topic
09:19:25 <szlin> 3
09:19:26 <szlin> 2
09:19:27 <szlin> 1
09:19:34 <szlin> #topic Kernel testing
09:19:36 <patersonc> szlin: Which I've already instructed LF to do.
09:20:16 <pave1> patersonc: Big thanks for testing LTS prerelases directly.
09:20:25 <patersonc> The LAVA master had some issues yesterday where it wasn't processing jobs.
09:20:29 <szlin> patersonc: thank you :D
09:20:42 <patersonc> I was debugging it last night. Still ongoing.
09:20:56 <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:57 <patersonc> Have an issue where one of the jobs won't end, blocking the RZ/G1E board
09:21:08 <patersonc> So any CI runs will eventually time out
09:21:28 <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:48 <pave1> patersonc: Aha, thanks, good to know.
09:22:17 <patersonc> In other news...
09:22:49 <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:23:03 <patersonc> This should speed up the total time.
09:23:10 <patersonc> See https://gitlab.com/cip-project/cip-kernel/linux-cip/pipelines/86158976 for an example
09:23:39 <patersonc> That's probably it from me today.
09:23:49 <patersonc> Again, sorry for the issues with the LAVA master
09:23:56 <patersonc> I'll try and upgrade to the newest LAVA next week, hopefully that'll make it more stable
09:24:09 <szlin> any other topics?
09:24:17 <szlin> 3
09:24:18 <szlin> 2
09:24:19 <szlin> 1
09:24:20 <pave1> patersonc: That sounds like a good idea. It also means that we'll see "arm64
09:24:22 <szlin> #topic CIP Core
09:24:41 <pave1> patersonc: tests failed" and not "all tests failed" ... which looks better.
09:24:46 <kazu> 1. I've updated PDP (v2.1), I'll get the final confirmation in cip-members about this
09:24:52 <kazu> https://docs.google.com/document/d/1Ce4G6cTIY3IGXESlJQfVZ9r-V0kOPkxKDocpb4Ob_AY/
09:24:59 <patersonc> pave1: Agreed.
09:25:00 <kazu> Discussions toward the package proposal in CIP security WG are now on-going
09:25:16 <kazu> 2. Regarding Debian 8 packages, Toshiba & Renesas shared the package list that they want to maintain longer term (in cip-members)
09:25:35 <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:51 <kazu> Before we propose this info to CIP, it would be better to get cost estimation from Debian ELTS
09:26:07 <kazu> 3. Planning to hold a CIP Core WG meeting during ELCE, please reply in Doodle if you are interested in
09:26:30 <kazu> No other update from me
09:26:39 <szlin> kazu: thanks
09:26:42 <szlin> any other topics?
09:26:48 <szlin> 3
09:26:50 <szlin> 2
09:26:50 <szlin> 1
09:26:53 <szlin> #topic Software update
09:27:26 <szlin> kazu: do you have any updates on this topic?
09:27:29 <kazu> Sorry, I could not get the detailed info from Suzuki-san but,
09:27:36 <kazu> [ON-GOING] Add some basic security features
09:27:47 <kazu> This seems to be the current focus
09:27:59 <szlin> kazu: thanks.
09:28:00 <kazu> (from TSC minute)
09:28:05 <szlin> any other topics?
09:28:06 <szlin> 3
09:28:07 <szlin> 2
09:28:08 <szlin> 1
09:28:16 <szlin> #topic AOB
09:28:20 <szlin> any other business?
09:28:40 <szlin> 3
09:28:41 <szlin> 2
09:28:42 <szlin> 1
09:28:50 <szlin> #endmeeting