IRC logs for #cip for Wednesday, 2017-02-22

*** donbrown has quit IRC03:16
*** donbrown has joined #cip03:36
*** kristerman has joined #cip09:19
*** rajm has joined #cip11:25
*** rajm has quit IRC12:24
*** CTtpollard has quit IRC12:55
*** rajm has joined #cip13:21
*** rajm has quit IRC13:42
*** toscalix has joined #cip15:08
toscalixhaving two sources of info is not a good idea15:57
toscalixI suggest to kill the info in gitlab and refer to the howto in the wiki15:58
toscalixthe readme should be a description about the project and a links section to the main content15:58
toscalixkristerman:15:58
toscalixwhat do you think about my idea?15:58
kristermanYes, there is no use, the one in the wiki is the updated one16:00
toscalixI will send you a mail in a few minutes with what it shoud include the readme file16:02
kristermantoscalix, where did Jan get this document from?16:02
kristermanIn Gitlab there is a different one16:02
toscalixah, I thought it was from gitlab16:03
kristermanDo we have documents elsewhere?16:03
toscalixnot that I am aware of16:03
kristermanDid he do the review today/yesterday?16:04
toscalixyesterday I assume16:05
toscalixI do not understand what i the difference between what we have in the wiki and what we have in the readme on gitlab16:05
kristermanah no, it is in Gitlab16:05
toscalixwe have a high risk of discrepancy there16:05
kristermanit seems that the one we have in Gitlab is outdated16:05
toscalixyes, that is what I thought16:06
kristermanSo I will link GItlab to wiki, so we don't update 2 sources16:06
toscalixso I will send you a text for gitlab16:06
toscalixto substitute the current text16:06
toscalixfor devs, that readme will be the front page16:07
toscalixso we need to explain what is there wnad where to find the info16:07
kristermanHmm, so it will be the same as wiki page?16:07
kristermanI am changing Gitlab page so it is the same as wiki16:09
toscalixkristerman: no, please16:24
toscalixI just sent you a mail with the text that should go in gitlab16:25
toscalixWe do not want the same docu in two places. That is a guarantee for future disaster16:25
kristermanOkay, I am replacing it now with the text you sent on email16:27
toscalixthanks16:27
toscalixpease format it according to gitlab marcdown standards16:27
kristermanwill do16:28
toscalixI am not sure I used the right syntax in the bullet points16:28
toscalixwriting in 5 different "marcdown based tools " has ended up making me crazy16:29
toscalixI do not know what marcdown is anymore16:29
kristermanIndeed, wiki syntax is different16:29
toscalixfinishing the download page based on what we have. It should only take me a few minutes16:29
kristermantoscalix: https://gitlab.com/cip-project/board-at-desk-single-dev/blob/master/README.md16:33
kristermanlet me know if you want me to change something16:33
toscalixkristerman: as soon as I finish the download page, please include it in the readme16:34
toscalixworking on it16:34
toscalixthat would be it16:34
bwhThe wiki is dokuwiki. It's weird to start with and can be made more weird by extensions!16:38
kristermanThankfully donbrown has figured it out so just I mimicked his style16:40
toscalixbwh: it seems you have already fought with it :-)16:47
toscalixkristerman: https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipdownload16:47
toscalixlink to the download page16:47
toscalixplease add it to the readme file16:47
toscalixI will do so in a couple other places16:48
bwhtoscalix: I host a dokuwiki, for my sins16:48
toscalixoh hosting... you are a pain pro then16:48
kristermantoscalix, add the download page first under 'Interesting Links' ?16:50
toscalixright before the instructions16:51
toscalixso first you read the description, then you download, then you follow the instructions16:52
toscalixthat is the order of the links in my opinion16:52
kristermanhttps://gitlab.com/cip-project/board-at-desk-single-dev/blob/master/README.md16:53
kristermanok, but in wiki we have download link first16:53
kristermanshould I change it there too?16:53
kristermanI think so, changing it to main wiki page too16:54
toscalixno no, different workflow in the wiki16:54
toscalixleave it as it is16:54
kristermanah ok then16:54
toscalixthe way you get to the main wiki is different16:54
toscalixone last thing16:54
toscalixadd as last link in the readme file the Homa Page link https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting16:55
toscalixof the interesting link section16:55
toscalixdownload page is published and the link added to home page16:55
kristermanhyper link titled 'Home Page' ?16:55
toscalixyes16:56
toscalixeven better16:56
toscalixCIP testing project home page16:56
toscalixnow I will concentrate in the release announcement. I have to review it and publish it16:57
kristermanOkay, let me know if README looks ok now16:57
kristermanI made the changes16:57
toscalixok kristerman let's go for a final round of last minutes checks before sneding the release announcement, ok?17:03
kristermanok17:03
toscalixI would like you to go over the download page and ansure that  vagrant works17:04
toscalixI will check the links of the other pages17:04
toscalixlet's come back once we finish17:04
kristermanwe know that it works for debian/jessie and whatever version of Ubuntu don is using17:04
toscalixfor the final release I will write down these final checks so we go through it in a sistematic way17:05
kristermanother than that, there might be problems with other distros17:05
toscalixmight means we haven't test it?17:05
kristermanWe haven't tested Vagrant with all distros17:05
toscalixthen it is not a known issue17:05
kristermanYes17:06
toscalixthat should be added then to the instructions at the beginning17:06
toscalixthat has been done using debian17:06
toscalixwe will have windows users :-)17:06
toscalixok, back to final checks17:07
kristermanhttps://www.vagrantup.com/downloads.html17:07
kristermanFrom this page we know which OS work with Vagrant. according to Vagrant17:07
toscalixah, and is that link included in the instructions at the beginning?17:09
toscalixdonbrown: I read your comments about improvements in the wiki documentation. Feel free to add your suggestions. Feel free in general to add content to carify things17:10
kristermanI don't see it17:10
toscalixif we expect questions about the OS we should add a note about it in the instructions17:11
kristermanokay we need to change the 'Vagrant' hyerplink here: https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipdownload17:11
toscalixbe proactive is a must17:11
kristermanso it links to that page17:11
toscalixyep17:11
toscalixthe instructions shold point to the created download page17:12
toscalixshould17:12
kristermanchanged it on wiki download page17:12
kristermanSo make hyperlink in instructions page too on wiki?17:14
toscalixI would yes17:14
toscalixdonbrown: can modify it if he has a different opinion17:15
kristermanah wait, you mean the whole download page17:15
toscalixI do not understand this question17:15
kristermanOn downloads page now clicking on Vagrant leads to the page I sent to you earlier17:16
toscalixI do not think we should change the download page17:16
kristermanthe only think I changed is the Vagrant hyper link17:16
toscalixthe only change I am suggesting is including in the instructions page a reference to what OS has been tested. You suggested a link to be added that reflects which OS works. I agree with that change17:17
toscalixif you are talking about an additional change, I do not understand which one you are referring to17:18
kristermanhttps://wiki.linuxfoundation.org/civilinfrastructureplatform/cipdownload17:18
kristermanclick on Vagrant17:18
toscalixhummm17:19
toscalixgive me a couple of minutes to go through the workflow again17:19
kristermanok17:19
toscalixnop17:20
toscalixI will introduce a change in the download page. Your suggestion is a good one, but now the link to the code is not present17:20
toscalixnow17:23
toscalixI checked the links in the feature page, the home page and the FAQ and they work17:24
kristermanAlright, now we have both17:24
toscalixis there any last min check you want to do?17:25
toscalixsomething you haven't tested the last couple of days17:25
kristermanI tested both LAVA and KernelCI today, so I think not17:26
kristermandonbrown, still hasn't managed to perform a health check with his bbb, so we may encounter problems with that17:26
kristermanBut I can't test anything else17:27
toscalixhave you?17:27
toscalixwith bbb?17:27
kristermanyes17:27
kristermanso we know that it can be done :)17:27
toscalixbut we should be able to reproduce it17:27
toscalixhow longer will you be online?17:28
toscalixmuch longer17:28
kristermanI am confident he will be able to perform a test by today or tomorrow17:28
kristerman20 minutes?17:29
toscalixok17:30
toscalixhow long it takes for somebody to download and try it out for the first time, in your opinion?17:30
kristermanto try everything, at least 1 hour, because of having to download the kernel17:31
toscalixI see, I will wait then another 90 min to publish the announcement so I reduce the time between the release and having Don on line17:33
toscalixsince Yoshi talk is at 11:30 PT17:33
kristermanThat would be better17:33
*** toscalix has quit IRC17:47
*** kristerman has quit IRC18:17
*** rajm has joined #cip18:28
*** toscalix has joined #cip18:44
toscalixdid a small change based on Jan-Simon suggestion on step 29 and 30 I switched them18:50
toscalixemail sent18:51
*** rajm has quit IRC19:12
*** toscalix has quit IRC19:14
*** dl9pf has joined #cip19:34
dl9pfhi19:34
dl9pfI get an kvm error on the healthcheck job inside the vagrant/virtualbox VM19:38
dl9pfhttp://paste.debian.net/916263/19:44
dl9pfpossibly remove the "--enable-kvm"19:44
dl9pfBoot command: /usr/bin/qemu-system-x86_64 -cpu host -enable-kvm -nographic -net nic,model=virtio,macaddr=41135085299 -net user -m 1024 -monitor none -drive format=raw,file=/var/lib/lava/dispatcher/tmp/3/deployimages-O_sQhl/stretch-2.img -drive format=qcow2,file=/var/lib/lava/dispatcher/tmp/3/apply-overlay-guest-OhzANF/lava-guest.qcow2,media=disk,if=ide19:44
dl9pfstarted a shell command19:44
dl9pf,Kernel panic - (.*) end Kernel panic,Stack:\s+(.*\s+-+\[ end trace (\w*) \]-+),ALERT! .* does not exist.\s+Dropping to a shell!,root@debian:,login:19:45
dl9pfCould not access KVM kernel module: No such file or directory19:45
dl9pffailed to initialize KVM: No such file or directory19:45
dl9pfConnection closed19:45
dl9pffunnily:19:46
dl9pfroot@jessie:/home/vagrant# dmesg | grep kvm19:46
dl9pf[    0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d0019:46
dl9pf[    0.000000] kvm-clock: cpu 0, msr 2:1ffed001, primary cpu clock19:46
dl9pf[    4.344255] kvm-clock: cpu 1, msr 2:1ffed041, secondary cpu clock19:46
dl9pf[    4.427674] Switched to clocksource kvm-clock19:46
dl9pf[    5.457686] systemd[1]: Detected virtualization 'kvm'.19:46
dl9pfso disabling kvm might be a safer bet within a vagrant environment19:47
dl9pfwill slow-down the qemu01 worker, but stablilize it19:47
dl9pfacross different user environments19:49
donbrowndl9pf: Hi Jan, Yes, I've encountered this error before and I *thought* I had already turned off -enable-kvm automatically in the boot process.22:10
donbrownYour issue is valid. I will look to see what I did and add it to the instructions.22:11
*** toscalix has joined #cip22:40
toscalixdonbrown: around?22:42
donbrownyes22:53
donbrowntoscalix: I have answered Jan's issues in the Google Doc, and I am working on the KVM error. I've seen and solved this before, so I just need to make the change and document it properly.22:54
toscalixok22:56
donbrownAny feedback from the talk today? Any idea how it went?22:57
toscalixI had a meeting so I did not attend to the talk but it went well. I just met the CIP guys. No questions about the VM but about the kernel22:58
donbrownCool!22:58
toscalixpeople is specially interested in the use cases and the maintenance period22:58
donbrownYes. Are they still talking LTS for 25+ years?22:58
toscalixone thing.... if you work in an issue, please add a ticket22:58
donbrownWill do.22:58
toscalixdo not work in anything that does not have a ticket22:59
donbrownGotcha.22:59
toscalixthe reason is that if there is no ticket, nobody from the community can follow you up22:59
toscalixso no collaboraiton is possible until you put code in the repo22:59
donbrownright23:00
toscalixI have a question from Chris from Renesas here at the booth23:05
donbrownGo ahead23:05
toscalixwhat filesystem are we using to test on BBB?23:05
toscalixChirs has been hanging around the channel before23:06
donbrownI believe it is ext4, but I'll double-check23:06
toscalixyes please23:06
donbrownThe boot partition is FAT12, but the Linux partition is ext423:08
toscalixthanks23:09
donbrownnp23:09
toscalixmaybe is good to add this detail to the docu23:09
donbrownWill do23:09
toscalixwe might have the question again in the future23:09
donbrownDone23:11
donbrownin the FAQ23:11
toscalixok23:11
*** toscalix has quit IRC23:14
donbrowndl9pf: Please see Issue #32 in GitLab. (https://gitlab.com/cip-project/testing/issues/32). I explain how I fixed this bug.23:32
*** toscalix has joined #cip23:37

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