IRC logs for #cip for Thursday, 2018-09-13

*** patersonc has joined #cip06:05
*** rajm has joined #cip07:04
*** rajm has quit IRC07:34
*** toscalix has joined #cip07:39
*** rajm has joined #cip07:49
*** Tzongyen_Lin has joined #cip07:59
*** rajm has quit IRC08:00
*** hungtran has joined #cip08:00
*** moxavictor has joined #cip08:00
*** rajm has joined #cip08:00
*** patersonc has quit IRC08:00
gavinlaiszlin has a meeting conflict today08:00
gavinlaiI will chair this meeting :)08:01
gavinlai#startmeeting08:01
*** sangorrin has joined #cip08:01
gavinlai#roll call08:01
bwhhi08:01
rajmhi08:01
sangorrinhello~08:01
gavinlaiplease say hi if you are here08:02
hungtranhi08:02
gavinlai#topic action item review08:02
gavinlaiaction item: Agustin will ping Ben for the feedback of git group account in kernel.org08:03
gavinlaibwh: any feedback of git group account in kernel.org?08:04
bwhI haven't asked yet. Does iwamatsu have a kernel.org account? It would be pointless to  have a group if no-one else can be in it yet.08:05
sangorrinApparently he doesn't08:06
sangorrinDaniel Wagner has one08:06
sangorrinprobably we will need to wait until the next maintainer(s) are approved08:07
sangorrinIs there any advantage in having the account in kernel.org instead of gitlab?08:08
gavinlaiok, let's move to next action item?08:08
bwhsangorrin: Well, I think it would be easier to just have it on Gitlab.08:08
bwhBut some people seem to think it looks more official if it's on kernel.org as well.08:08
bwh"it" =  the CIP kernel repository08:09
bwhgavinlai: OK08:09
sangorrinyeah, we should consult with the marketing team then ;)08:09
gavinlaiaction item: discuss the testing infra. including maintainer/admin at TSC meeting08:10
toscalixo/08:10
sangorringavinlai: I asked Ryan for permissions to use LAVA and KernelCI08:10
sangorrinhe said he had to upgrade LAVA, and then he will be sending tokens and calling for password exchanges08:11
gavinlaigot it08:12
sangorrinAnyway, it doesn't look like we can get admin permissions.. only enough to set our boards08:12
gavinlaiI see, thanks08:13
gavinlaiany other updates?08:14
gavinlai#topic kernel maintenance updates08:14
gavinlaimoxa team is working on sending our dts to mainline kernel08:15
gavinlai#link https://lkml.org/lkml/2018/8/30/113608:15
*** hungtran has quit IRC08:15
gavinlaithe TI employee suggests us to use phy-handle instead of phy_id which is deprecated.08:15
gavinlaiHowever, phy-handle is buggy on stable kernel 4.408:16
gavinlaimoxa team has sent patches to fix phy-handle problem08:16
gavinlaiwaiting for the review08:16
sangorrinIs it normal to submit one dts per board? I thought the dts would better be in the yocto meta layer or the openWrt kernel etc.08:16
sangorrinThanks for the phy-handle fixes08:18
sangorrinare you there gavinlai?08:21
gavinlaisangorrin: I have no idea right now08:21
gavinlaimaybe we can figure out is there any rule or guideline ofr this08:21
toscalixThe kernel released yesterday is the last one under Ben H. responsibility. We should focus some energy in the transfer to the following maintainer.08:21
sangorrinHopefully, Iwamatsu-san will be approved soon08:22
gavinlaiany action item for transfer?08:23
toscalixah, I see. I will raise the topic then in the next TSC meeting08:23
toscalixgavinlai: repo permissions08:23
*** hungtran has joined #cip08:23
sangorrinbwh: do you have some notes about the workflow you have been using until now?08:23
toscalixand probably an announcment in the cip-dev ML08:23
toscalixsangorrin: https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipkernelmaintenance08:24
sangorrinI think we need a script that can take patches and decide whether we should apply them to the cip kernel or not08:24
gavinlai#action toscalix will raise topic in TSC meeting for transfer maintainer08:24
sangorrinJan suggested using machine learning today, but other methods can be used as well08:25
bwhsangorrin: Nothing beyond what I put in the wiki about "how to review". But I can write something about whatever areas need them.08:25
gavinlainext topic?08:26
gavinlai#topic kernel testing08:27
sangorrinbwh: ok thanks. Maybe Iwamatsu san needs to get used to your scripts here https://gitlab.com/cip-project/cip-kernel/cip-kernel-sec08:27
rajm     hi, I've just successfully tested cip28 on b@d - email is on its way08:27
rajm08:27
toscalixtested=build+boot on BBB with kernelci (B@D), for those unfamiliar with rajm work08:28
rajmthe containerisation is progressing, I've run lava-docker with builds from the b@d VM - issues with tftp I think which I'm going to ask kevin about08:28
rajmand a MR of mine for kernelci-docker has been accepted08:29
gavinlairajm: thanks08:29
sangorrintoscalix: will codethink use the centralized LAVA server?08:30
rajmI've replicated a networking issue that renesas were experiencing so I can look further on that08:30
toscalixsangorrin: my intention is that but I cannot make any commitment at this point beyond moving B@D to containers. I would need an internal ok to dedicate effort08:31
toscalixto keep working on testing08:31
gavinlaiany other point for kernel testing?08:32
rajmnot from me!08:32
gavinlai#topic AOB08:33
gavinlaiany other point?08:33
sangorrintoscalix: ok, maybe you can wait until Chris or me prepare a simple guide to setup a typical board such as the beaglebone. Then it will be a matter of following that guide and ask me questions if there is a problem.08:33
toscalixsangorrin: thanks08:33
gavinlai308:34
gavinlai208:34
gavinlai108:34
gavinlai#endmeeting08:34
bwhThanks gavinlai08:34
gavinlaithanks all08:35
rajmta gavinlai!08:35
toscalixbye08:35
gavinlai:)08:35
sangorrinthanks all08:35
*** sangorrin has quit IRC08:35
*** hungtran has quit IRC08:36
rajmthe BBB healthcheck completed ~30 mins ago but I'm not seeing an email - maybe because the VM is with me at toscalix's and therefore codethink's email server is still greylisting it, anyone on cip-testing-results seen today's msg yet?08:37
*** moxavictor has quit IRC08:38
toscalixrajm: not yet08:42
rajmthough you're with the same incoming mail server - v odd08:42
rajmand it doesn't appear to have arrived at https://lists.cip-project.org/pipermail/cip-testing-results/2018-September/thread.html yet, just checked the VM's mail queue and it's not there, will check its logs08:44
rajmno sign of it in the log file - I can see yesterday's I'll try re-running the health check08:51
rajmah light dawns, it's a new health check and doesn't have the notify section - goes to repair that!08:55
rajmand that's better :-)09:05
rajma successful BBB health check with cip28 and an email to the list09:10
* rajm wonders whether the lava infrstructures allows/could allow include files making it easier to switch the health check between kernel versions - or is that going to be a lava-tool mechanism (to switch between versions)09:17
toscalixmail arrived09:26
rajmta!09:49
* rajm logs https://github.com/kernelci/lava-docker/issues/4509:49
*** CTtpollard is now known as tom__pollard10:29
*** patersonc has joined #cip10:40
*** Tzongyen_Lin has quit IRC10:41
* rajm adds extra point to https://gitlab.com/cip-project/cip-testing/testing/issues/192 as a need to consider how to handle email notifications14:59
szlin" It's long and now that 4.4 is getting15:53
szlinolder, the priority of mine is for newer kernels first, and older ones15:53
szlinsecond. "15:53
szlinQuote from Greg in stable mailing list15:54
rajmnope the u-boot prompt is right in lava-docker for our BBB, need to look at the other khilman suggestions16:25
*** toscalix has quit IRC16:36
*** rajm has quit IRC17:03
*** patersonc has quit IRC21:39

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