IRC logs for #cip for Friday, 2018-04-13

*** vidda has joined #cip01:28
*** moxavict2r has left #cip01:32
*** moxavictor has joined #cip01:35
*** szlin_ is now known as szlin01:48
*** vidda has left #cip01:54
*** patersonc has joined #cip07:02
*** rajm has joined #cip07:30
*** rajm has left #cip07:32
*** kristerman has joined #cip07:50
*** toscalix has joined #cip08:11
*** takuo has joined #cip08:15
*** takuo has quit IRC08:19
*** CTtpollard is now known as tpollard08:50
*** rajm has joined #cip09:14
*** rajm has quit IRC09:24
*** rajm has joined #cip09:24
patersoncrajm: This ethernet issue, is there a ticket for it? Or is it just mentioned in #167?10:15
rajmI think there's just the mention in #16710:16
rajmruns a BBB healthcheck with email to the list but the renesas one is failing this morning :-(10:16
patersoncFor the same reason?10:18
rajmthe same reason? bootloader-commands timed out after 294 seconds - this was after editing the HC to use the kernelci built stuff10:19
rajmyesterday I was using a lava-tool submission but I doubt that would make any difference10:20
patersoncrajm: Is it just the tftp command that times out? Or have you seen others do so as well?10:27
rajmI think it's just that I'm retrying with the yocto built stuff so I can (hopefully!) get the board back online with the lava system10:28
patersoncOkay. Are you re-flashing u-boot though? Or does it remain the same? It looks like the issue is happening in u-boot so it won't matter how you build the Kernel/RFS10:30
rajmthat's a relief it works - email to the list but the description in the email is a lie!10:30
rajmit's remaining the same, will now test with the lava-tool and the kernelci built stuff10:31
rajmand the lava-tool one using my kernelci built stuff also works! I'll put the health check back to see if it still fails10:36
*** CTtpollard has joined #cip10:49
*** tpollard has quit IRC10:49
* rajm thinks it's going to time out again - so why does lava tool work and HC doesn't?10:49
patersoncrajm: Do you have the actual console log from the target?10:53
rajmlet me see - but very interesting I've commented out the notification section and the HC with kernelci works!10:56
rajmand there's a working one with notification but run as a lava-tool rather than a HC, I'll carefully diff the 2 files!11:10
rajmnotify - email went to the list11:10
patersoncReceived11:11
rajmno significant differences between the two files12:07
*** toscalix has quit IRC12:12
* rajm tries HC again removing some elements from the notify section12:14
rajmand that works too! (as cip-testing-results receivers will see!)12:19
rajmI'll update the journal...12:19
rajmrather verbosely! and I've put something similar in the #167 ticket, will email lava-users12:27
*** CTtpollard has quit IRC12:37
*** tpollard has joined #cip12:38
*** CTtpollard has joined #cip12:40
*** tpollard has quit IRC12:40
*** toscalix has joined #cip14:33
toscalixbwh ping14:35
bwhhi14:35
toscalixpatersonc: can you please repeat your questions, now that bwh is available_14:35
toscalixszlin: around?14:35
toscalixbwh: patersonc and szlin had questions for you yesterday at the meeting14:36
toscalixlet's see if they are around to ask you. If not, I will tell them to send a mail to cip-dev14:36
patersoncHello world14:38
toscalixpaterson, shoot14:39
patersoncbwh: I was asking about Debian LTS, specifically a couple of questions...14:41
patersonc1) What packages are supported?14:41
patersonc2) What is actually maintained? Just CVE security issues? Or bug fixes etc. as well?14:41
bwhThe support list is driven by what LTS contributors are prepared to support14:42
bwhMost LTS contributors are being paid through Freexian and Freexian surveys its customers to find out what they need to be supported14:42
toscalixLTS includes sources and packages, right?14:43
bwhSome packages are explicitly excluded (see the debian-security-support package) because they tend to have complex security issues that depend on upstream help to fix, and upstream doesn't support the version in LTS (or has gone away completely)14:44
bwhtoscalix: Currently it's mostly concerned with delivering binary packages14:45
toscalixwhat challenges do you see in CIP maintaining some sources on our own, extending LTS, for our platforms?14:45
toscalixbeyond capacity restrictions14:46
bwhtoscalix: Let me cover patersonc's number 2 first14:46
toscalixof course14:46
bwhAlmost all the work is concerned with security fixes, but other important bug fixes can be done. Certainly for the kernel I'm applying other bug fixes.14:47
bwhOK, so the main challenge I see ais in maintaining the build infrastructure over a longer period14:49
toscalixbwh: I see it also as a challenge, but not as a big one as maintaining yocto :-)14:51
toscalixbitbake, I mean14:51
toscalixwe will need to analise the packages required to install and maintain the build infra14:52
toscalixin debian14:52
toscalixand add those to our Core system14:52
toscalixlots of packages, I predict14:52
toscalixit is going to be fun14:52
toscalixthanks bwh14:56
patersoncBwh: thank you so much. I'm sorry I had to go to a meeting!15:27
*** patersonc has quit IRC15:32
szlintoscalix: I'm here15:33
*** CTtpollard has quit IRC15:35
rajmprepares to depart have a good weekend all!15:37
*** rajm has quit IRC15:39
szlinbwh: Two questions for CIP kernel maintenance15:42
szlin1. CIP kernel maintenance team working flow15:42
szline.g., by subsystem driven.15:42
szlin2. Hands-on tasks for team member15:42
bwhszlin: Hi!15:51
bwhSorry I couldn't make yesterday's meeting15:51
bwhAt the moment I'm the sole maintainer. I review changes in the 4.4 LTS branch (on stable@vger.kernel.org) and merge them after review. Any other patches are sent to the cip-dev list and I apply them after review.15:53
bwhI would like to see more people start doing thorough reviews of changes on the LTS branch15:54
bwhI made some notes about how to review changes and they're on the wiki: https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipkernelmaintenance#patch-review-howto15:55
szlinbwh: thanks, we read the wiki already. But how to start some hands-on tasks?16:05
szlinback to question #1, do we have any  CIP kernel maintenance team working flow so far16:05
szlinDo you think the working model of Debian kernel team is suitable for us?16:06
toscalixszlin: bwh is doing an internal talk now at codethink. Not sure if he will come back today. I suggest to write a mail to cip-dev wiith this question. I am sure others are interested in the answers aswell16:18
szlintoscalix: got it, thanks16:38
*** kristerman has quit IRC17:05
*** toscalix has quit IRC18:44

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