IRC logs for #cip for Thursday, 2019-10-03

*** rajm has joined #cip06:25
szlin#startmeeting CIP IRC weekly meeting09:00
brloggerMeeting 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
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
*** kazu has joined #cip09:00
szlin#topic rollcall09:00
*** brlogger changes topic to "rollcall (Meeting topic: CIP IRC weekly meeting)"09:00
bwhhi09:00
szlinplease say hi if you're around09:00
*** vidda has joined #cip09:00
kazuhi09:00
viddahi09:00
gavinlaihi09:00
szlin#topic AI review09:00
*** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"09:00
szlin1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san09:01
fujita[m]hi09:01
szliniwamatsu: are you around?09:01
wenshi09:01
szlinit seems like Iwamatsu-san is not around, I will skip this topic09:02
kazuszlin He is not in our office, but probably working in another place09:02
szlinkazu: thank you for your information09:02
szlin2. Test LTS (pre)releases directly – patersonc09:02
szlinpatersonc: are you around?09:02
*** masashi910 has joined #cip09:03
*** iwamatsu_ has joined #cip09:03
*** pave1 has joined #cip09:03
iwamatsu_hi all.09:03
szlin3. Move cip-core repo to cip-project/cip-core - kazu09:03
pave1hi09:03
masashi910hi09:03
kazuszlin done https://gitlab.com/cip-project/cip-core/cip-pkglist09:03
szliniwamatsu: pave1:  (wave09:03
szlinkazu: thank you very much09:03
szlin4. Review the proposal from Kudo-san - Kernel team09:04
szlinPavel reviewed it.09:04
szlinFor now, we are discussing with SoC vendor. Thanks to Jan's information.09:04
szlinmasashi910: do you have any update on this AI?09:04
patersonchi09:05
masashi910At this moment, I have no update from my side. I would like to know the next step.09:05
patersoncYep09:06
patersoncSorry I'm late.09:06
szlinpatersonc: no worry :)09:06
patersoncFor my AI, I'm still waiting for feedback.09:06
pave1patersonc: Feedback on testing of stable -rc releases?09:07
patersoncpave1: Yep.09:07
patersoncIs the approach I'm going with suitable?09:07
szlinmasashi910: next step is to wait for feedback with Xilinux, and we can start to merge codes afterward09:07
pave1patersonc: (they are discussing Xilinx now, lets wait).09:07
szlinpave1: ^ do you have any comments09:08
pave1szlin: Xilinx merge?09:09
szlinyes09:09
pave1szlin: Seems doable from my side. Next steps were outlined in the email..09:09
szlinpave1: thanks, I will keep this AI09:09
szlinmasashi910: is that ok for you?09:09
pave1szlin: Identifying what is really needed for basic system was on the list...09:10
pave1szlin: and moving neccessary parts from starging to kernel proper in the mainline would be good steps.09:10
szlinpave1: indeed.09:10
masashi910The next step provided by Pavel-san is quite reasonable.09:10
iwamatsu_pave1: if your are OK, please add me to discuss xilinx (to CC)?09:10
masashi910My question is if Xilinx does not respond, or does not cooperate with us, what happens.09:11
iwamatsu_pave1: if you are discussing by email.09:11
pave1iwamatsu: I thougth I'm copying cip-dev lists; that discussion was meant to be public.09:11
iwamatsu_pave1: Oh, OK. thanks.09:12
szlinmasashi910: let's discuss after the meeting, let's check the AI first :)09:12
szlinsince Iwamatsu-san is here, I will back to the AI which belongs him09:12
szlin1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san09:12
masashi910Sure! Thanks.09:12
szliniwamatsu: do you have any updates on this AI?09:13
szliniwamatsu: are you around?09:14
iwamatsu_szlin: I have almost completed this work. Now testing.09:14
szliniwamatsu_: thank you, I will keep this AI09:14
szlin2. Test LTS (pre)releases directly – patersonc09:14
szlinpatersonc: do you have any update on this AI?09:14
patersoncI'm just waiting to see if there is any more feedback before continuing with this09:15
szlinpatersonc: I see, thank you.09:15
szlin#topic Kernel maintenance updates09:15
*** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"09:15
szlinIwamatsu-san released 4.19.75-cip1109:16
szlin#info https://lists.cip-project.org/pipermail/cip-dev/2019-September/003340.html09:16
szlinPavel released 4.4.190-cip36-rt25 and 4.19.72-cip10-rt309:16
szlin#info https://lists.cip-project.org/pipermail/cip-dev/2019-October/003394.html09:16
szlin#info https://lists.cip-project.org/pipermail/cip-dev/2019-October/003393.html09:16
szliniwamatsu_: pave1: do you have any updates?09:16
patersoncWe need a better way to view results etc.09:16
patersoncProbably best to use something like KernelCI09:16
iwamatsu_pave1: thanks for your work.09:16
pave1I reviewed 4.19.76...09:16
iwamatsu_szlin: I reviewed 4.4.16809:17
szliniwamatsu_: pave1: thank you for your work09:17
iwamatsu_patersonc: +109:17
szlinany other topics?09:18
szlinpatersonc: that means we need to setup kernelCI09:18
szlinpatersonc: it might related to testing, I will jump to next topic09:19
szlin309:19
szlin209:19
szlin109:19
szlin#topic Kernel testing09:19
*** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"09:19
patersoncszlin: Which I've already instructed LF to do.09:19
pave1patersonc: Big thanks for testing LTS prerelases directly.09:20
patersoncThe LAVA master had some issues yesterday where it wasn't processing jobs.09:20
szlinpatersonc: thank you :D09:20
patersoncI was debugging it last night. Still ongoing.09:20
pave1patersonc: I have not figured out how to tell which -rc is being tested, but I'm sure I'll find out eventually :-).09:20
patersoncHave an issue where one of the jobs won't end, blocking the RZ/G1E board09:20
patersoncSo any CI runs will eventually time out09:21
patersoncpave1: 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
pave1patersonc: Aha, thanks, good to know.09:21
patersoncIn other news...09:22
patersoncI'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 complete09:22
patersoncThis should speed up the total time.09:23
patersoncSee https://gitlab.com/cip-project/cip-kernel/linux-cip/pipelines/86158976 for an example09:23
patersoncThat's probably it from me today.09:23
patersoncAgain, sorry for the issues with the LAVA master09:23
patersoncI'll try and upgrade to the newest LAVA next week, hopefully that'll make it more stable09:23
szlinany other topics?09:24
szlin309:24
szlin209:24
szlin109:24
pave1patersonc: That sounds like a good idea. It also means that we'll see "arm6409:24
szlin#topic CIP Core09:24
*** brlogger changes topic to "CIP Core (Meeting topic: CIP IRC weekly meeting)"09:24
pave1patersonc: tests failed" and not "all tests failed" ... which looks better.09:24
kazu1. I've updated PDP (v2.1), I'll get the final confirmation in cip-members about this09:24
kazuhttps://docs.google.com/document/d/1Ce4G6cTIY3IGXESlJQfVZ9r-V0kOPkxKDocpb4Ob_AY/09:24
patersoncpave1: Agreed.09:24
kazuDiscussions toward the package proposal in CIP security WG are now on-going09:25
kazu2. Regarding Debian 8 packages, Toshiba & Renesas shared the package list that they want to maintain longer term (in cip-members)09:25
kazuI'm agree that CIP Core keep maintenance of Tiny profile (deby) for Debian 8, but the problem is maintenance of source packages09:25
kazuBefore we propose this info to CIP, it would be better to get cost estimation from Debian ELTS09:25
kazu3. Planning to hold a CIP Core WG meeting during ELCE, please reply in Doodle if you are interested in09:26
kazuNo other update from me09:26
szlinkazu: thanks09:26
szlinany other topics?09:26
szlin309:26
szlin209:26
szlin109:26
szlin#topic Software update09:26
*** brlogger changes topic to "Software update (Meeting topic: CIP IRC weekly meeting)"09:26
szlinkazu: do you have any updates on this topic?09:27
kazuSorry, I could not get the detailed info from Suzuki-san but,09:27
kazu[ON-GOING] Add some basic security features09:27
kazuThis seems to be the current focus09:27
szlinkazu: thanks.09:27
kazu(from TSC minute)09:28
szlinany other topics?09:28
szlin309:28
szlin209:28
szlin109:28
szlin#topic AOB09:28
*** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"09:28
szlinany other business?09:28
szlin309:28
szlin209:28
szlin109:28
szlin#endmeeting09:28
brloggerMeeting ended Thu Oct  3 09:28:50 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:28
brloggerMinutes:        https://irclogs.baserock.org/meetings/cip/2019/10/cip.2019-10-03-09.00.html09:28
brloggerMinutes (text): https://irclogs.baserock.org/meetings/cip/2019/10/cip.2019-10-03-09.00.txt09:28
brloggerLog:            https://irclogs.baserock.org/meetings/cip/2019/10/cip.2019-10-03-09.00.log.html09:28
*** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/"09:28
szlinthank you all09:28
kazuThank you09:29
iwamatsu_thanks09:29
masashi910Thanks!09:29
szlinkazu: could you invite suzuki-san to join the meeting next week?09:29
pave1thank you!09:29
kazuszlin OK, I will ask09:29
fujita[m]thank you09:30
szlinkazu: thank you09:30
pave1Minutes do not seem to be available?09:31
pave1Neither of the links from brlogger works for me :-(09:31
pave1Patersonc: is there some easy way to retrigger the tests?09:32
pave1patersonc: for example https://gitlab.com/cip-project/cip-kernel/linux-cip/pipelines/86143896 was cancelled, but it would be interesting to re-run the tests...09:33
szlinpave1: it works now.09:34
szlinI mean, meeting minutes09:34
pave1szlin: Thansk! Yes, it works now. I guess it needs few seconds for processing.09:35
szlinpave1: do you have any suggestion with current situation in xilinux?09:35
patersoncpave1: Sorry, I'll be back in 509:36
szlinIn case they don't reply us, just as Kudo-san mentioned.09:36
pave1iwamatsu: my mails on Xilinx mpsoc should be on cip-dev, in "Xiling MPSOC -- was Re:  CIP IRC weekly meeting today" thread09:38
pave1iwamatsu: Sorry for spelling mistake.09:38
masashi910SZ-san, we started the discussion with Xilinx thanks to Jan-san.09:39
pave1iwamatsu: There's additional thread from "Jan Kiszka" that was not cc-ed to cip-dev.09:39
szlinmasashi910: yes, I've received the reply few hours ago09:40
masashi910Also I understand that the involvement of Xilinx kernel team would be much better.09:40
masashi910Our intention is, however, to start the contribution from Mainline to CIP in parallel with this discussion with Xilinx folks.09:41
*** kazu has quit IRC09:41
masashi910Because it may take a long time for Xilinx to decide whether they may want to cooperate with us.09:41
szlinpave1: do you have any concern to merge the codes from Cybertrust before confirming with Xilinux?09:42
pave1szlin: From my side it looks like reasonable way forward.09:43
masashi910Do you think the Xilinx involvement  is the gating factor?09:43
szlinpave1: sure, let's do it.09:43
szlinmasashi910: No.09:43
pave1szlin: Of course, it all depends on how patches look like.09:43
masashi910szlin: Thanks. I am relived. :)09:43
szlinpave1: thank you.09:43
patersoncpave1: I'm back. I'll chat to you once the xilinx discussion is done09:44
masashi910s/relived/relieved/09:44
pave1szlin: But promoting patches from staging to mainline proper and separating basic changes needed for boot is not something that needs Xilinx involvement.09:44
szlinmasashi910: thank you for your understanding, let's move forward :)09:44
masashi910pave1: Definitely. Their involvement in that case is needed. I agree.09:45
masashi910szlin: Thanks!09:45
pave1masashi910: I was trying to say that you can submit patches to mainline, too. It does _not_ need Xilinx involvement.09:46
pave1masashi910: Except they probably need to be cc-ed, let me check the maintainers :-).09:46
masashi910pave1: I see. Regarding this, I would like to continue to discuss with you. In somehow, there might be areas SoC vendors should be involved.09:48
masashi910pave1: Anyway, thanks for your consideration.09:48
masashi910So, thanks all for the discussion for code contribution. I am leaving today.09:49
pave1masashi910: Of course, if you can get SoC vendor involved, that's a good thing :-).09:49
masashi910pave1: Thanks for your comments! Very helpful!09:50
pave1masashi910: You are welcome, good luck with the project.09:50
masashi910pave1: Thanks!09:50
pave1patersonc: It seems channel is ours :-)09:53
*** masashi910 has quit IRC09:53
patersoncpave1: Wooo09:56
patersoncThere is a way to re-submit jobs, yes09:56
patersoncBut maybe you don't have the power?09:57
patersoncIf you go to the pipeline screen: https://gitlab.com/cip-project/cip-kernel/linux-cip/pipelines09:57
patersoncIf a pipeline wasn't successful there will be a "restart" button on the right.09:58
patersoncA circular arrow09:58
pave1Aha, I see it.09:58
patersoncIf you go into the pipeline itself you can also do this on a per job basis09:58
pave1Aha, I wsa at the pipeline itself, and did not see the button.09:59
patersoncBoth options only retry jobs that didn't complete - no need to re-run jobs that were successful09:59
pave1hmm. Now I see it even on the pipeline itself.10:00
patersoncpave1: You'll find from pipeline 86143896 that it will fail. The tests on the G1E boards won't be able to run due to the problems I mentioned earlier10:00
pave1Aha.10:00
patersoncThe rest of the boards will be tested though10:00
*** toscalix has joined #cip10:01
patersoncFeel free to run it. I just cancelled it last night because I was doing lots of reboots on the lava master10:01
pave1Ok, let me try to run it anyway. If it fails elsewhere it will be good to know.10:01
pave1Is it safe to queue more than one job for testing?10:01
pave1afc10:02
patersoncSure10:02
patersoncSure. Just the more that are running the bigger the queue will be :)10:05
patersoncpave1: Maybe the job will pass - LAVA ignores the job request because I put the RZ/G1E board into retirement.10:11
patersoncHuzzah. LAVA master is back up and running properly.10:15
pave1patersonc: Yep, now it says passed. Thanks!10:18
pave1patersonc: But there's like 60 minutes timeouts on the jobs, so if I queue way too many, eventually it will timeout and fail, right?10:18
patersoncYep10:19
patersoncHopefully an hour is enough though - although we'll have to rethink it when we start running LTS tests etc.10:20
patersoncSome of them take an hour on their own10:20
patersoncs/LTS/LTP10:20
pave1patersonc: Yes. Maybe running _such_ long tests only makes sense on manual request.10:21
pave1patersonc: Are we running realtime tests (cyclictest?) at the moment?10:22
patersoncpave1: Not yet. I was working on it before all the LAVA master issues.10:24
pave1patersonc: That makes sense. Thanks!10:24
patersoncAt the moment we're running a boot test and the spectre/meltdown checker test10:24
patersoncTo be honest, if we're running other tests, maybe we don't also need a boot test :)10:25
patersoncWe'll get there10:25
patersoncI just wish I could work on this 100% of the time, rather than about 10%10:25
pave1patersonc: And I guess spectre/meltdown test would not be the most important test I'd select.10:26
pave1patersonc: But knowing that the board boots is always good thing.10:27
patersoncIndeed10:28
pave1bye for now...10:31
patersoncttfn10:38
*** vidda has quit IRC10:44
*** pave1 has quit IRC10:51
*** masashi910 has joined #cip12:09
*** masashi910 has quit IRC12:13
*** toscalix has quit IRC18:10
*** iwamatsu_ has quit IRC20:06
*** iwamatsu_ has joined #cip20:18
*** iwamatsu_ has quit IRC20:30
*** rajm has quit IRC22:06
*** iwamatsu_ has joined #cip22:19
*** iwamatsu_ has quit IRC23:59

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!