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

*** yoshidak has joined #cip04:18
*** yoshidak has quit IRC04:23
*** yoshidak has joined #cip04:37
*** yoshidak has left #cip04:38
*** rajm has joined #cip07:39
*** therisen has joined #cip08:20
*** rajm has quit IRC08:36
*** rajm has joined #cip08:43
*** suzuki76 has joined #cip08:57
*** pave1 has joined #cip08:57
*** masashi910 has joined #cip08:58
*** kazu43 has joined #cip09:00
szlin#startmeeting CIP IRC weekly meeting09:00
brloggerMeeting started Thu Nov 21 09:00:03 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:00
*** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"09:00
szlin1. Test LTS (pre)releases directly - patersonc09:00
szlin== Quote from patersonc ==09:01
szlinEverything is working and we've found a few issues that have been reported to stable.09:01
szlinRemaining tasks are:09:01
szlin* Add a way to identify in GitLab what commit is being tested.09:01
szlin* Move everything from cip-playground to cip-project/cip-testing.09:01
szlin2. Ask KernelCI for recommendations on what tests to run - patersonc09:01
szlin3. Create a way/process to run LTP only for release tests - patersonc09:01
szlin== Quote from patersonc ==09:01
szlinTechnically this is now possible due to updates to linux-cip-ci.09:01
szlinWe just need to decide the best method to define 'release' testing.09:01
szlinI'll propose a method of how to do this to the maintainers soon.09:01
szlin4. Combine rootfilesystem with kselftest binary - Iwamatsu-san09:01
szlin== Quote from Iwamatsu-san ==09:01
szlinI am working yet. please keep this A.I.09:01
szlin5. Document a process on how to add tests to the CIP test setup - patersonc09:01
szlin== Quote from patersonc ==09:01
szlinNo updates09:01
szlin6. Split out non-Kernel config sections from gitlab-ci.yml - patersonc09:01
szlin== Quote from patersonc ==09:01
szlinPrototype complete. I just need to move from cip-playground to cip-testing.09:01
szlin7. Do we want to go with the current approach where GitLab CI is run ‘out of tree’- Kernel team09:02
szlinI think this AI is done by today09:02
szlinpatersonc: pave1: correct me if I'm wrong09:02
pave1I'm not sure there were any decissions.09:03
pave1Testing "out of tree" is okay with me.09:04
patersoncI think the consensus is that the new approach will be okay09:04
pave1It is definitely okay with me :-).09:04
szlin8. Ask RT admin to put CIP RT kernel to their CI-RT - Kernel team09:04
szlinI think this AI belongs to Iwamatsu-san he updated the status last week09:06
szlinpave1: ^ do you have any news?09:06
pave1News about CI-RT or general updates?09:07
szlinthis one "Ask RT admin to put CIP RT kernel to their CI-RT"09:07
szlinif not, I will leave it to let Iwamatsu-san to update.09:08
pave1I believe Iwamatsu is right person to do that :-).09:08
szlinpave1: thanks09:08
szlin#topic Kernel maintenance updates09:08
*** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"09:08
szlin== Quote from Iwamatsu-san ==09:08
szlinI reviewed v4.4.201, 202-rc and v4.19.85-rc.09:08
pave1I'm working on 4.19.85 reviews and applying Renesas patches from the list.09:08
szlinI've sent MR for kernel-sec, and I will send new MR to fix an error in previous MR.09:09
szlinpave1: thanks09:09
szlinany other topics?09:09
szlinwens: do you have any updates?09:09
wenswork in progress for classify-failed-patches09:09
szlinwens: thanks.09:10
pave1Actually, there was debate of "no patches from us being backported to 4.19-stable".09:10
pave1If I know what to backport I can try to do that.09:10
pave1Maybe we can discuss after the meeting?09:10
szlinpave1: sure09:11
szlinpave1: thanks.09:11
szlin#topic Kernel testing09:11
*** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"09:11
szlinpatersonc: the floor is yours09:11
patersoncI've been working to implement the gitlab-ci.yaml files as discussed. It's pretty much ready now, hopefully I'll get it finalized by next meeting.09:11
patersoncOnce done I'll then start enabling LTP tests etc. in anger09:12
patersoncBut maybe just for RZ/G1M for now due to lack of other boards.09:12
pave1As soon as .yml with include is ready, I'll be happy to commit it to 4.4 and 4.19 :-)09:12
patersoncI maybe be able to add a second RZ/G2M board to lab-cip-renesas soon.09:12
patersoncThanks pave109:12
patersoncI think that's about it for me09:13
szlinpatersonc: pave1: thank you all09:13
szlinany other updates?09:13
szlin#topic CIP Core09:13
*** brlogger changes topic to "CIP Core (Meeting topic: CIP IRC weekly meeting)"09:13
kazu431. Debian ELTS for jessie packages: Approved by TSC, discussing the way for cost reduction in members ML09:13
kazu43Please join this if you have any ideas09:13
kazu432. PDP updated: "Security criteria" information is now automatically set by the script09:14
kazu43Now ready for proposal (again)09:14
kazu43Security WG almost fixes their proposal, it will be done soon :-)09:14
kazu433. WIP: Adding script to submit basic tests to LAVA master (to the both profiles)09:14
kazu43Probabry will ask some helps to finalize this task :-)09:14
kazu43That all from me09:15
szlinkazu43: thanks.09:15
szlinany other topics?09:15
patersonckazu43: Sure09:15
patersoncLet me know09:15
kazu43patersonc thanks09:15
szlinpatersonc: thank you.09:15
szlin#topic Software update09:15
*** brlogger changes topic to "Software update (Meeting topic: CIP IRC weekly meeting)"09:15
suzuki76Recently, I'm preparing a script to make development environment (demo environment) of CIP software update mechanism.09:15
suzuki76It's almost done.09:15
suzuki76In the next step, I plan to make a subgroup of SW Updates WG in cip-project GitLab and make a repository for publishing the script.09:15
suzuki76In addition, I plan to manage our WG's tasks and their progress in the subgroup's issue board.09:16
suzuki76That's all from our WG.09:16
szlinsuzuki76: thanks.09:16
szlinany other topics?09:16
patersonckazu43: What are the actual packages we've asked ELTS to support?09:16
szlin#topic AOB09:16
*** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"09:16
szlinany other business?09:16
brloggerMeeting ended Thu Nov 21 09:16:44 2019 UTC.  Information about MeetBot at . (v 0.1.4)09:16
brloggerMinutes (text):
*** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at"09:16
szlinthank you all09:16
pave1thank you!09:16
masashi910thank you!09:17
suzuki76Thank you!09:17
kazu43patersonc The package list is in the recent TSC meeting docs09:17
fujita[m]thank you!09:17
*** suzuki76 has quit IRC09:17
patersonckazu43: Okay09:17
pave1szlin: If there's a list of patches to be backported to 4.19 (and also 4.4) somewhere, I can start taking patches from the list.09:18
pave1I guess classify-failed-patches is expected to contain that?09:18
szlinpave1: yes, will do, thank you very much09:18
pave1ok, thanks!09:19
kazu43patersonc busybox (Renesas/Toshiba), binutils (Renesas), gcc-4.9(libgcc) (Toshiba), glibc (Renesas/Toshiba), openssl (Renesas/Toshiba), openssh (Toshiba), shadow (Toshiba)09:19
wensthe coverage for classify-failed-patches at the moment is kind of poor. it only sees singular (not in a series) patches from the stable ML09:19
wensneither does it know what CIP cares about; it simply lists patches it finds (matched by subject) that haven't been applied09:20
patersonckazu43: Thanks09:21
wensI could very much use everyone's input on this. For now I'm improving the coverage and accuracy of the matching mechanism09:21
*** masashi910 has quit IRC09:21
*** masashi910 has joined #cip09:21
szlinwens: thanks.09:25
pave1Well, automatically doing the right thing might not be trivial.09:27
pave1OTOH I suspect there is a lot of patches that could be backported...09:28 if you see something that looks relevant, I can try backporting.09:28
*** kazu43 has quit IRC09:29
*** pave1 has quit IRC10:15
*** masashi910 has quit IRC10:36
*** masashi910 has joined #cip13:01
*** masashi910 has quit IRC13:08
*** therisen has quit IRC16:16
*** tpollard has quit IRC17:11
*** alicef has quit IRC21:12
*** gavinlai has quit IRC21:12
*** alicef has joined #cip21:13
*** gavinlai has joined #cip21:14
*** rajm has quit IRC23:03

Generated by 2.15.3 by Marius Gedminas - find it at!