[00:08] <cprofitt> hello all
[00:14]  * balloons waves
[00:14] <cprofitt> hey balloons SergioMeneses
[00:15] <SergioMeneses> cprofitt, good evening
[07:50] <dholbach> good morning
[07:53] <jibel> good morning
[10:14] <dholbach> pitti, jibel: seems like vibhav is becoming the unstoppable autopkgtest machine :-P
[10:14] <dholbach> there's one up for ncurses now
[10:15] <jibel> dholbach, indeed, great contributions :)
[10:15] <dholbach> :-)
[10:16] <jibel> dholbach, now the sponsoring machine must become unstoppable too ;P
[10:25] <dholbach> jibel, we got the queue under 30 a few days ago, which was quite good
[10:25] <dholbach> http://reqorts.qa.ubuntu.com/reports/1glance-sponsoring/ might give you an idea how it looked before :)
[10:25] <jibel> dholbach, j/k
[10:26] <dholbach> no, I just wanted to say that "we're on it" :)
[11:50] <vibhav> dholbach: :D
[11:52] <vibhav> jibel, pitti: Talking about autopkgtests, I am writing one for libxcb too :)
[12:05] <jibel> vibhav, great! I noticed that there is a small testsuite in libxcb, it'd probably be worth looking at what it's doing and reuse it or write more upstream tests if possible.
[12:06] <vibhav> jibel: Yep
[12:08] <vibhav> jibel: I dont exactly know how to reduce them
[12:09] <vibhav> s/reduce/reuse/
[12:18] <vibhav> jibel: From what I can see, the testsuite in libxcb has its own mechanism for testing. It is going to be hard to reuse them, so the best would be to have seperate tests for them
[12:19] <vibhav> btw, I have libcaca as the next package on my list
[12:51] <pitti> vibhav: unstoppable :)
[12:52] <pitti> vibhav: just like the others, as long as the upstream test suite runs during the package build, the autopkgtests can be limited to a simple compile/link/run test
[13:15] <jibel> vibhav, ok, no problem.
[14:10] <vibhav> pitti: From what I caan see in the Makefile, no test suites re being performed: http://paste.ubuntu.com/1620726/ . I will hve to test the entire library then.
[14:14] <jibel> vibhav, according to build logs check is performed during the build
[14:14] <jibel> line 875 https://launchpadlibrarian.net/121646178/buildlog_ubuntu-raring-amd64.libxcb_1.8.1-2_BUILDING.txt.gz
[14:15] <jibel> result is line 894
[14:15] <zyga> cprofitt: hey, is there any update on friendly?
[15:02] <vibhav> jibel: ah, thats perfect :)
[18:13] <cprofitt> hello all
[18:50] <SergioMeneses> cprofitt, hi
[20:23] <balloons> afternoon everyone.. my internet has been bouncing me around all day.. how is everyone today?
[20:26] <Noskcaj> good, everyone's at the classroom session
[20:26] <balloons> :-)
[20:26] <balloons> good
[20:35] <SergioMeneses> balloons, hi! we are in our testing-session /o\
[20:54] <SergioMeneses> questions from balloons  :O
[20:58] <balloons> SergioMeneses, :-) Sorry I wasn't able to tweet about the sessions until just now :-(
[20:59] <SergioMeneses> balloons, dont worry :)
[21:47] <fully_human> Hello, I'm trying to get started using autopilot.  I'm following the guide at [http://www.theorangenotebook.com/2012/11/a-glance-at-autopilot.html].  When I run the first autopilot command, autopilot spits this out: [http://paste.ubuntu.com/1622304/]  Any ideas?  Thanks.
[21:48] <robotfuel> fully_human: you don't have tests to run with autopilot
[21:48] <fully_human> Ah.
[21:48] <fully_human> Even though I'm executing: autopilot run unity.tests.test_showdesktop.ShowDesktopTests.test_showdesktop_hides_apps
[21:49] <fully_human> ?
[21:49] <robotfuel> fully_human: if you do ls is there a unity folder?
[21:50] <balloons> fully_human, howdy
[21:50] <fully_human> No, there isn't.
[21:50] <fully_human> balloons: Howdy.
[21:50] <balloons> what distro are you running?
[21:50] <robotfuel> fully_human: you need to download the tests first
[21:51] <fully_human> Ah.  Thanks for helping a newbie. :P
[21:51] <balloons> basically, if you have unity installed your likely to have the tests installed
[21:51] <balloons> if you don't, let me give you the package you need
[21:52] <balloons> sudo apt-get install unity-autopilot
[21:52] <fully_human> I think I saw my problem.  I needed to do "autopilot list unity" and then run of the tests listed.
[21:52] <fully_human> Even though I still got python errors preceding the test list.
[21:53] <balloons> yes.. if autopilot list unity shows tests, then it's just a check to make sure you don't misspell the test :-)
[21:53] <balloons> you get errors running autopilot list?
[21:54] <fully_human> Yes, missing test modules, apparently.
[21:54] <fully_human> "Failed to import test module: unity.tests.launcher.test_icon_behavior" for instance.
[21:54] <balloons> ohh ohh
[21:54] <balloons> so quickly, what distro are you on?
[21:54] <balloons> precise, quantal, raring?
[21:54] <fully_human> I did install unity-autopilot, though.
[21:54] <fully_human> Quantal.
[21:55] <balloons> ok
[21:55] <balloons> so, the next part of the series covers this, but there's an autopilot ppa
[21:55] <fully_human> I installed that, too.
[21:55] <balloons>  sudo add-apt-repository ppa:autopilot/ppa
[21:56] <balloons> ok, that's good..
[21:56] <balloons> so that should ensure you have the updated version, but let's check
[21:56] <balloons> apt-cache show python-autopilot
[21:56] <balloons> I have Version: 1.2daily13.02.06-0ubuntu1
[21:57] <fully_human> Same here: 1.2daily13.02.06-0ubuntu1+bzr129pkg0quantal1
[21:57] <fully_human> I didn't run bzr, though (on the second page)
[21:58] <fully_human> But, of course, that has nothing to do with the default test cases.
[21:58] <balloons> yea.. it's odd things aren't working right for you
[22:00] <robotfuel> fully_human: does the command 'autopilot vis' work for you?
[22:01] <fully_human> Yes.
[22:01] <balloons> having the unity tests work properly isn't a big deal tho
[22:01] <balloons> you can just move on the the next part
[22:01] <fully_human> Alright, thanks.  Can't wait to contribute!
[22:01] <balloons> it might be an issue with you running the new autopilot, but using the old autopilot unity tests
[22:02] <balloons> since, your running the autopilot unity from the archive
[22:02] <balloons> thanks for the heads up on it
[22:02] <balloons> that post is really just to show off autopilot a little and give you a taste
[22:05] <fully_human> Yikes...it's really messed up now!
[22:06] <fully_human> I try to run autopilot run helloworld (from inside the autopilot-walkthrough directory) and get this: http://paste.ubuntu.com/1622342/
[22:07] <robotfuel> fully_human: what does 'python --version' return?
[22:08] <fully_human> 2.7.3.
[22:08] <fully_human> I need python 3, don't i?
[22:08] <robotfuel> no
[22:09] <balloons> wow.. weird :-(
[22:10] <fully_human> No kidding.
[22:10] <balloons> well, we've recommended you run raring to do autopilot development, but i'm really surprised it's simply not working for you on quantal
[22:10] <balloons> dkessel.. nah
[22:10] <balloons> *bah
[22:10] <balloons> he's not around
[22:10] <balloons> letzoaf?
[22:11] <balloons> I *think* they run quantal and do ap development
[22:11] <fully_human> balloons: Alright, thanks...I'll keep an eye out for 'em.
[22:11] <balloons> fully_human, are you able to run a vm on your box?
[22:12] <fully_human> Yes...I've loaded 13.04 there.
[22:12] <fully_human> Specifically to do testing. :-)
[22:12] <balloons> if so, I'd encourage you just to run raring and do the ap stuff there
[22:12] <balloons> ohh
[22:12] <balloons> perfect
[22:12] <balloons> yea, lol, use that then
[22:12] <balloons> and let's file a bug on what you found on quantal
[22:12] <balloons> using the ppa should let it work
[22:15] <SergioMeneses> ok guys see you later! take care
[22:15] <balloons> so, fully-human, I'm not sure ubuntu-bug will let you file
[22:15] <balloons> but if not, let's manually do it
[22:16] <balloons> https://bugs.launchpad.net/autopilot/+filebug
[22:17] <balloons> let me know if I can help you file it..
[22:22] <fully_human> balloons: Thanks.