[00:33] <fully_human> Yeah! My first bug fix!
[00:33] <balloons> fully_human, ohh! linky!
[00:35] <fully_human> Darn...I thought I fixed it. :(
[00:39] <phillw> fully_human: that's the problem with bugs... they are like cockroaches.... capable of surviving a nuclear war :)
[07:30] <dholbach> good morning
[07:34] <jibel> good morning
[11:16] <jibel> pitti, what's your understanding of the option --tmp-dir of adt-run? If it's specified it should unpack the package,  build it if required and test if from that dir, right?
[11:18] <pitti> jibel: yes, that's what it sounds like
[11:28] <jibel> pitti, ok, another bug in adt-run then. That makes collecting test artifacts created by the test more difficult, like impossible since the tmp directory is destroyed upon test completion :/
[12:49] <jibel> vibhav, 1rst run https://jenkins.qa.ubuntu.com/job/raring-adt-ncurses/1/ \o/
[13:02] <jibel> vibhav, wrt. the error on stderr "Error opening terminal: unknown." I think you need to set TERM before executing the test
[13:03] <jibel> export TERM=linux should do it
[13:03] <jibel> vibhav, add that line 90 in debian/tests/build
[13:40] <smartboyhw> phillw, ping
[13:41] <phillw> hi smartboyhw
[13:41] <smartboyhw> phillw, if you want zequence just simply ping him:P
[13:41] <phillw> okies
[14:39] <vibhav> jibel: thanks
[14:40] <vibhav> pitti: Do I need to add a seperate changelog entry to fix the test?
[14:40] <pitti> vibhav: for ncurses? yes, it's a new upload
[14:40] <vibhav> Good
[14:40] <vibhav> Will do that ASAP
[14:41] <pitti> vibhav, jibel: oh, I pinged about the ncurses thing in #u-devel earlier
[14:41] <pitti> if $TERM succeeds, that should be alright; I guess it shoudl have a valid /dev/console after all in the VM
[14:41] <vibhav> Ah, I never thought about that
[14:43] <pitti> you can try yourself in a VM
[14:44] <vibhav> pitti: I am on a mobile right now
[14:45] <vibhav> pitti: Are there any special instructions for setting up a VM?
[14:45] <jibel> pitti, do you tihnk we should set TERM by default?
[14:45] <jibel> vibhav, http://bazaar.launchpad.net/~auto-package-testing-dev/auto-package-testing/trunk/view/head:/doc/USAGE.md
[14:45] <pitti> vibhav: http://developer.ubuntu.com/packaging/html/auto-pkg-test.html#executing-the-test
[14:46] <pitti> vibhav: pick your favourite doc :)
[14:46] <jibel> dholbach, how do I proposed updates to http://developer.ubuntu.com/packaging/html/auto-pkg-test.html ?
[14:46] <pitti> jibel: I'd rather not; it makes these kinds of assumptions explicit, and there is no particular valid TERM for that environment
[14:46] <jibel> *propose
[14:46] <jibel> pitti, ok
[14:49] <dholbach> jibel, bzr branch lp:ubuntu-packaging-guide
[14:50] <jibel> dholbach, thanks, I'd like to describe how to run tests from a local directory
[14:50] <dholbach> great
[14:53] <vibhav> pitti: Okay, so I add export TERM=linux on line 90, right?
[14:54] <pitti> vibhav: right before the ./curses-test ? sounds right
[14:54] <vibhav> alright
[14:54] <pitti> vibhav: but as I said, I'm not entirely sure whether that will suffice
[14:54] <pitti> I'll check it in a VM when sponsoring
[14:54]  * pitti builds current VM
[14:55] <vibhav> Actually, the problem here is that I have a very very slow Internet connection
[14:55] <vibhav> 100 kbps-ish
[14:56] <pitti> vibhav: no worries, I'll tests it here
[14:56] <vibhav> pitti: Thats why I use "sudo adt-run --no-built-binaries --built-tree=. --- adt-virt-null". I hope it has no downsides
[14:56] <pitti> vibhav: it's a good first test, but doesn't catch a lot of error cases
[14:57] <vibhav> Yes, it is also hard to ensure that required packages are not installed
[15:04] <vibhav> pitti: https://code.launchpad.net/~vibhavp/ubuntu/raring/ncurses/add-autopkgtest/+merge/147383
[15:04] <vibhav> \o/
[15:04]  * vibhav goes back to writing libxcb test case
[15:04] <pitti> vibhav: "Fix --cflags --libs" -> hah, I guess you forgot to push that earlier? that's what I mentioned in the MP
[15:04] <pitti> vibhav: testing that
[15:04] <vibhav> Indeed =)
[15:09]  * vibhav crosses fingers
[15:09] <pitti> ubtree0t-build       FAIL status: 1, stderr: --cflag: unknown option
[15:10] <pitti> vibhav: --cflags :)
[15:10] <vibhav> bang_head(table);
[15:10] <pitti> vibhav: mind to push this? (I'm testing your branch directly)
[15:10] <vibhav> Of course
[15:10]  * pitti hugs vibhav
[15:11]  * vibhav hugs pitti back
[15:11] <vibhav> Done
[15:12] <pitti> $ run-adt-test -s -S lp:~vibhavp/ubuntu/raring/ncurses/add-autopkgtest ncurses
[15:12]  * pitti runs again
[15:13]  * vibhav crosses all fingers
[15:14] <pitti> . o O { this would be a lot faster if there wasn't a kernel update today }
[15:15] <vibhav> :)
[15:17] <pitti> vibhav: rocking, works now
[15:17]  * pitti merges/sponsors
[15:18] <vibhav> aw yeah
[15:18] <dholbach> yeehaw
[15:24] <jibel> $ apt-cache search ^lib|wc -l
[15:24] <jibel> 21575
[15:24] <jibel> vibhav, ^ 21575 to go ;P
[15:25] <vibhav> i had done te same today :)
[15:25] <jibel> vibhav, haha, great, thank you for your help :)
[15:27] <vibhav> jibel: No problem :D
[15:27]  * vibhav plans to finish at least 20 more packages in this cycle
[15:28] <pitti> vibhav: can you please send a Debian bug with the patch, too?
[15:29]  * pitti hopes that at some point http://jenkins.debian.net/ will run them, too
[15:30] <vibhav> pitti: Sure
[15:31] <jibel> pitti, I haven't found preinstalled images of debian yet, so that'd mean using a different provsioning method
[15:32] <pitti> jibel: something like calling debootstrap with a couple of --include=autopkgtest,openssh-server,...  I guess?
[15:33] <jibel> pitti, yes, it should work.
[15:33] <vibhav> pitti: Is it recommended to use library routines that block/sleep ?
[15:34] <pitti> vibhav: for tests? autopkgtest has a builtin timeout, but of course it blocks the machines if they just sit there for 2 hours
[15:34] <vibhav> Neat
[15:36] <pitti> vibhav: what do you mean in particular?
[15:40] <vibhav> pitti: xcb_wait_for_event() blocks. So I was wondering if there is a timeout
[15:40] <pitti> vibhav: isn't there an easier API which won't block which you could use for a compile/link/run test?
[15:41] <vibhav> pitti: xcb_poll_for_event
[15:41] <vibhav> I will use that then
[15:41] <pitti> vibhav: libxcb already runs upstream tests during package build for functionality (not sure how much coverage they have, though), so a simple libxcb_open() or whatever should suffice
[15:41] <vibhav> But there is not going to be any event
[15:42] <vibhav> \o/
[15:42] <pitti> vibhav: or xcb_intern_atom{,reply} perhaps
[15:43] <pitti> vibhav: but I guess a simple xcb_connect (NULL, NULL); should even suffice
[15:43] <vibhav> okay
[15:49] <fully_human> Hello.  Could someone please grab the latest source file for AutoPilot (from Launchpad) and run "autopilot vis?"  What do you get?
[15:50] <fully_human> Rather... "auto-pilot vis"
[15:50] <vibhav> pitti: Any export magic needed?
[15:50] <pitti> vibhav: you need to run the test in xvfb-run
[15:51] <vibhav> done
[15:52] <vibhav> xvfb-run ./test yields no output, is that fine?
[15:52] <pitti> vibhav: I don't know, does ./test print anything?
[15:52] <pitti> xvfb-run certainly doesn't block stdout/stderr
[15:52] <vibhav> Not printing
[15:54] <vibhav> pitti: Okay, tests are successfully working \o/
[15:57] <vibhav> pitti: http://paste.ubuntu.com/1625421/
[15:59] <pitti> vibhav: LGTM
[16:13] <vibhav> pitti: I will upload them tomorrow
[16:14] <pitti> have a nice weekend everyone!
[16:15] <vibhav> Ok, I gotta study. See you guys later
[17:20] <plars> jamespage: around?
[17:22] <jamespage> plars: I am
[17:24] <plars> jamespage: I'm seeing something odd on a server install that's normally fairly reliable... it's not one of the smoke test jobs
[17:25] <plars> jamespage: it's using the same preseed as for a while now, same hardware, but today it doesn't seem to be seeing the disks, and is getting stuck asking if I have iscsi to set up
[17:25] <plars> jamespage: do you know of anything that might have changed between yesterday's and todays image that would possibly cause that?
[17:27] <jamespage> plars: for raring?
[17:28] <plars> jamespage: yes
[17:37] <jamespage> plars: not that I am aware of
[17:38] <jamespage> plars: that would indicate its not seeing the internal disks I guess
[17:39] <plars> jamespage: it's all remote from me, so it's a bit of a pain to work with, but both the i386 and amd64 images on this machine have been going strong for a while now, then all of a sudden today they both failed to install with this same issue.  I ran another install with desktop on here (which frequently breaks because of some odd bug we're having with cobbler installs atm) and it worked
[17:40] <plars> so I think the drives are ok
[18:26] <balloons> fully_human, did you manage to get autopilot going?
[18:26] <balloons> I also wanted to make sure a bug got filed :-)
[19:03] <jibel> balloons, fully_human autopilot in trunk was broken until recently
[19:03] <balloons> jibel, it wasn't working in quantal for him.. but was in raring
[19:04] <balloons> do you have a bug for the issue or ?
[19:04] <jibel> balloons, I didn't see it was in quantal. no bug it was a discussion between devs
[19:05] <jibel> balloons, BTW I asked to have the introspection modules landed daily into raring
[19:05] <jibel> balloons, so people have all the good stuff directly in raring without the need of a ppa
[19:05] <balloons> jibel, yes that should be happening
[19:05] <balloons> perhaps they didn't land the introspection stuff
[19:05] <balloons> but they should
[19:06] <balloons> I am still running via the ppa, but I see ap coming in often in the archive in raring
[19:06] <jibel> balloons, autopilot-gtk is now in raring as of 2013-02-08 16:40:12.249579+00:00
[19:06] <jibel> balloons, and -qt will probably be Monday
[19:06] <balloons> nice, good to know, thank you
[19:06] <balloons> thomi should be back next week as well
[19:07] <jibel> balloons, this is the same version than the PPA minus 1, but tested through the daily landing system
[19:42] <balloons> hello letozaf_
[19:42] <balloons> hello Noskcaj
[19:42] <Noskcaj> hey balloons
[19:42] <balloons> letozaf_, I wanted to ask you.. did you or do you use quantal for autopilot testing?
[19:42] <letozaf_> balloons, Hi
[19:43] <letozaf_> balloons, no I used Raring
[19:43] <balloons> ahh.. kk
[19:43] <balloons> did you try quantal and it not work?
[19:43] <letozaf_> balloons, no I have always tested on Raring
[19:43] <letozaf_> balloons, but if you need I can try on Quantal
[19:43] <balloons> no no
[19:43] <balloons> it's semingly broken, heh
[19:44] <balloons> when fully_human is around again, I need to see if he was able to file a good bug
[19:44] <letozaf_> balloons, but what is broken on Quantal?
[19:44] <letozaf_> balloons, I mean the whole autopilot or a test o what?
[19:44] <balloons> not sure exactly, but he wasn't able to run tests properly it seems
[19:45] <balloons> autopilot itself
[19:45] <balloons> not us :-p
[19:45] <letozaf_> balloons, :-P
[19:45] <letozaf_> balloons, if you want I can reboot my notebook on Quantal and try autopilot
[19:45] <balloons> sure.. he simply tried running the unity tests
[19:46] <balloons> give it a whirl
[19:46] <letozaf_> balloons, ok, let me try
[19:46] <balloons> sudo apt-get install python-autopilot unity-autopilot
[19:46] <balloons> try with and without the ppa
[19:46] <letozaf_> balloons, ok
[19:51] <letozaf_> balloons, it will take a bit, I have to install all Quantal updates, I have been using Raring lately and have left Quantal aside
[19:51] <balloons> letozaf_, lol.. yea, I know how that is
[19:51] <balloons> I have a precise install around that had tons of updates needed.. I just updated it last week
[19:51] <balloons> after like 3 months
[20:05]  * letozaf_ is rebooting 
[20:26] <Letozaf_> balloons, should I run the complete unity autopilot test or only one in particular ?
[20:26] <mapreri> ciao Letozaf_ :)
[20:27] <mapreri> umh..., hello :)
[20:27] <Letozaf_> mapreri, Hey how are you ?
[20:29] <Letozaf_> balloons, couldn't wait so I am now running the full autopilot unity test
[20:30] <Letozaf_> balloons, looks like it's working fine up to now
[20:30] <mapreri> Letozaf_: fine! unlike ic3d. He have the enterly family ill... :\
[20:32] <Letozaf_> mapreri, oh! I'm sorry for him, didn't know this, well unfortunatly this is the right period for bad flus
[20:33] <phillw> Hi, folk! what is current minimum RAM recommendation for Ubuntu?
[20:34] <balloons> Letozaf_, ok, so that's without the ppa yes?
[20:34] <fully_human> balloons: I'm back.
[20:34] <Letozaf_> balloons, yes
[20:34] <balloons> you only need to run one
[20:34] <balloons> ahh
[20:34] <balloons> fully_human, hello
[20:34] <balloons> :-)
[20:35] <fully_human> Hello.
[20:35] <Letozaf_> balloons, it's still running :D
[20:35] <balloons> Letozaf_, ok, try the ppa..
[20:35] <balloons> Letozaf_, you can stop it :-p
[20:35] <Letozaf_> balloons, yes sure!
[20:35] <balloons> it will run fo r a LONG tme
[20:35] <balloons> fully_human, so Letozaf_ is trying to reproduce your issue on quantal
[20:35] <Letozaf_> balloons, I was just looking at it, wish I could write all those tests :D
[20:35] <balloons> did you get a bug filed for it? jibel also mentioned some issues with ap that might have been affecting things
[20:35] <fully_human> Letozaf_: The vis issue?
[20:35] <fully_human> balloons: The vis issue?
[20:36] <fully_human> (That was too balloons :|)
[20:36] <balloons> IIRC, you couldn't run any tests right?
[20:36] <fully_human> *to
[20:36] <balloons> or the autopilot vis tool
[20:36] <balloons> ?
[20:36] <fully_human> balloons: IIRC?
[20:36] <balloons> if i remember correctly
[20:36] <fully_human> Ah.
[20:37] <Letozaf_> phillw, https://help.ubuntu.com/community/Installation/SystemRequirements
[20:37] <fully_human> Well, the problem was that I used TAB to autocomplete the test suite, it appended a slash, and python import statements can't handle slashes.
[20:37] <balloons> phillw,  I believe 512
[20:37] <fully_human> So I fixed the bug and proposed a merge.
[20:37] <Letozaf_> balloons, yes 512
[20:37] <balloons> fully_human, ohh.. so it is working?
[20:38] <fully_human> Yes, but vis isn't working...I'm working on that next.
[20:38] <balloons> k
[20:38] <balloons> so Letozaf_ sounds like we're ok
[20:38] <balloons> does autopilot vis work on that quantal box?
[20:38] <Letozaf_> balloons, fine :D
[20:38] <phillw> balloons: Letozaf_ gr8, i just realised that I'm suggesting 512 Mb RAM for my virtualisation classroom sessions :)
[20:38] <fully_human> Letozaf_: Are you a dev for autopilot?
[20:39] <Letozaf_> fully_human, mmm dev... I do my best to write some autopilot tests :-P
[20:39] <fully_human> :-P Never mind. :-D
[20:39] <balloons> fully_human, Letozaf_ is our friendly neighborhood Carla :-) always ready to jump in
[20:39] <balloons> thomi is an autopilot dev, and he does hang around in here
[20:40] <balloons> but's he's away at the moment
[20:40] <Letozaf_> balloons, autopilot vis works on my Quantal notebook
[20:40] <fully_human> Ah, thanks.
[20:40] <balloons> we also sometimes bug alesage ... just to get his box to ping
[20:40] <balloons> alesage
[20:40] <balloons> alesage, <3
[20:40] <alesage> my ears are tingling!!!!!!
[20:40] <fully_human> It's addictive...this bug-fixing thing. :-)  I'd better hide my laptop under my bed so my parent's can't see the launchpad page up. :-)
[20:41] <phillw> lol
[20:44] <balloons> so, fully_human what where you thinking about writing up?
[20:45] <fully_human> Writing up?
[20:45] <balloons> btw, alesage did you get anywhere on eye of gnome?
[20:46] <alesage> not yet balloons, but I've fixed a bug that was blocking elopio https://code.launchpad.net/~allanlesage/autopilot/fix-path_info-param-lp1119541/+merge/147416
[20:46] <balloons> fully_human, sorry mate.. I meant to say, what were you thinking about trying to write an autopilot test for? Or where you just checking it out?
[20:47] <fully_human> I was running through the tutorial at orangenotebook (I think that's the site).  I ran into a few problems, though and decided to fix them.
[20:47] <balloons> alesage, nice.. gtk introspection <3
[20:47] <Letozaf_> fully_human, you're also an Aussy ?
[20:48] <fully_human> Nah.  Why would you say that? :-)
[20:48] <alesage> balloons, so full of hearts today--Valentine's day can't be far off :)
[20:48] <Letozaf_> fully_human, because balloons wrote "mate" usually Aussies say mate
[20:49] <balloons> Letozaf_, lol.. yes, I randomly adopt all sorts of phrases.. it's part of working with so many folks across the world
[20:49] <fully_human> Nope, I'm a full-blooded American.
[20:49] <Letozaf_> fully_human, :D
[20:49] <fully_human> If it would make you feel comfortable, though, I could say "mate" every once in a while.
[20:49] <fully_human> :-)
[20:49] <fully_human> And "cheers" whenever I leave.
[20:50] <Letozaf_> lol
[20:50] <balloons> aww, righto..
[20:52] <Letozaf_> balloons, what does aww, righto mean ?
[20:52] <balloons> fully_human, anyways, so I'm actually the author of those tutorials, so I just wanted make sure everything was going well.. and if not, then :-)
[20:53] <balloons> Letozaf_, I was trying to be silly.. however, I believe 'right-oh' or righto simply means, yes, I understand, I agree.. something along those lines
[20:54] <balloons> phillw is the native british english speaker here.. he should tell us
[20:54] <Letozaf_> balloons, :-P google didn't help me this time :D
[20:54] <fully_human> Yes, everything was going pretty well...I was able to run the "helloworld" and "firefox" examples.  I got to the vis example, saw there was a bug and though "dang, a bug!" Then I realized, "I know python! I can fix this!"  But, yes, I like the tutorials.
[20:54] <balloons> ohh boy.. this isn't good..
[20:55] <balloons> my disk just went to read-only again and I can't hear it failing in the pc.. on a new drive... HMMMMM
[21:00] <Letozaf_> balloons, :(
[21:02]  * balloons wonders if I have another cable or ? I'm confused
[21:03] <phillw> balloons: you got a new disk?
[21:04]  * balloons switches boxes
[21:04] <balloons> yes, the disk in there is new
[21:04] <balloons> the old one failed, wouldn't run the full diagnostic
[21:04] <phillw> hmm, not good :/
[21:04] <balloons> and the log had a bunch of read failures
[21:04] <balloons> so, I was going to debug it a bit more and confirm it's death this weekend
[21:05] <phillw> is SMART okay with new drive?
[21:05] <balloons> meanwhile I put the new disk in
[21:05] <balloons> it was.. I can't tell now..
[21:06] <balloons> I think i'm going to play the switch cables game and see what happens
[21:06] <balloons> gotta start looking at this more closely
[21:06] <balloons> also switching ports on the mobo
[21:06] <balloons> i'll assume for now the disk is actually good
[21:07] <balloons> it's just like testing.. except it's real
[21:07] <balloons> fun game!
[21:07] <phillw> yeah, run fsck over it and see if it reports any errors. It could actually be the hard-disk controller that is 'poorly'.
[21:08] <phillw> a poorly disk, is a great concern... I had one reporting errors and it was nail biting waiting for the replacement to arrive.
[21:09] <balloons> brb, going to swap things around and turn it back on
[21:10] <phillw> okies.
[21:10] <phillw> good luck & happy hunting!
[21:20] <Letozaf_> balloons, http://paste.ubuntu.com/1626746/
[21:20] <Letozaf_> balloons, I'm trying to click on shotwell button
[21:21] <Letozaf_> balloons, but I get an error saying Object 'None' does not have any recognised position attributes
[21:21] <Letozaf_> balloons, what is it ? I mean does this mean that I cannot click on that button or that I have done something wrong ?
[23:23] <phillw> balloons are you going to be about for https://wiki.ubuntu.com/Testing/Activities/Classroom#Section_3 ?