IRC logs for #cip for Monday, 2017-10-16

*** bananadev has joined #cip02:33
*** patersonc has joined #cip06:41
*** patersonc has quit IRC06:51
*** rajm has joined #cip07:14
*** Gwaihir has joined #cip07:26
* rajm boots up the vm races to get to the health check before it runs but not fast enough - it's going to ping yourIRCHandle again...07:53
rajmbut apart from that the BBB health check runs successfully07:55
*** toscalix has joined #cip08:10
toscalixrajm: around?08:19
rajmyes - morning!08:20
toscalixfrom what I see, the only thing left in the deployment is the communication?08:21
* rajm thinks that's so08:21
* rajm goes to have a re-read of the ticket08:21
toscalixfill out the acceptance criteria and let's move on08:22
toscalixsend a mail to tom and myself when you are done.08:22
toscalixI will start with the feature page and the download page08:22
toscalixI would like you to focus first in the technical documentation08:22
toscalixwe will have a meeting then to talk about the rest of the pages08:23
rajmah yes - tom checked out the signing and download on friday - I'll tick off those bits of #143 and email you08:24
rajmI assume the 'Add the links and hashes.' in the ticket are the internal links in that - rather than the download page so I've ticked that08:26
toscalixok08:30
toscalixI have to change the block diagram08:30
toscalixfrom what I see, debian stretch comes with new vagrant also, 1.9.108:30
rajmthough vagrant is on the host rather than within the vm08:32
toscalixCTpollard introduced such change in the old feature page08:32
rajmdpkg-query -l 'vagr*'08:32
rajmdpkg-query: no packages found matching vagr*08:32
toscalixah, so I need to change it in the diagram too, just like I did with ser2net08:33
rajmI was treating that line of 3 boxes as being on the host - though I was wondering about ansible - I feel they ought to be above the stretch box rather than below?08:35
toscalixagree08:36
toscalixgit on the host?08:37
rajmwell both - but that's the right version of git for the vm08:38
toscalixhost os -> vm -> guest OS -> lava+kernelci ?08:39
toscalixin red everything determined by the guest os08:41
* rajm inspects diag08:41
rajmyes I'm in agreement with the current state08:42
toscalixansible and git..... lava and kernel ci depend on them but not "on top" right?08:42
*** Gwaihir has quit IRC08:43
rajm'not on top'? (but they do depend)08:43
*** Gwaihir_ has joined #cip08:43
*** Gwaihir_ has quit IRC08:47
toscalixnow better?08:49
rajmI'm not sure why the git/ansible are more part of stretch than say apache or the toolchains but that heirarchy is imho a bit arbitrary08:51
*** kristerman has joined #cip08:52
*** kristerman has quit IRC08:53
*** patersonc has joined #cip08:53
toscalixI see08:53
*** Gwaihir has joined #cip08:55
toscalixreverted08:56
toscalixvagrant is 1.9.1, right?08:57
rajmI have 1.9.2 but 1.9.1 is fine - I think that's what CTPollard is using08:59
toscalixso we are done with the diagram. Let me add it to feature page08:59
toscalixis the technical docu done from your side?08:59
rajmso reviewing steps 1-5 for any necessary changes - and making them?09:01
toscalixyes09:01
toscalixbut first, the deployment mail to finish the ticket09:02
rajmok will re-read - checked on friday but in case I've missed anything - do the links in the deployment page need changing *now*?09:03
toscalixdeployment page?09:03
rajmhttps://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptestingboardatdeskdingledevdeployment#b-d-standalone-virtual-machine-box09:04
toscalixyes09:05
toscalixthe ones we will do on release day are the download page. The rest let's change them now09:06
rajmok will do - and there's the sig date and id that's wrong too I'll go through steps 2-5 first and then return to step 109:06
*** CTtpollard has joined #cip09:17
* rajm completes a review of the configuration page (step 2)09:17
rajmand the beaglebone cofig page is done09:20
* rajm spots inconsistent reference to tags in the build howto page and fixes them09:30
toscalixI am adding licenses to the feature page tables09:32
rajmI'm going to need to change the logs of tests (referenced as links on the test cases page) but will do that later09:32
* rajm wonders whether we need to explicitly reference the B@D version number quite so often on the wiki09:34
*** Gwaihir_ has joined #cip09:40
*** Gwaihir has quit IRC09:40
*** Gwaihir_ is now known as Gwaihir09:40
*** Gwaihir has joined #cip09:41
toscalixrajm: we do not09:41
toscalixjust state... latest version of b@D09:41
toscalixcurrent version09:41
rajmok if I spot any more I'll drop a few and will go with that when I edit pages in future09:42
rajmtest cases page done (apart from logs) - now pack to the links on page 109:42
*** bananadev has quit IRC10:12
* rajm needs to provision another box to get the example wiki output - back shortly ;-)10:17
rajmlast point of the FAQ also wants a version change10:21
toscalixI keep working on the feature page10:26
toscalixI keep forgetting the model of the renesas board we are using10:40
patersonc:)10:44
patersoncI call it the iWave-M board, but the official Kernel name is iwg20m10:45
toscalixthanks10:45
toscalix:-)10:45
toscalixman we are on fire this week10:46
toscalixpatersonc: in the feature page we are collecting the links to the info about the boards https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptestingboardatdesksingledevfeaturepage#b-d-supported-hardware-links10:48
* rajm updates #144 for the technical tick boxes - I'll reference this issue in a CIP-kernel-test-logs file I'm about to update - committing directly to master10:48
toscalixcan you tell me which links should I add there?10:48
* rajm assumes that's a patersonc question rather than mine10:49
toscalixyes10:49
patersonchttp://www.iwavesystems.com/rz-g1m-qseven-development-kit.html10:49
toscalixis this one interesting, you think? https://www.elinux.org/R-Car/Upstream-Kernel-Release-Highlights10:50
patersonc^ is the nearest link. The spec for the CIP project is slighly different - there is no display10:50
patersonctoscalix: Looks quite handy10:53
patersoncLooks like Simon has been updating it10:53
toscalixCTtpollard: which was the link to the description of the board from elinux you provided me the other day?10:54
CTtpollardone second10:55
CTtpollardtoscalix: https://elinux.org/RZ-G/Boards/SK-RZG1M10:56
toscalixpatersonc: what about this link CTtpollardjust posted?10:57
patersoncThat is for a different platform. Same SoC, but a board made by Renesas rather than the iWave board that the CIP are using.10:57
patersonc(similar feature set though)10:58
toscalixah, I see10:58
toscalixwill make a note10:58
patersonc:)10:59
patersoncI've just kicked off an internal email to see if we can get eLinux updated a bit10:59
toscalixthanks11:00
toscalixpatersonc: I added three links. https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptestingboardatdesksingledevfeaturepage#b-d-supported-hardware-links11:01
toscalixwe will improve the links as CTtpollard preare the session, which he is doing this week11:03
* rajm has updated the vagrant up output and the BBB HC output just need to alter the QEMU log - this is currently a pdf - I'm intending to make it a snippet for consistency with the BBB one (and it's then easier to update!)11:05
* rajm intends to lunch - back shortly!11:06
CTtpollardpatersonc: I'm evaluating a patchset to add the board to b@d, it refers to a readme for using project-x to compile. Do you know where I could look for this?11:07
toscalixCTtpollard: project-x is in gitlab. Let me see if you have access. If not, I will provide it to you11:08
toscalixor ping the person that can11:08
toscalixCTtpollard: can you see this? https://gitlab.com/cip-playground/project-x11:09
toscalixadding you11:10
CTtpollardyep I can see it, ty11:10
toscalixnow you are dev there11:10
toscalixso you can contribute11:10
CTtpollardhowever the readme doesn't contain usage instructions11:12
toscalixyou might want to write daniel sangorrin11:13
toscalixhe cannot access this IRC channe;l11:13
toscalixsend CC to cip-dev11:13
toscalixsent mail in private11:14
toscalixdaniel S. mail address11:14
CTtpollardI have the readme I need now, thanks11:20
toscalixgreat11:21
toscalixI think I am done with the feature page. rajm will need to do the rest (technical info)11:22
toscalixafter lunch I will focus on the social media messages and the mail version of the release announcement11:23
toscalix... and my talk11:23
toscalixand the sync meeting11:23
rajmso I'm ok to update the feature page - goes to look11:39
rajm?11:39
patersoncThanks toscalix. Links look good to me.11:39
patersoncCTpollard, could you share the readme Daniel sent you?11:40
patersoncCTtpollard11:40
CTtpollardpatersonc: I didn't contact him in the end, just found it deeper in the repo https://gitlab.com/cip-playground/project-x/blob/master/deby/poky/meta-cip-iwg20m/README.IWG20M.txt12:01
patersoncThanks :)12:06
* rajm intends to use our tags for the git repos we have mirrors of?12:11
rajmno scrub that - it wouold involve changing the diagram again!12:11
CTtpollardcreated a box with the provided iwg20m patch12:19
rajmI'm not sure what you think I should be changing toscalix with some of the fixme annotations on the features page, am I ok just removing them or do you have things you want changed in those sections, I've updated version numbers in the tables12:20
toscalixrajm: we will talk about it in the meeting12:33
toscalixrajm: do you consider the technical docu done?12:34
toscalixI would like to finish that first, since it has implications on the training session12:34
toscalixand then go over the release related pages12:35
toscalixmeanwhile, the journal could be a good place to llok at ;-)12:35
toscalixI will raise at the TSC meeting again the need to have a better process to add people to the wiki12:37
rajmok - is it just the features page you wanted me to look at (apart from the 5 step pages)12:40
rajmI just need to adda QEMU log to the snippets and then link it12:41
toscalixrajm: you will need to also take care of the download page12:41
toscalixbut that will be on the RD12:41
toscalixwe will go over the documentation task during the meeting12:41
rajmyes had that as a future item12:41
toscalixI am adding bits to the landing page12:47
toscalixI would love to change it, now that we have plenty of content, but I do not have time. Will write a ticket about it.... for the future12:47
toscalixnow is simply too dense12:47
toscalixhttps://gitlab.com/cip-project/cip-testing/testing/issues/15512:54
patersoncHello toscalix, I thought Annie/LF had already granted permissions to Tom?12:55
patersonc(ref your email)12:55
toscalixhummmm if she had, I missed12:56
toscalixCTtpollard: can you try?12:56
toscalixediting in the cip wiki?12:56
toscalixhttps://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/journal#monday-2017101612:56
toscalixfor instance12:56
CTtpollardyes I can edit the wiki12:58
CTtpollardI have already closed a ticket12:59
CTtpollard#15312:59
toscalixgreat. Apologised to Annie. I cannot find the confirmation. Anyway...13:03
toscalixCTtpollard: do you mind adding yourself to the journal today?13:03
toscalixrajm: with your additions about the license and mine, I consider the landing page done13:04
CTtpollardsure13:05
rajmthat sounds good toscalix , I've just updated my bit of the journal for this morning13:09
toscalixouch..... TSC call13:11
*** darknighte has joined #cip14:02
*** rajm has quit IRC14:04
*** rajm has joined #cip14:19
*** patersonc has quit IRC14:33
*** patersonc has joined #cip14:33
toscalixso after the sync up, it seems we went over all the topics14:58
toscalixback to release work14:58
* rajm updates ticket #144 (techical instructions section)15:03
*** patersonc has quit IRC15:05
toscalixrajm: remember there is a specific task fopr each stage of the release process and a different high level view task of the process. This is due to limitations on the concept of milestone in gitlab15:07
toscalixa milestone is a colection of tasks, but not a task in itself15:07
* rajm doesn't understand the 3rd & 4th paragraphs of the test cases page they appear to be duplicate (and potentially contradictory) will make sure it gets cleaned up15:08
*** patersonc has joined #cip15:10
* rajm feels like there's duplicates in various places in terms of boxes to 'close' I feel that #141 should depend up the closure of (say) 144 rather than just being related (unless I'm missing where it is)15:12
*** patersonc has quit IRC15:12
toscalixrajm: no dependencies possible in giotlab15:13
toscalixwith tickets15:13
rajmI think some of these documentation boxes in #141 can be marked as done but I'll head to the features page with a view to those updates15:13
toscalixfocus on the low level tasks15:13
toscalixI will take care of the high level one15:13
toscalixas we close the low level task15:14
rajmthough #144 says that it's blocked by #14215:14
toscalixI will take care of #14115:14
rajmagreed (on 141)15:14
toscalixyes, I mention the blockages on the tickets15:14
* rajm thinks the 6.6GB for the installation is a gross underestimage and one of other of the vagrant/virtual box requirements were missed last time - ups it to 13GB15:24
CTtpollardI hope lots of people have usb3.0 :)15:25
*** patersonc has joined #cip15:28
toscalixrajm: in the feature page, one thing you can talk about and it is not mentioned in the release announcement is the update to stretch15:31
*** rajm has quit IRC15:32
toscalixmail version draft created from the web release announcement https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/batdmarketing#b-d-v10-releaserelease-announcement-mail-version15:46
toscalixso we have the usb sticks for the training session. Good15:48
*** patersonc has quit IRC15:51
*** patersonc has joined #cip15:58
*** patersonc has quit IRC16:21
*** patersonc has joined #cip16:31
*** patersonc has quit IRC16:34
*** toscalix has quit IRC16:41
*** patersonc has joined #cip19:01
*** patersonc has joined #cip20:26
*** patersonc has quit IRC20:48
*** patersonc has joined #cip20:52
*** patersonc has quit IRC20:55
*** patersonc has joined #cip20:59
*** patersonc has quit IRC21:02

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