=== verterok` is now known as verterok === balloons is now known as Guest87130 === bigcat__ is now known as bigcat [06:37] good morning [06:39] mvo: hey, did you have a safe trip home? [06:49] good morning [07:09] good morning [07:26] morning o/ [08:00] *yawn* [08:00] morning! [08:27] mvo: o/ [08:29] hey Chipaca! good morning [08:29] mvo: welcome back to the world of the living mr mvo! [08:29] mvo: hope you've been able to rest and snuggle the family :) [08:30] Chipaca: :) thanks! I did and it was very nice. I am currently write down all that I can remember from the sprint [08:30] mvo: good idea. carry on. :) [08:31] Chipaca: is there anything I can do for you? [08:31] Chipaca: I guess code reviews? [08:31] Chipaca: (haven't really looked yet :( [08:31] Chipaca: I will certainly need a break from spec writing at some point [08:32] mvo: don't worry about it *until* you need that break :) [08:32] i'm in no hurry [08:32] puzzled by things that are nil not being equal :) [08:33] Chipaca: heh :) [08:34] i've got thing != nil, but thing == (*snappy.SnapPart)(nil) [08:34] *head scratch* [08:34] on the upside, tests are hitting some weird corner cases :D [08:34] woah [08:35] ah, i know why; thing is an interface [08:35] interface value [08:36] \o/ [08:54] Good morning all; happy Monday, and happy Teachers' Day! 😃 [10:39] dholbach, it seems now LP can build snaps http://blog.launchpad.net/general/launchpad-news-september-2015 [10:39] yep, great news, isn't it? :-D [10:40] I'm just finishing my patch pilot shift today, then I'll go and play around with it and then write a blog post :) [10:47] cool :) [10:56] with bug 1487010 still stuck, that means no race detector for go in wily, right? [10:56] bug 1487010 in golang (Ubuntu) "please upload new package to reenable go's race detector on wily" [Undecided,In progress] https://launchpad.net/bugs/1487010 === chihchun is now known as chihchun_afk [12:56] Hello, I have a .snap file. We are wondering how to run this? [12:59] squll: run "snappy install your-snap" on a snappy system, snaps will only work on snappy systems, i.e. http://ubuntu.com/snappy [13:30] mvo: any chance of a review on https://code.launchpad.net/~chipaca/snappy/activate-package/+merge/272716 ? [13:31] mvo: http://i.imgur.com/UnlYwpF.jpg [13:31] built a snappy file, still no clue on running that [13:31] Anyone got tips? [13:32] squll: how did you build it? [13:33] snappy build . [13:33] squll: and how did you try to run it? [13:34] We still have no clue on even how to run that [13:34] squll: and, more interestingly for me [13:34] ok [13:34] And Googling 'How to run a snappy app' gives me alot of information on building [13:34] But I am not really seeing a command or something like that to run it [13:34] squll: did you see mvo's reply to you the first time you asked? [13:34] squll: how do you run an apk? [13:34] No I did not [13:34] squll: run "snappy install your-snap" on a snappy system, snaps will only work on snappy systems, i.e. http://ubuntu.com/snappy [13:35] Yes I saw that [13:35] We did that indeed. [13:35] snappy versions gives us a list with that name in the list [13:35] But then I want to run it (it gives me data when executing it) [13:37] squll: sorry, i'm not sure i understand [13:37] squll: did you install the snap in a snappy ubuntu core system? [13:37] Yes we did [13:38] We have an Erle Rover (robot) with an small pc on it running snappy Ubuntu Core [13:38] squll: ok [13:38] squll: and does your snap have binaries, services, both, ...? [13:39] We are able to connect to the snappy app webinterface where we were able to run the HelloWorld snap. We find a hello-world.canonical file after some searching. That is indeed running and echo'ing hello world as expected. [13:40] squll: does *your* snap, the one you built, have binaries, services, both, ...? [13:40] So then we go along and follow the tutorial of the vendor of our robot containing a snappy which prints out the date. [13:40] No it does not [13:40] what prints out the date? [13:40] Well, we just don't really understand what we should expect after like a succesful build. Do we get a .canonical file or somthing? [13:41] It's just some C++ code, let me look up if there is a public github [13:41] squll: hold on [13:41] squll: let's slow down a bit [13:41] squll: you created a snap by following the tutorial and doing "snappy build ." [13:42] Yes we did. [13:42] squll: you then copied the snap to your snappy system === Odd_Blok1 is now known as Odd_Bloke [13:42] squll: and did "sudo snappy install your-snap.snap" [13:42] We moved it to /home/ubuntu (as the tutorial tells us to do) [13:43] squll: ah, you built it on the snappy system itself? [13:43] squll: and did you then install it? [13:44] Yes. We are ssh-ing into the system and indeed building it on the system itself [13:45] squll: sorry to repeat, but: did you, after building the .snap, install it? [13:46] Okay, hold on. We seemed to build it and let the robot blink a LED as we expected. But the whole idea of snappy is vague to us [13:47] We received a script file and after executing that, the led blinks. [13:47] Chipaca: yes, I do that next, sorry for the delay === davmor2_ is now known as davmor2 [13:48] Anyone know the link for sabdfl's talk at ROSCon? [13:48] squll: I'm not sure whether you think you've answered my question, because I still feel you haven't [13:49] @tedg: Not found it yet, I think you should keep an eye on the social media platforms of OSRF [13:49] squll: No such command! [13:49] mvo: thanks [13:50] Chipaca, what question you mean exactly? [13:51] squll: did you, after building the .snap, install it? [13:52] We executed 'snappy install status-led-XXX.snap'. Is that what you mean by installing?\ [13:52] Funny that it was apparently live streamed, but when trying to get things the old fashioned recorded way that proves difficult :-) [13:52] squll: yes. [13:52] squll: ok, so "snappy list" shows that snap, then [13:52] Yes we did execute that command [13:52] Yes it does [13:53] squll: so. If your snap exports binaries, you should now have things that start with status-led-* in your PATH [13:53] squll: if you enter status-led- and hit they should come up [13:54] umm. was "-" valid as part of a snap name? I don't remember. Anyway, not important at this stage. [13:54] squll: if, on the other hand, your snap exports services, they would show up in "snappy services status" [13:54] squll: sorry, snappy service status [13:56] We find an binary (what is a script) contain some shellscript [13:56] It uses the command aa-exec which needs a profile which can not be found [13:57] squll: that means your snap is not a good snap :) [13:57] But it is a safe app thing, we know it is safe [13:58] squll: could you pastebin your package.yaml and what you get when you run the script? [13:59] squll: also, could you point me at the tutorial you followed, if it's online? [14:02] Can't find the tutorial quickly. Package is just as it should [14:02] How do I officially run a snappy app? Just as a command? [14:04] squll: I'd expect most snaps at this stage to have services, with commands used only for debugging, introspection, or integration purposes [14:05] squll: as to "official", as long as you're using the services (through whatever interface they provide) or binaries (through the wrappers in /apps/bin), that's about as official as it gets [14:07] squll: as to your snap being "just as it should", if it were exactly as it should you wouldn't get apparmor complaining [14:08] Well I look at the default example of a package.yml [14:08] The package.yml is following that specification [14:09] squll: which is the default example of a package.yml? [14:53] plars: any news with the lab? [14:54] elopio: I'm having some annoying issues with logstash, and with rpi, but otherwise things are going ok [14:55] elopio: last I tried, the logging was working this morning, so if you want to retry your job I can look (unless you were able to get output some other way already) [14:55] plars: I will run it. [14:55] elopio: actually [14:55] elopio: did you already run it this morning? [14:55] elopio: someone ran something on bbb [14:56] plars: it's scheduled to run daily, but jenkins chooses the time. [14:56] so yesterday, at some point, it ran. [14:56] elopio: https://www.irccloud.com/pastebin/J5R78ELe/ [14:58] can anyone review https://code.launchpad.net/~dholbach/snapcraft/fix-pep8-and-doc-indentation/+merge/273195? [15:00] * Chipaca looks [15:00] dholbach: actually, standup; after that [15:00] cool thanks! [15:00] plars: ok, that's one step closer. Still it doesn't capture those errors in the results. It should. [15:01] plars: also, it should exit with != 0, but it says PASS. [15:02] elopio: yeah, that's a change that just landed this morning, I can redeploy with the new code in just a bit if you'd like [15:02] plars: that would help a little. [15:03] that output for some reason hides everything that happened on the actual run. /me checks that. [15:04] elopio: it looks like you are pointing at a bad path [15:04] plars: where? [15:05] elopio: I guess perhaps it would be there if the earlier go bits ran [15:05] plars: no, that's because adt-run didn't execute. [15:06] the error is before, when we build the test binaries. [15:06] plars: could you install this two? [15:06] sudo apt-get install golang-go-linux-arm [15:06] sudo apt-get install gcc-arm-linux-gnueabihf [15:08] elopio: sure, I'll wait for the job on bbb-5002 to complete and redeploy both [15:40] elopio: try again? [15:40] elopio: I also installed the latest autopkgtest from http://launchpadlibrarian.net/218441943/autopkgtest_3.17.2_all.deb [15:41] plars: thanks. Running. [15:47] barry: You know, to help with the Python 3 transition, you guys should make it so the Python2 documentation isn't indexed by search engines. [15:48] dholbach: long branch, but an easy ready :) lgtm. [15:48] easy read* [15:48] thanks Chipaca! [15:50] tedg: maybe! i almost never see py2 docs. i have a nice chrome search shortcut for getting to the latest py3 library docs [15:51] barry: Ah, the problem is the py2 ones come up first almost always, they're the most linked to. [15:52] tedg: i'm not sure how we can influence that, other than making those pages off limits to robots, which seems like a heavy hand [15:53] tedg: i'd go more with public shaming for even thinking about py2 :) [15:54] barry: "To see this documentation please first watch this video on why you're a bad person if you click 'next'." [15:54] tedg: love it! :) [15:57] can someone point me to a list of basic snappy commands to get my nic running? [15:58] also can someone tell me how to list the installed pci devices - lspci does not seem to work or be installed [16:02] wiggleworm: not without a lot more info on what you've got, and maybe not even then :) [16:02] wiggleworm: your nic as in a network interface? [16:03] wiggleworm: wrt lspci, ls /sys/bus/pci/devices might be a good place to start [16:10] @Chipaca: I ran the ls command and is shows a lot of device IDs but not "human readable" names [16:10] wiggleworm: No such command! [16:11] @nothal_: thanks :) - thats why I am here - I am looking for a list of basic network commands [16:11] wiggleworm: No such command! [16:12] I know that I have a wireless card and an ethernet card but I do not know the commands to bring them up [16:13] @dance for us [16:13] Chipaca: No such command! [16:14] * Chipaca thinks nothal_ is no fun anymore [16:14] * nothal_ thinks Chipaca is no fun anymore [16:14] wiggleworm: is the (ethernet) network plugged in? [16:14] wiggleworm: if so it should come up on its own [16:16] wiggleworm: for wireless i'm not sure; i think we ship enough bits that it should be possible, now, to bring up a wireless network, but i wouldn't know how to go about it. I'd start reading interfaces(5) and go from there. [16:21] @Chipaca: thanks, I will start there [16:21] wiggleworm: No such command! [16:26] plars: things are happening, because it has been running for more than 15 minutes. [16:27] elopio, do you know which version of pep8 is running on the tarmac instance? (https://code.launchpad.net/~dholbach/snapcraft/fix-pep8-and-doc-indentation/+merge/273195) [16:28] dholbach: let me check. [16:31] elopio: I never saw any output from it, but the last run I see seems to have exited with a rc of 2 [16:34] dholbach: 1.4.6-1.1build1 [16:35] ah, ok, so that's trusty's pep8... [16:35] dholbach: yes, tarmac is trusty. [16:35] should I install vivid's pep8? [16:35] I'll see what I can do [16:36] that helps already, thanks [16:36] dholbach: it would be nice to have the tests passing in both. But I prefer to land your branch soon, so let me know if it is bothering you too much. [16:37] I'll see if I can make it conform to both [16:50] plars: now it says failed: http://10.55.32.109:8080/job/snappy-daily-rolling-bbb/26/console [16:50] still no results. Can you please paste the output? [16:51] this one must have run something because it took 1 hour to poll the result. [16:51] elopio: ^ [16:51] elopio: Command failed, rc=2 [16:51] no output [16:52] plars: hum, does it timeout? [16:52] elopio: it didn't take that long to die, only about 12 min [16:52] elopio: in my logs I show that it was done trying to run after 12 min [16:52] plars: are you looking at jenkins-snappy-daily-rolling-bbb-26669ff7f4-ddb9-4dcc-b836-28b879072a26 ? [16:53] if it took only 12 min, there's something wrong with the results in spi. The job checked it 4 times. [16:53] elopio: I have no idea how long it takes for spi to register the results [16:53] elopio: but on my end, it's been done for a very long time [16:54] afk for a few, brb [16:57] elopio, it works for me in both now - maybe you want to take another look? https://code.launchpad.net/~dholbach/snapcraft/fix-pep8-and-doc-indentation/+merge/273195 [17:01] dholbach: thanks a lot [17:01] thanks for confirming and reviewing it initially :) [17:01] I've been wanting to do this for a long time, but mterry doesn't like 80 column lines [17:02] you doing it while he's no longer with us was the perfect solution :D [17:03] I had no idea :) [17:03] elopio, :) [17:03] 80 column lines are an historical accident [17:03] dholbach: I know. I didn't say a word ;) [17:04] mterry: we still love you and miss you. [17:04] :) [17:04] * dholbach hugs you all [17:08] have a great rest of your day everyone! === bigcat is now known as bigcat[s3] [17:14] ouch, dholbach had a typo. [17:21] Question about webdm - if its running should I be able to see port8080 in LISTEN mode [17:23] wiggleworm: webdm uses port 5200, not 8080 [17:23] 4200* === DanChapman_ is now known as DanChapman [17:26] wiggleworm: what's on 8080? [17:27] @Chipaca: ok, even if its 4200 - I should still be able to see it when I run netstat -ntlp [17:27] wiggleworm: No such command! [17:27] stop with the @s already :) [17:27] ok [17:27] wiggleworm: just saying my nick is enough [17:28] no [17:28] np [17:28] otherwise i'll have to ask for nothal to be kicked out, because it's annoying [17:28] anyway [17:29] what does the at symbol do [17:29] wiggleworm: yes, if webdm is running, i'd expect to see it in netstat [17:29] wiggleworm: nothal_ is a bot, he does some useful things for us [17:29] for example [17:29] @reviewlist [17:29] https://code.launchpad.net/~snappy-dev/ubuntu-core-launcher/lp1496070/+merge/271167 | No reviews (19 days old) [17:29] https://code.launchpad.net/~stephen-stewart/webdm/use-correct-version-for-post-css-bemlinter/+merge/272467 | Approve: 1 (9 days old) [17:29] https://code.launchpad.net/~kyrofa/webdm/autorestart_services/+merge/268120 | No reviews (51 days old) [17:29] https://code.launchpad.net/~fgimenez/snappy/hw-assign-test/+merge/273413 | No reviews (less than a day old) [17:29] https://code.launchpad.net/~fgimenez/snappy/wait-for-idle-partition/+merge/273100 | No reviews (3 days old) [17:30] $ sudo netstat -ntlp [17:30] Active Internet connections (only servers) [17:30] Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name [17:30] tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1007/sshd [17:30] tcp6 0 0 :::22 :::* LISTEN 1007/sshd [17:30] tcp6 0 0 :::4200 :::* LISTEN 3293/snappyd [17:30] wiggleworm: ^ [17:31] Chipaca - thanks. Mine is not showing that - I guess i do not have the service started [17:32] wiggleworm: do you have it installed? [17:32] Chipaca: its says its installed - but I think its not running [17:33] Chipaca: systemctl list-units --no-pager | grep webdm [17:33] wiggleworm: what does "snappy service status" say? [17:33] shows webdm_snappyd_0.9.2.service loaded failed failed [17:33] wiggleworm: time for a little journalctl [17:33] wiggleworm: or [17:34] webdm snappyd enabled; loaded; failed (failed) [17:34] sudo snappy service logs webdm [17:37] Chipaca: 2015-10-05T16:45:51.766560Z systemd Started Snappy WebDM. [17:37] 2015-10-05T16:45:51.769154Z systemd Starting Snappy WebDM... [17:37] 2015-10-05T16:45:51.930078Z ubuntu-core-launcher 2015/10/05 16:45:51 Failed to listen 224.0.0.251:5353: listen udp4 0.0.0.0:5353->224.0.0.251:setsockopt: no such device [17:37] 2015-10-05T16:45:51.973332Z systemd webdm_snappyd_0.9.2.service: main process exited, code=exited, status=1/FAILURE [17:37] 2015-10-05T16:45:51.973857Z systemd Unit webdm_snappyd_0.9.2.service entered failed state. [17:37] 2015-10-05T16:45:51.974349Z systemd webdm_snappyd_0.9.2.service failed. [17:38] Chipaca: Service failed - any way to find out why? [17:38] sigh [17:38] i know why [17:38] it can't start without a network device [17:38] it's supposed to wait, but there is a timeout [17:38] my eth1 is working [17:39] Chipaca: is there a way to "modify" the wait time? [17:39] wiggleworm: sudo snappy service webdm start should get you back up [17:39] wiggleworm: not easily, no [17:40] wiggleworm: but there is a bug about restarting services not happening [17:40] need to fix that [17:41] Chipaca: another error [17:41] Chipaca: unable to start webdm's service snappyd: [start webdm_snappyd_0.9.service] failed with exit status 6: Failed to start webdm_ [17:41] snappyd_0.9.service failed to load: No such file or directory. [17:41] oh, that's interesting [17:42] oh, wait [17:42] snappyd_0.9.service? [17:42] did you type that by hand, or is it missing the .2? [17:43] wiggleworm: ? [17:43] Chipaca: I ran sudo snappy service webdm start and thats what popped out [17:43] ok [17:43] wiggleworm: and what does 'status' print now? [17:43] this might be a different bug :) [17:44] wiggleworm: there's a bug where sometimes service files get left behind on upgrade, i need to dig a little but it's some weird systemd integration problem, probably my fault [17:44] wiggleworm: but it's benign, if it is that [17:46] Chipaca: (amd64)ubuntu@localhost:~$ snappy service status [17:46] Snap Service State [17:46] webdm snappyd ; not-found; inactive (dead) [17:46] webdm snappyd enabled; loaded; failed (failed) [17:46] hurr [17:47] wiggleworm: what do you get from `sudo journalctl -ex -u webdm_snappyd_0.9.2.service`? [17:47] (pastebin plz) [17:48] Chipaca: Sorry, I have to run. I will be back later this afternoon. I will run that and pastebin it in a little bit [17:48] wiggleworm: sure [17:48] then ping you [17:48] wiggleworm: i'm off too, but will read up when i return [17:57] elopio: one just finished a few minutes ago, same exit status (2) no output [17:58] plars: I will remove the test from the script and just try creating the results json. [17:59] Chipaca: here is the pastebin you asked for http://pastebin.com/GHTfEpM0 [19:42] plars: take a look at the script. I commented out everything except the cat to the results.json. Still no payload. How come? [19:45] elopio: hmm, not sure... let me take a look [19:45] elopio: where's your script again? [19:46] plars: http://people.ubuntu.com/~elopio/spi_scripts/snappy-tests-job.sh [19:47] elopio: also, do you have the results url for spi? [19:47] plars: not sure what do you mean [19:48] plars: https://spi.canonical.com/orgs/canonical/results ? [19:48] elopio: https://spi.canonical.com/orgs/canonical/results... or something? what's a good search string to use? [19:49] https://spi.canonical.com/orgs/canonical/results/ + image_unique_id [19:49] elopio: ....which is? [19:49] plars: for the latest run, jenkins-snappy-daily-rolling-bbb-29af6fb1fb-6489-4e26-a298-28d14c6fe827 [19:53] elopio: your json needs fixing [19:53] elopio: double quotes instead of single, and you need a comma between the k:v pairs [19:53] elopio: then it should work [19:53] elopio: also, try something for me [19:54] elopio: this won't matter to spi, but it will answer a question for me about my logging config, have it echo something during your script [19:54] to stdout, not just to the file [19:54] elopio: fixing the json should be enough that you can see results in the result_payload though [20:01] plars: ugh, stupid me [20:01] thanks, I'll give it a try. [20:34] elopio: I got the output on my end, but it looks like your payload is still missing. I think I know what's wrong though, sorry I forgot to mention, but you'll likely need to escape your quotes [20:34] elopio: \" [20:34] elopio: otherwise the json will still be missing them [20:54] Chipaca: you back yet? [20:59] wiggleworm: no [20:59] wiggleworm: remind me, what was it about? [21:00] something about webdm not running [21:00] * Chipaca looks at the pastebin [21:01] wiggleworm: the pastebin is cut off, can you tell me what it says to the right of “Failed to listen 224.0.0.251:5353: list”? :) [21:17] Chipaca: listen udp4 0.0.0.0:5353->224.0.0.251: setsockopt: no such device [21:24] elopio: I see your result payload now [21:24] \o/ [21:27] wiggleworm: this is after a reboot? [21:31] Chipaca: nope, just a sec and I will reboot and try again [21:38] is there something like bzr shelve, but less dselect-before-apt? [22:10] mwenning: any news wrt the race detector branch? [22:10] package [22:10] thing? [22:12] mwhudson: ^ I meant you [22:12] mwenning: bad completion, sorry [22:12] Chipaca: no, i had one round of review [22:12] yeh, saw that, but then nothing? [22:12] Chipaca: if you know any members of ~ubuntu-sponsors... [22:12] mwhudson: i fear it'll miss the boat, if it hasn't happened already :( [22:13] Chipaca: it is getting pretty late :( [22:13] Chipaca: i'm not sure i have the energy to get worked up about it unfortunately, i have other things on my plate [22:13] (as i'm sure everyone does) [22:14] mhmm [22:14] i'll poke pitti tomorrow [22:14] he'll be so relieved i'm not asking him about systemd, he might actually do something about it [23:23] yisss [23:24] after a moment of panic where i thought i'd deleted it all, the husks pipeline is now up for review [23:24] \o/ [23:24] also: 💤