IRC logs for #cip for Thursday, 2019-11-14

*** yoshidak[m] has joined #cip01:46
*** masashi910 has joined #cip02:01
*** masashi91014 has joined #cip02:03
*** punit has quit IRC03:12
*** masashi910 has quit IRC03:59
*** masashi910 has joined #cip04:03
*** masashi910 has quit IRC06:36
*** masashi910 has joined #cip07:12
*** iwamatsu has joined #cip07:20
*** iwamatsu has quit IRC07:26
*** iwamatsu has joined #cip07:27
*** rajm has joined #cip07:49
*** masashi910 has quit IRC08:05
*** masashi910 has joined #cip08:06
*** masashi910 has quit IRC08:07
*** rajm has quit IRC08:08
*** masashi910 has joined #cip08:09
*** masashi910 has quit IRC08:16
*** masashi910 has joined #cip08:16
*** rajm has joined #cip08:37
*** suzuki93 has joined #cip08:55
*** pave1 has joined #cip08:56
*** kazu has joined #cip08:56
*** vidda has joined #cip08:59
szlin#startmeeting CIP IRC weekly meeting09:00
brloggerMeeting started Thu Nov 14 09:00:02 2019 UTC and is due to finish in 60 minutes.  The chair is szlin. Information about MeetBot at
brloggerUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
brloggerThe 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 rollcall09:00
*** brlogger changes topic to "rollcall (Meeting topic: CIP IRC weekly meeting)"09:00
szlinplease say hi if you're around09:00
szlin#topic AI review09:01
*** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"09:01
szlin1. Test LTS (pre)releases directly - patersonc09:01
szlinpatersonc: are you around?09:01
szlinI will skip Chris AI for now since he is not around09:02
szlin4. Investigate the RT test tools - Pavel09:02
pave1I can look more  into it, but I believe we should get cyclictest to work first.09:03
pave1It is the "default" one, way better than nothing... and I already have some experience with it.09:03
szlinpave1: thanks for the update, so this AI could be closed09:04
szlin5. Combine rootfilesystem with kselftest binary - Iwamatsu-san09:04
*** hungtran_renesas has joined #cip09:05
iwamatsuszlin: I do not finish yet. please keep this A.I.09:05
szliniwamatsu: thanks for the heads up09:05
szlin9. Ask RT admin to put CIP RT kernel to their CI-RT - Kernel team09:05
iwamatsuszlin: I do not get mail from RT-admin. I will contact to admin.09:06
szliniwamatsu: thank you for the update09:06
szlinI will keep this AI09:06
szlin10. Provide the CIP mini-summit slide with as a PDF file - Pavel09:07
szlinDone, Pavel just sent the email09:07
szliniwamatsu: can you provide the slide as well?09:07
pave1Yep, sorry for the delay.09:07
iwamatsuszlin: sure. I will do it soon.09:07
szliniwamatsu: thank you09:07
szlinI will integrate our slides.09:08
szlin#topic Kernel maintenance updates09:08
*** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"09:08
szlinIwamatsu-san released v4.4.199-cip39, v4.19.80-cip13, and v4.19.82-cip1409:08
szlinPavel released v4.19.72-cip10-rt409:08
pave1I am reviewing 4.19.83 and
szlinI reviewed and updated the data in kernel-sec repo.09:08
iwamatsuI reviewed v4.4.19809:09
wensI will update the data in classify-failed-patches this week09:09
szlinWens and I have some discussion in here [1]09:09
szlin#info [1]
szliniwamatsu: feel free to review it, thanks.09:09
iwamatsuszlin: Okay.09:10
szlinthank you all.09:10
szlinany other topics?09:10
wensto elaborate, the idea is to expand the coverage of classify-failed-patches09:10
szlinwens: thanks.09:11
szlin#topic Kernel testing09:11
*** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"09:11
szlinChris is not aorund, so do we have any other topics?09:11
szlin#topic CIP Core09:11
*** brlogger changes topic to "CIP Core (Meeting topic: CIP IRC weekly meeting)"09:12
kazu1. Generic profile: CI(Deploy) supported for hihope-rzg2m09:12
kazuNow handling issues about the format of rootfs image for LAVA test09:12
kazu2. Got the estimated cost for 7 Debian jessie packages requested by members (6,000 EUR / year)09:12
kazuThis is now under voting process in TSC09:12
kazu3. [WIP] Replacing profile specific kernel configs by the configs in cip-kernel-config09:12
kazu4. [WIP] Updating PDP helper scripts to use Debian package tags for security criteria09:13
kazuwill be finished soon09:13
kazuThat's all from me09:13
szlinkazu: thank you for your update09:13
pave1Actually, I'd like to comment on 3.09:13
szlinpave1: the  floor is yours09:14
pave1I believe it makes sense to base configuration of yocto project on what we have in cip-kernel-config,09:14
pave1and maybe synchronize changes back, too, but I'm not sure if it is good idea to directly link them.09:14
pave1Testing process uses cip-kernel-config, too, and there may be different requirements between testing and yocto build..09:15
kazupave1 "base configuration" means to split the current config to the base one + members extensions?09:16
szlinpave1: kazu: let's have further discussion after meeting.09:16
kazuszlin OK!09:17
szlinany other topics?09:17
szlin#topic Software update09:17
*** brlogger changes topic to "Software update (Meeting topic: CIP IRC weekly meeting)"09:17
suzuki93As I mentioned at the TSC meeting in this week, I added our WG's 2nd iteration roadmap to our WG's wiki page.09:17
suzuki93It's URL is
suzuki93Currently, I'm preparing development and testing environment to make easier to contribute to our WG for any developer.09:17
suzuki93That's all from SW Updates WG09:17
szlinsuzuki93: thanks.09:18
szlinany other topics?09:18
szlin#topic AOB09:18
*** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"09:18
szlinany other business?09:18
brloggerMeeting ended Thu Nov 14 09:19:08 2019 UTC.  Information about MeetBot at . (v 0.1.4)09:19
brloggerMinutes (text):
*** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at"09:19
szlinthank you all09:19
wensthank you09:19
pave1Thank you!09:19
masashi910thank you!09:19
kazuThank you09:19
suzuki93Thank you!09:19
fujita[m]thank you!09:19
pave1kazu: What I'm trying to say is that current configuration ("separate09:19
*** suzuki93 has quit IRC09:19
pave1config files for yocto") makes sense to me, and I'd keep it for now.09:20
pave1It is possible that configs will change too often or something like that....09:20
pave1..but I don't quite think so, so I believe duplicate configs will not be problem in practice.09:21
kazupave1 Thank you for your comment09:23
*** masashi910 has quit IRC09:23
kazupave1 actually, each profile have separate config file now09:24
kazuThe initial idea to use cip-kernel-config is to use the same kernel config between the two profiles09:25
kazuI also agree that... duplicate configs will not be problem in practice09:25
kazubut, it would be simple for us to use the single config in CIP from testing point of view (CIP Core image also will be tested in LAVA)09:29
pave1kazu: It is your area, so do what you believe is best; I just wanted to comment that I don't see great need for the configs to be shared. If it is easy to share them, it is obviously not a problem either.09:31
kazupave1 I got it, thanks. Actually it's not difficult to share them, so anyway will try once. it might be separated again if we find something better than sharing them :-)09:36
pave1Ok :-)09:37
kazuAlso, CIP Core probably doesn't want to change the existing kernel config in cip-kernel-config while it's tested in kernel team, so there is no concern of making frequent updates in cip-kernel-config at the moment09:39
kazuIf something should be changed from cip-kernel-config for CIP core specific reasons, we will have additional configs in CIP Core side (in metadata)09:40
pave1Ok, lets see how it works.09:42
*** vidda has quit IRC09:45
kazupave1 thank you09:46
*** kazu has quit IRC09:46
*** hungtran_renesas has quit IRC10:26
*** iwamatsu has quit IRC11:06
*** pave1 has quit IRC11:16
*** rynofinn has left #cip12:25
*** rynofinn has joined #cip12:35
*** cp has quit IRC12:51
*** dl9pf_home has quit IRC12:51
*** helmut has quit IRC12:51
*** mungaip[m] has quit IRC12:51
*** Gwaihir has quit IRC12:51
*** rajm has quit IRC12:51
*** tpollard has quit IRC12:51
*** laurence- has quit IRC12:51
*** alicef has quit IRC12:51
*** wens has quit IRC12:51
*** gavinlai has quit IRC12:51
*** thommey has quit IRC12:51
*** wagi has quit IRC12:51
*** lchlan has quit IRC12:51
*** fujita[m] has quit IRC12:51
*** szlin has quit IRC12:51
*** dl9pf has quit IRC12:51
*** bwh has quit IRC12:51
*** Guest38304 has quit IRC12:51
*** yoshidak[m] has quit IRC12:51
*** patersonc has quit IRC12:51
*** ironfoot has quit IRC12:51
*** rynofinn has quit IRC12:51
*** rynofinn has joined #cip12:54
*** rajm has joined #cip12:54
*** yoshidak[m] has joined #cip12:54
*** bwh has joined #cip12:54
*** Guest38304 has joined #cip12:54
*** laurence- has joined #cip12:54
*** alicef has joined #cip12:54
*** wagi has joined #cip12:54
*** tpollard has joined #cip12:54
*** fujita[m] has joined #cip12:54
*** mungaip[m] has joined #cip12:54
*** patersonc has joined #cip12:54
*** Gwaihir has joined #cip12:54
*** cp has joined #cip12:54
*** dl9pf_home has joined #cip12:54
*** szlin has joined #cip12:54
*** wens has joined #cip12:54
*** gavinlai has joined #cip12:54
*** helmut has joined #cip12:54
*** dl9pf has joined #cip12:54
*** thommey has joined #cip12:54
*** lchlan has joined #cip12:54
*** ironfoot has joined #cip12:54
*** toscalix has joined #cip14:51
*** rajm has quit IRC17:47
*** tpollard has quit IRC17:55
*** yoshidak[m] has quit IRC18:21
*** fujita[m] has quit IRC18:21
*** mungaip[m] has quit IRC18:21
*** patersonc has quit IRC18:21
*** toscalix has quit IRC18:29
*** rajm has joined #cip19:09
*** rajm has quit IRC23:04

Generated by 2.15.3 by Marius Gedminas - find it at!