[14:30] <balloons> teward, it works for me. odd
[14:30] <teward> balloons: the clipit -c didn't work in my wily VM
[14:30] <teward> and i just pulled all the updates when i said that message
[14:30] <teward> let me reload that
[14:31] <teward> (it's different than my QA testing VM, and I have a 14.04 ISO to generate the actual data there since a wily problem)
[14:31] <rbasak> Who looks after reports.qa.ubuntu.com please? Can someone see why http://reqorts.qa.ubuntu.com/reports/ubuntu-server/merges.html has stopped updating?
[14:32] <rbasak> I can fix a problem with the script, but have no access to the box where it runs from cron I believe.
[14:33] <teward> isnt IS the one with access?
[14:34] <balloons> I'm sure an RT would be able to update it
[14:40] <teward> balloons: this is what i have from the output of that command: http://paste.ubuntu.com/11948655/
[14:40] <teward> granted this is a server VM but
[14:41] <teward> probably needs a reinstallation anyways
[14:41] <teward> i'm just a little lazy :
[14:41] <teward> :P
[14:42] <balloons> ok, I guess 2 out of 3 :-)
[14:42] <teward> balloons: works fine with the second one, but the clipit breaks it
[14:43] <teward> not sure if it's a bug or just weirdness
[14:43] <teward> (I generate the data from a 14.04 livecd anyways)
[14:43] <teward> (for the specs on my test vm on the hardware list... in fact i had to update that because VMware Workstation needed an upgrade to work with CentOS.. >.<)
[16:40] <dkessel> balloons: yes, I did get the reply. honestly, i was still waiting for the other Daniel ;)
[16:41] <dkessel> balloons: what about using AWS?
[16:42] <dkessel> i don't know anything about the hardware requirements we will have though... so if i had to choose, i would aim low to keep costs low, and try to get something that scales well if there is demand for more power
[16:46] <dkessel> i think part of the task would also be setting the whole software up and describing that good enough that it can be set up on other hardware, too. if there would ever be a need to change.
[16:47] <dkessel> after all, we don't know anything about how good acceptance and usage by the community will be. i would not want to buy and maintain hardware for that yet.
[16:47] <knome> AWS would be perfect for that
[16:50] <dkessel> what is needed to get money from the community fund?
[16:50] <knome> a receipt
[16:50] <dkessel> DanChapman, FYI ^
[16:51] <knome> let me see if i can find a url for you
[16:51] <dkessel> so.. someone paying in advance, right?
[16:51] <knome> http://community.ubuntu.com/help-information/funding/
[16:52] <knome> maybe you can talk with the CC
[16:52] <dkessel> damn, i could have requested funding for an ubuntu phone :)
[16:52] <knome> no, not that, the community team
[16:52] <knome> :P
[16:53] <knome> Q: How is payment made?
[16:53] <knome> A: It depends on the request. As an example, if you need coffee for an event, we would likely pay the vendor directly. If you need equipment, we would likely purchase it for you and then send it to you. If it is a travel request we may coordinate the booking with you. We will never write a check and send it to an individual unless it is for reimbursement.
[17:01] <balloons> hey dkessel, knome
[17:01] <balloons> I was just talking about this again. I was going to mail if i didn't hear back
[17:02] <balloons> aws is one option; there are other cloud providers as well. I think for this specifically though, you need/prefer real hardware
[17:04] <balloons> but the idea would be to figure out what is needed / desired. The key is to also make it easy to run for everyone, so we don't have to go for the absolute lowest cost on the server, if it comes to it. Think about TCO ;-)
[17:05] <balloons> once we know, I would ask you to make a request for funding. It makes sense to ask for several months or a year at once, depending on who you choose and how it can be paid
[17:06] <balloons> dkessel, I could help with exploring options if you wish
[17:08] <dkessel> balloons: sure, that would help if you could to that :)
[17:09]  * balloons rolls dice on DanChapman being around
[17:51] <voron> hi all
[17:53] <balloons> hello
[17:54] <ahayzen> balloons, Hi, what was status of getting jenkins with autopilot for coreapps on vivid+overlay running again?
[17:54] <balloons> ahayzen, if you need it, request it
[17:54] <ahayzen> \o/
[17:55] <ahayzen> balloons, both music and weather could do with it ;-)
[17:55] <balloons> ahayzen, I'm not sure we can deliver it, but we can make sure jenkins still lets you work in the interim, heh
[17:55] <ahayzen> ah yeah we have things disabled so we can still land
[17:56] <balloons> on the new jenkins, it's still wip
[17:56] <ahayzen> i was just wondering what the status/timeframe for actually having autopilot running again is
[17:56] <balloons> working on making the devices work.. they are giving trouble
[17:56] <balloons> you can be first for trialing it out.. how's that?
[17:56] <ahayzen> thats cool thanks :-)
[19:08] <rbasak> I can fix a problem with the script, but have no access to the box where it runs from cron I believe.
[19:08] <rbasak> Who looks after reports.qa.ubuntu.com please? Can someone see why http://reqorts.qa.ubuntu.com/reports/ubuntu-server/merges.html has stopped updating?
[19:11] <balloons> rbasak, did you file an RT?
[19:11] <balloons> do you know how?
[20:00] <rbasak> balloons: yeah I can do that, thanks.
[20:01] <alesage> balloons, I might need another hand-holding session re: adt-run if you're available, sure I'm doing this wrong http://pastebin.ubuntu.com/11950211/
[20:17]  * balloons looks
[20:18] <balloons> at first glance, it appears someone added a dependency but didn't add it to the manifest :-)
[20:18] <balloons> compare the debian/control file with the manifest and see
[20:36] <alesage> balloons, but that invocation looks ok?
[20:37] <balloons> alesage ?
[20:37] <alesage> balloons, i.e. my command-line invocation of adt-run looks ok
[20:38] <balloons> ohh
[20:38] <balloons> yes, it looks correct. So looking at the manifest for clock, there's no depends listed?!
[20:39] <balloons> mm.. which matches the debian control file
[20:39] <balloons> So I think I might be to blame here
[20:39] <balloons> actually, lol
[20:39] <balloons> I added the requirement for lxml
[20:39] <balloons> ohh boy
[20:40] <alesage> balloons, ok
[20:40] <balloons> so, anyways, the depends should properly reflect things
[20:40] <balloons> I suppose I should update it with an mp
[20:41] <balloons> in the interim, add the python-lxml as a depends
[20:42] <alesage> balloons, ok, just trying to figure the proper command-line really
[20:42] <balloons> bad balloons! https://code.launchpad.net/~nskaggs/ubuntu-clock-app/update-test-layout/+merge/262271
[20:42] <balloons> alesage, lol, you got it. run the calculator app
[20:43] <alesage> balloons, ok
[20:43] <balloons> alesage, and nice find on the clock whoops
[20:43] <balloons> it's always fun when you are the one to blame, heh
[20:44] <alesage> score one for testing :)
[20:44] <alesage> balloons, next question is . . . how to prevent in future :)
[20:44]  * alesage just can't get off that ci topic
[20:47] <balloons> alesage, test using adt :-)
[20:47] <balloons> technically it should have been caught under the debian package, but testing is disabled on clock because of ci
[20:48] <balloons> so really, under the old system had it been enabled, we would have caught it
[20:51] <balloons> alesage, so here's my diff
[20:51] <balloons> http://paste.ubuntu.com/11950436/
[20:52] <alesage> balloons, ok
[20:52] <balloons> if you want to try using it? lp:~nskaggs/ubuntu-clock-app/add-lxml-depends
[20:55] <alesage> balloons, ok
[20:55] <balloons> that would be helpful to confirm I didn't make a mistake, heh
[21:33] <alesage> balloons, ok but what's the proper command-line to test my locally unbuilt, modified source tree on the device? :)
[21:34] <balloons> alesage, you want to run your tests in a local source tree against the installed click on the device?
[21:34] <alesage> balloons, I don't think I want to test the installed click on the device, right?  (to test your change)
[21:35] <balloons> alesage, in this case only the tests change, so need need to update the click on the device
[21:35] <balloons> but I'm not sure what you want, hah :-) To test my change, just pass the click source, and then the click name, not a new click file
[21:36] <alesage> balloons, ok the same command-line above produces the same result :(
[21:36] <balloons> alesage, ohh wait, I lied
[21:36] <balloons> you need a new click, because the depends in the base click don't have the python3-lxml
[21:37] <alesage> balloons, right that makes sense
[21:37] <alesage> also I forgive you
[21:38] <alesage> (for lying) and also it's helpful to go through this to get some best-practices together
[22:34] <veebers> balloons: if you're still around, I need a quick hand with checkbox and was hoping you could point me in the right direction
[22:37] <balloons> veebers, you are wanting to make a testcase to run through checkbox?
[22:38] <veebers> balloons: aye, just a very simple one so I can get the results and actually go through the process to see how it works
[22:38] <veebers> in the wiki docs it mentions a simple manual test with a mouse "Is your mouse moving" etc
[22:38] <balloons> veebers, my advice for you would be to run some of the default tests and look at the results
[22:39] <veebers> balloons: Ok, I can try that. I had a quick look last night. Perhaps it'll be more obvious today. I also could find where the test jobs were stored at all
[22:40] <balloons> veebers, what docs? note, I've not put together a test in a little while, and I know some things have changed. That said the format is easy. What I don't know offhand is how to package and feed it to checkbox
[22:41] <balloons> but for what you are after, running the defaults is probably the simplest for now
[22:41] <veebers> balloons: ack, I'll try that. Thanks :-)
[22:41] <veebers> balloons: oh, re: docs it was these: https://wiki.ubuntu.com/Testing/Automation/Checkbox
[22:42] <balloons> veebers, ohh my
[22:42] <balloons> I wouldn't touch those
[22:42] <knome> lol
[22:42] <knome> what's the status of checkbox really?
[22:42] <knome> is anybody working onit?
[22:42] <veebers> balloons: :-P it's what came up in a google search
[22:43] <knome> is there any features that actually make it more useful than just learning to set up vboxes yourself?
[22:44] <veebers> knome: my understanding is that it can be used for manual testing and results collection
[22:46] <knome> how does it collect results then?
[22:46] <knome> oh wait, that's something different
[22:46] <knome> i thought we were talking about testdrive
[22:46] <knome> continue!
[22:47] <veebers> knome: oh, ^_^ too many names
[22:47] <knome> yes...
[22:47] <knome> too many generic names
[22:47] <balloons> knome, hehe!
[22:48] <ahayzen> balloons, is there an AP sdk helper for triggering the bottom edge?
[22:49] <balloons> ahayzen, there isn't. The reason is the bottom edge can mean anything to an app
[22:49] <ahayzen> ah ok
[22:49] <ahayzen> guess i can hijack code from someone else :-)
[22:49] <balloons> that said, obviously different apps may have helpers you can borrow if your app behaves in a similar way
[22:49] <balloons> in reality, it's a simple drag operation, depending on what you are doing