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

« Wednesday, 2019-07-10 Index Friday, 2019-07-12 »
*** rajm has joined #cip06:52
*** JohnsonCH_Chen has joined #cip07:33
*** JohnsonCH_Chen has quit IRC07:33
*** yamamodo has joined #cip07:35
*** yamamodo has quit IRC07:47
*** yamamodo has joined #cip07:47
*** yamamodo has quit IRC07:49
*** yamamodo has joined #cip07:49
*** yamamodo has quit IRC08:22
*** toyooka_ctj has joined #cip08:28
*** yamamodo has joined #cip08:31
*** vidda has joined #cip08:56
*** sangorrin has joined #cip08:57
szlin#startmeeting CIP IRC weekly meeting09:00
brloggerMeeting started Thu Jul 11 09:00:07 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
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
iwamatsuhi09:00
sangorrinhi09:00
viddahi09:00
toyooka_ctjhi09:00
szlin#topic AI review09:00
*** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"09:00
szlin1. Provide the script for CIP kernel config collection - bwh09:00
szlin#link https://lists.cip-project.org/pipermail/cip-dev/2019-June/002506.html09:00
*** pave1 has joined #cip09:01
sangorrinNote: I plan to integrate that with the CVE scripts09:01
sangorrini.e.: get issues that affect your kernel for this configuration09:01
szlinsangorrin: do you mean CVE scripts & config collection script?09:01
bwhszlin: This is mostly done; I still need to add a rule to merge the lists of source files together09:02
szlinfair enough09:02
szlinbwh: thanks, I will keep this AI.09:02
sangorrinszlin: yes09:02
szlinsangorrin: got it, thanks.09:03
yamamodohi09:03
pave1ho09:03
szlin2. List real time kernel questions to ask Daniel Wagner - szlin09:03
pave1hi09:03
szlin-> Done09:03
patersonchi09:03
szlin3. Try updating CIP RT kernel to 4.19.50 - Pavel09:03
szlin#link https://lists.cip-project.org/pipermail/cip-dev/2019-June/002548.html09:03
pave1So.. I released update... and I got feedback that I numbered the version wrong.09:04
pave1I'll need to fix that one.09:04
szlin#action Fix release number in CIP RT kernel - pavel09:04
szlinpave1: thanks09:04
pave1But my testing shows some high latencies I'm currently debugging.09:04
szlinpave1: we can discuss RT testing in CIP kernel & testing f2f meeting.09:05
szlin4. Work out a solution for LAVA master backups - patersonc09:06
patersoncNot done09:07
szlinpatersonc: thanks, I will keep this AI09:07
szlin#topic Kernel maintenance updates09:07
*** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"09:07
sangorrinI sent a "few" patches to Ben (sorry if there are too many)09:07
pave1I finished review of 4.19.57, and reviewed 4.19.58. (Plus I'm having realtime fun).09:08
iwamatsuszlin: I reviewed 4.4.164, and I updated base of 4.4.y and 4.19.y for release.09:09
bwhsangorrin: No, not too many09:09
szlinthank you!09:09
iwamatsuI am testing on LAVA updated kernel.09:09
patersonciwamatsu: Great09:09
szliniwamatsu: Please let me know if you need any assistence in relesing kernel.09:10
patersonciwamatsu: Sorry about the healthcheck issues on G2E. I've added a patch to fix it. I'll try and update the master today09:10
iwamatsuszlin: OK, thanks for your help!09:10
szlinI'm working with yamamodo in failed patches.09:11
iwamatsupatersonc: great! thank you!09:11
yamamodo:)09:11
szlinany other comments?09:12
patersonco/09:12
szlin#action Send invitation email to cip-members for CIP kernel and testing f2f meeting in OSS-J - szlin09:12
szlinpatersonc: please go ahead09:12
patersoncIs there any chance my gitlab-ci.yml patches could be reviewed/merged before OSS-J?09:12
patersonchttps://patchwork.kernel.org/project/cip-dev/list/?submitter=15474109:13
pave1patersonc: Yes, I believe I should just do that.09:13
patersoncThey could also be added to the -rt branches, as they are only doing boot tests atm09:13
pave1Agreed.09:13
patersoncThanks pave109:14
szlin#action Review "gitlab-ci.yml" patches before OSS-J - pavel09:14
szlinpave1: thank you.09:15
szlin309:15
szlin209:15
szlin109:15
szlin#topic Kernel testing09:15
*** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"09:15
szlinpatersonc: the floor is yours09:15
patersoncWooo09:15
patersonc#info Mentor are still working on adding the two Siemens boards:09:15
patersonc#link https://lava.ciplatform.org/scheduler/device/x86-SIMATIC-IPC227E09:15
patersonc#link https://lava.ciplatform.org/scheduler/device/Altera-Terasic-Deo-Nano-0109:15
patersonc#info At OSS-J we will have a browser open on a RZ/G2M platform that can be used to show the GitLab CI / LAVA testing websites.09:15
patersonc#info szlin is trying to set up a Kernel maintenance/testing meeting at OSS-J.09:15
patersoncAgenda (WIP): https://docs.google.com/document/d/1_GI-2YDm-8TL4h-L-rO6vD4-fHFK1SLrldrfsgZw0uM/edit#09:16
patersoncCan people fill in the doodle if they want to attend? https://doodle.com/poll/473sudmu7hrvqqv809:16
patersoncThat's it from me this week, unless there are any questions?09:16
szliniwamatsu: pave1 bwh ^ please fill in when you're available.09:17
szlinany other comments?09:18
szlin309:18
szlin209:18
szlin109:18
szlin#topic CIP Core09:18
*** brlogger changes topic to "CIP Core (Meeting topic: CIP IRC weekly meeting)"09:18
sangorrin#info I am just testing the deployment of Deby from Gitlab to AWS S3 (https://gitlab.com/cip-project/cip-core/deby/-/jobs/249491414)09:19
sangorrinthat's all09:19
bwhszlin: I'm not going to OSS-J09:19
szlinsangorrin: thank you09:19
szlinbwh: could you join the meeting via zoom?09:19
pave1szlin: Ok, will do. Note that I'll not be in Japan, so it will be some kind of remote access.09:20
iwamatsuszlin: OK, I will add to doodle.09:20
szlinpave1: no problem, we will setup it.09:20
szliniwamatsu: thank you09:20
szlin== Quote from Kazu ==09:20
szlin* (WIP) Creating document about CIP-Core package decision process [60%]09:20
szlin* (WIP) Implementing the script to resolve package dependencies automatically [20%]09:20
szlin* Arrange CIP Core / testing WG F2F meeting on July 15th (11 attendees)09:20
bwhszlin: Not sure09:20
pave1szlin: thank you!09:20
szlin====09:20
yamamodo3q09:21
szlinany other comments?09:21
szlin309:22
szlin209:22
szlin109:22
szlin#topic Software update09:22
*** brlogger changes topic to "Software update (Meeting topic: CIP IRC weekly meeting)"09:22
sangorrin#info Demo is almost ready, I created a small double-side leaflet to explain the demo and the workgroup to participants.09:22
szlinsangorrin: nice09:22
sangorrin#info I updated the wiki page also, we need to decide the next roadmap during the F2F meeting09:22
szlinany other comments?09:23
szlin309:23
szlin209:23
szlin109:23
szlin#topic AOB09:23
*** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"09:23
szlinany other business?09:23
bwhI still want to know if I can remove old kernel configs for 4.1909:24
pave1patersonc: I'd like to chat after the meeting if possible.09:24
bwhIf we don't do that, it will make more work for the kernel maintainers as they will have to review stable changes that don't affect members09:24
patersoncpave1: Sure09:24
pave1patersonc: Thanks!09:24
patersoncbwh: I've updated the renesas configs, so please keep09:25
szlinbwh: I've asked my counterpart to update the config before this week, and thus I can update the MR afterward.09:25
sangorrinI was planning to answer soon. I think that the config I sent specifically for 4.19 is the only needed from Toshiba. I will confirm tommorrow09:25
bwhpatersonc: acknowledged09:25
patersoncThanks09:26
sangorrin→ tomorrow09:26
bwhsangorrin: thanks09:27
szlin309:27
szlin209:27
szlin109:27
szlin#endmeeting09:27
brloggerMeeting ended Thu Jul 11 09:27:27 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:27
brloggerMinutes:        https://irclogs.baserock.org/meetings/cip/2019/07/cip.2019-07-11-09.00.html09:27
brloggerMinutes (text): https://irclogs.baserock.org/meetings/cip/2019/07/cip.2019-07-11-09.00.txt09:27
brloggerLog:            https://irclogs.baserock.org/meetings/cip/2019/07/cip.2019-07-11-09.00.log.html09:27
*** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/"09:27
szlinthank you all09:27
iwamatsuthank you!09:27
pave1Thank you!09:27
laurence-thanks szlin09:27
yamamodothanks you09:27
toyooka_ctjthank you!09:27
laurence-bwh: what's the impact of keeping some members old config files and removing others? does that matter at all?09:27
sangorrinthanks09:28
bwhlaurence-: If any of those config files are not really being used, it is likely to mean wasted effort in reviewing stable changes. Of course, that depends on how much they overlap with the config files that really are used.09:30
laurence-OK, so a response from each member is needed really, thanks09:32
pave1patersonc: First, thanks for the pointers.09:33
*** sangorrin has left #cip09:34
pave1https://lava.ciplatform.org/results/1825/0_cyclictest is actually one of my experiments.09:34
pave1But problem with the cyclictest is that it cluctuates a lot...09:35
pave1fluctuates.09:35
pave1...even non-realtime kernels can have maximum of 167 usec (which is pretty good).09:35
pave1So it seems we'd need longer test and probably some kind of background load.09:35
*** vidda has quit IRC09:36
pave1I tried to modify the tests, but Lava is not my friend (yet).09:36
pave1So I'll need some help there...09:38
patersoncLet me have a go09:43
patersoncpave1: hello11:33
patersoncdo you have a link to a rt kernel?11:34
pave1Hello, still here.11:34
pave1Sources or binary?11:34
patersoncbinary11:35
pave1Will binary for iwg20m do the trick?11:36
pave14.19 based?11:36
patersoncur11:37
patersoncSure11:37
patersoncwhatever you've been testing with cyclictest11:37
pave1Let me build it.11:38
patersoncIs http://atrey.karlin.mff.cuni.cz/~pavel/outgoing/cip2/uImage just a normal build?11:39
pave1I think so, yes.11:39
pave1It can be seen on first few lines on kernel boot -- it says kernel version and "RT" in the version if realtime is enabled.11:39
patersoncTrue11:40
pave1So I'm building 4.19.50 with _RT_FULL for iwg20m.11:40
patersoncGreat11:41
patersoncI've created a test for cyclictest + hackbench11:41
patersonchttps://lava.ciplatform.org/scheduler/job/196411:42
patersoncThe results are shocking with the non-rt kernel11:42
pave1Great!11:42
pave1I've put rt build on http://atrey.karlin.mff.cuni.cz/~pavel/outgoing/cip2/uImage11:42
patersoncProbably some tweaking to be done with test params, but it'll be interesting to see how it goes with a RT kernel11:42
patersoncI assume the dtb is the same?11:43
pave1I've updated it, too. But I assume it is same.11:43
patersoncTest running: https://lava.ciplatform.org/scheduler/job/197211:44
pave1I've started running tests on T40p. ... it seems to be halfway usable.11:44
patersoncT40p?11:45
pave1Fairly old IBM thinkpad... but someone had good results on T41 so I tried it.11:47
patersonc:)11:48
tpollardonly 16 years old....11:48
patersoncResults are in from that RT build: https://lava.ciplatform.org/results/1972/0_cyclictest_plus_hackbench11:49
patersoncCompared to non-RT build: https://lava.ciplatform.org/results/1964/0_cyclictest_plus_hackbench11:49
pave1non-RT results are probably wrong.11:50
pave1CONFIG_HIGH_RES_TIMERS=y11:50
pave1high res timers are needed for useful results.11:50
patersoncThe iwg20m does have highres counters if you need them11:52
pave1Yes... CONFIG_HIGH_RES_TIMERS=y needs to be enabled in kernel config or cyclic test complains and produces invalid results like that11:53
pave1Thanks for the help, I'll need to go soon.11:54
patersoncOh you mean for the non-rt results above. Gotcha11:54
pave1Yep. min latency should be < 50 usec.11:55
patersoncThat's okay. If you have a non-RT kernel with the high res timers ON then that would be good to compare with job #197211:55
pave1So I have feeling that #1972 is wrong -- 1262 usec is way too much.11:56
patersoncYea11:57
patersoncThe configs for hackbench could probably be improved11:57
*** rajm has quit IRC12:01
pave1Yes.. there's a lot work left.12:01
*** rajm has joined #cip12:01
pave1I need to go, bye for now and thanks for the help!12:10
patersoncNo worries12:14
patersoncChat soon12:14
pave1:-)12:15
*** pave1 has quit IRC12:15
*** toyooka_ctj has quit IRC12:30
*** rajm has quit IRC16:47
laurence-Is there a list available anywhere to see all of the talks being given by CIP members at OSSJ ?19:19
laurence-I'm sure I have seen it.19:19
laurence-I guess there is https://docs.google.com/spreadsheets/d/1dwPxfHCkGDz0Nvk4mlZuB_ywh5CS1jw0KtmziyKtL4s/edit#gid=141678257019:20
*** rajm has joined #cip20:03
*** rajm has quit IRC22:05
« Wednesday, 2019-07-10 Index Friday, 2019-07-12 »

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