[01:24] <SergioMeneses> balloons, around?
[05:29] <pitti> Good morning
[06:23] <elfy> Good morning
[07:14] <jibel> good morning
[09:18] <asac> so for http://reports.qa.ubuntu.com/smokeng/saucy/image/2601/ i see that there is one error
[09:18] <asac> now i wonder how to find the consoleouput/job of the error
[09:18] <asac> how do i navigate from there?
[09:19] <asac> https://jenkins.qa.ubuntu.com/job/saucy-touch-maguro-smoke-default/4/console
[09:19] <asac> ->
[09:20] <asac> Triggering a new build of eventstat-saucy-touch-armhf-install-idle-maguro #3
[09:20] <asac> Triggering a new build of smem-saucy-touch-armhf-install-idle-maguro #3
[09:20] <asac> but: https://jenkins.qa.ubuntu.com/job/eventstat-saucy-touch-armhf-install-idle-maguro/ has no #3 :)
[12:54] <xnox> that's public instance results. the in-progress builds can be viewed via vpn on the internal jenkins instance.
[12:56] <xnox> balloons: ^
[13:20] <asac> plars: any hint how to find out which 10 tests were run an which failed for http://reports.qa.ubuntu.com/smokeng/saucy/image/2610/
[13:20] <asac> ?
[13:21] <plars> asac: yep, those are the ones you and gema discussed recently. we added them and transitioned to using the saucy images
[13:21] <plars> asac: the only test that's failing is the pwd/cd test, just due to a minor bug in the test. I submitted a merge proposal to fix it yesterday and I'm about to merge it
[13:22] <asac> plars: how can i see in the bug what those 10 tests are?
[13:22] <asac> err in the job
[13:23] <plars> asac: I'm linking it now (just got up, morning here, sorry)
[13:23] <plars> asac: but it will take a bit of time before it cycles through to the dashboard
[13:25] <asac> linking?
[13:25] <asac> is there no way to see which tests got run in the console?
[13:28] <plars> asac: in the console?
[13:30] <asac>  /console
[13:30] <asac> jenkins log
[13:30] <plars> asac: if you mean the console output in jenkins, it will typically only have the raw log of the installation, and calling utah
[13:30] <plars> asac: if you look at the yaml file in the artifacts though, it has the details of the test run
[13:30] <asac> ok sorry ... guess i just need quick intro :) ... so if i go there: https://jenkins.qa.ubuntu.com/job/saucy-touch-grouper-smoke-default/3/console
[13:30] <asac> i can see 2 jobs get run
[13:30] <plars> asac: including all tests run, stdout/stderr, returncode, and all that
[13:30] <asac> i checked out those logs and they really run one test each
[13:31] <asac> but that doesnt sum up to 9/10 (which is what i see on the dashboard)
[13:31] <plars> asac: right, see https://jenkins.qa.ubuntu.com/job/saucy-touch-grouper-smoke-default/3/artifact/utah.touch-smoke-default.yaml/*view*/
[13:32] <asac> is that a magic url?
[13:33] <plars> asac: no
[13:33] <plars> asac: it's linked to in jenkins that way
[13:34] <asac> its not linked for me here: https://jenkins.qa.ubuntu.com/job/saucy-touch-grouper-smoke-default/3/
[13:34] <asac> i only have https://jenkins.qa.ubuntu.com/job/saucy-touch-grouper-smoke-default/3/artifact/utah.touch-smoke-default.yaml
[13:34] <plars> asac: click on artifacts
[13:34] <asac> which doesnt view inline
[13:34] <plars> asac: then next to the yaml file, click view
[13:34] <asac> it doesnt have the /*view*/
[13:34] <asac> oh
[13:34] <asac> secret box
[13:34] <plars> asac: you can get to it with what you point at also, but it will download it instead... which also works
[13:34] <asac> found it :)
[13:34] <plars> it's the same file
[13:34] <asac> man thats not very intuitive :)
[13:34] <plars> not so secret, it's the link at the top :)
[13:35] <plars> agree, it's not as intuitive as I'd like
[13:35] <asac> well, but all i would expect from space is already there, inlined
[13:35] <plars> but we don't write jenkins
[13:35] <asac> so i wouldnt expect that this hides anything marginally different :)
[13:35] <asac> just the view link basically
[14:08] <gema> apw: do you have an eta on when your changes for the battery of the nexus 4 will be in the images?
[14:10] <apw> gema, checking ... but as we can install kernels manusally (and have to indeed) i don't think it hsould hold you up any
[14:10] <gema> apw: it doesn't , I am just curious
[14:11] <gema> apw: what holds me now is the apps behaviour
[14:11] <gema> apw: but getting there
[14:11] <apw> gema, ok it is in the -3.11 kernel which is in the archive
[14:11] <apw> gema, not sure how to tell whether it is in the image other than installing it
[14:11] <gema> apw: ack, I will do that
[14:11] <gema> I need to upgrade anyway
[14:48] <asac> plars: so after fixing the pwd/cd, will you rerun the tests?
[14:49] <asac> e.g. to get stuff green?
[14:49] <plars> asac: I can if you like, or they will automatically kick off tomorrow
[14:49] <asac> if its cheap, lets kick them off
[14:50] <asac> who knows... maybe tomorrow there will be something else ornage :)
[14:50] <plars> asac: as it is right now, the failure is tagged with a bug indicating what was wrong, and the bug is fix-released
[14:50] <plars> asac: I also added a new test to check for presence of the UI
[14:50] <asac> nice
[14:50] <asac> so rerun :)
[14:50] <asac> if there is a new image with the fix yet
[14:50] <asac> not sure how to figure that easily
[14:51] <asac> oh the fix was on infrastructure? then its just a rerun for sure
[15:58] <gema> apw: changes available in the new image
[15:58] <gema> excellent stuff
[16:42] <xnox> I did not specify needs-building, yet my autopkgtest is currently building the package. That's exactly what it shouldn't be doing.
[16:42] <xnox> why is that?
[16:42] <xnox> plars: pitti ^ did something change in auto-pkg-testing?
[16:45] <xnox> nevermind. I didn't specify package name to test =)
[16:46] <xnox> plars: pitti: unping =)
[17:29] <asac> plars: u said the code to show the details of what tests ran/succeeded/failed will land in dashboard today?
[17:30] <plars> asac: I'm not aware of any plans for that, but I can talk to doanac and see
[17:30] <plars> doanac: is there any plan to parse the results and display testcase details in the dashboard?
[17:32] <asac> plars: nevermind. i think i misread what you said above
[17:33] <asac> i think linking the view directly would be helpful enough to get started
[17:34] <asac> like direct link from: http://reports.qa.ubuntu.com/smokeng/saucy/image/2610/ to a) https://jenkins.qa.ubuntu.com/job/saucy-touch-grouper-smoke-default/3/artifact/utah.touch-smoke-default.yaml/*view*/
[17:34] <asac> and b) maybe to console log
[19:04] <Letozaf_> balloons, Hi
[19:15] <balloons> Letozaf_, hello :-)
[19:16] <Letozaf_> balloons, I received a mail from Olivier telling me that my merge request for calendar app could not be accepted  because there are conflicts when merging my  branch into trunk due to a recent renaming of the packages and that I  need to merge back trunk into my branch and resolve conflicts.
[19:16] <Letozaf_> So I renamed the ubuntu-calendar-app directory on my PC branched in a new directory ubuntu-calendar-app and copied inside the test files under the "emulators" directory and the "tests" directory, but I get this error: http://paste.ubuntu.com/5778030/
[19:16] <Letozaf_> balloons, can you help me solve this ?
[19:17] <Letozaf_> balloons, looks like an API problem
[19:20] <balloons> Letozaf_, sure thing
[19:21] <balloons> since the upstream code changed while you were branching you need to rebase your branch
[19:21] <balloons> there's a command to do it in bzr, named aptly rebase I believe
[19:22] <balloons> Letozaf_, that's a wild bug
[19:23] <Letozaf_> balloons, looks like I'm lucky with wild things :p
[19:23] <balloons> hah! Well something in autopilot appears unhappy
[19:23]  * Letozaf_ is reading about bzr and rebase
[19:23] <balloons> I must same i've not had to do it much
[19:24] <balloons> jackson just did it.. if he was around he might have some insight
[19:24] <balloons> regardless what you did achieves the same thing
[19:24] <Letozaf_> balloons, yes I also thought so, but I get that API version error
[19:25] <balloons> care to push it to lp again and I'l try running it?
[19:25] <Letozaf_> balloons, ok just a second
[19:25] <balloons> your on saucy right?
[19:25] <Letozaf_> balloons, yes
[19:26] <Letozaf_> balloons, witch one do you want the old directory I renamed or the new one I branched again and where I get the new API error ?
[19:26] <balloons> the new branch :-)
[19:26] <Letozaf_> balloons, fine just a second
[19:28] <Letozaf_> balloons, https://code.launchpad.net/~carla-sella/ubuntu-calendar-app/calendar-API-problem
[19:29] <balloons> k, grabbing
[19:31] <balloons> wild.. why does autopilot want to install compiz?
[19:33]  * balloons needs to re-install autopilot on the laptop :-)
[19:34] <balloons> anyways since it was causing you issues on saucy I thought I'd try raring
[19:35] <Letozaf_> balloons, ok
[19:36] <balloons> anyways, i'm presuming it's an autopilot bug
[19:37] <balloons> Letozaf_, does autopilot list work for you?
[19:37] <balloons> it's broken for me.. that's not a good sign
[19:37] <Letozaf_> balloons, no
[19:37] <Letozaf_> balloons, broken !
[19:38] <Letozaf_> balloons, same API vers. problem
[19:38] <balloons> hmm.. indeed, your missing the ubuntusdk.py file
[19:38] <Letozaf_> balloons, thought I copied it, let me check
[19:39] <Letozaf_> balloons, it's there in the emulators directory
[19:39] <balloons> make sure autopilot list sees everything ok without error.. assuming that works and it doesn't run, well then we can think about blaming the tool. but otherwise  :-)
[19:39] <balloons> it's not in the branch you sent?
[19:39] <balloons> check bzr status
[19:39] <balloons> see if it's included or not
[19:40] <Letozaf_> balloons, oh my! how did this happen ? I did something wrong... let me check
[19:40] <Letozaf_> balloons, thats funny I've got it, should I paste it in pastbin so you can copy it ?
[19:41] <Letozaf_> balloons, or what ?
[19:41]  * elfy laughingly comments that he never does anything wrong with bzr 
[19:41] <elfy> balloons calls elfy a fibber
[19:41] <Letozaf_> elfy, a what?
[19:41] <Letozaf_> elfy, what is a fibber ?
[19:41] <elfy> fibs - like lies :)
[19:42] <elfy> not quite so "nasty: though :)
[19:42] <Letozaf_> elfy, yeah! checked on google :P
[19:42] <elfy> :)
[19:42] <Letozaf_> elfy, :-)
[19:43] <elfy> I think I've managed to get my head around it now though :)
[19:43] <Letozaf_> balloons, http://paste.ubuntu.com/5778129/
[19:44] <Letozaf_> balloons, even if I don't understand why it did not push that file, I was in the right directory when I pushed it
[19:44] <Letozaf_> balloons, weired :p
[19:44] <balloons> Letozaf_, if you don't 'add' a file to bzr it's not tracked and won't be pushed
[19:45] <balloons> just add it and then commit, and then push it up to lp
[19:45] <balloons> I can then pull the branch and get the update :-)
[19:46] <Letozaf_> balloons, oh right, let me do it
[19:46] <balloons> hehe :-)
[19:46] <balloons> elfy, how are you.. I'm so behind on merging, but I hope to get it going again today
[19:46] <balloons> as I told Jackson I had to pause for a bit because of a sync bug
[19:47] <Letozaf_> balloons, done :p
[19:47] <elfy> balloons: I'm ok - I somehow got confused with a bunch of tests - but I think I've caught up now - there's a merge request from me for a fix to 2 I did
[19:48] <elfy> got my head around reviewing testcases as well
[19:50] <balloons> elfy, :-)
[19:50] <Letozaf_> balloons, I had downloaded the ubuntu-calculator-app to have a look at it and if I run autopilot list on it I get the same error, so it's for sure not related to the calculator app
[19:50] <balloons> ohh boy
[19:51] <Letozaf_> balloons, :(
[19:53] <elfy> balloons: mostly I'm pleased that once a bunch of merges go through - the xubuntu bugs will be closer to 25 than 35 :)
[19:54] <Letozaf_> balloons, I will reboot my notebook, never know just in case, be back in a few seconds...
[19:54] <balloons> Letozaf_, ok so I see the issue
[19:54] <balloons> lol
[19:55] <balloons> Noskcaj, howdy sir
[19:55] <Noskcaj> hello balloons
[19:56] <balloons> Letozaf_, so I see the issue
[19:56] <Letozaf_> balloons, what is it ?
[19:56] <balloons> it's a couple things.. one they renamed ubuntu_calendar_app to calendar_app so we need to update things
[19:57] <balloons> the second is you didn't copy __init.py__ (assuming there was one)
[19:57] <Letozaf_> balloons, argh!
[19:57] <balloons> because there's an import for it in the main test
[19:59] <Letozaf_> balloons, the __init.py__ in witch dir
[19:59] <Letozaf_> balloons, there are 3 I think
[19:59] <Letozaf_> balloons, in the calendar_app dir, the tests dir and the emulators one
[20:00] <balloons> yes, rather annoything how they use it don't you think
[20:00] <balloons> but, it's the one in the calendar_app dir
[20:00] <balloons> it's the only non-blank one
[20:00] <Letozaf_> balloons, quite :P
[20:01] <Letozaf_> balloons, yes looks like I got three blank ones :(
[20:01] <balloons> ahh.. well then, they must not have done it. So I'm confused about the import in the main test
[20:02] <balloons> CalendarTestCase is not defined
[20:02] <balloons> see the import? from calendar_app.tests import CalendarTestCase
[20:02] <Letozaf_> balloons, no I was wrong, just a second...
[20:03] <Noskcaj> balloons, on issue i've been seeing with the manual testcases: What is the correct format for the testcase description (the bit before <dt.>)
[20:03] <balloons> Noskcaj, you can put any text you wish before the <dt> atm..
[20:04] <balloons> the biggest difference is the continuing of the old testcase naming before the <dt> vs not
[20:04] <Noskcaj> ok
[20:07] <balloons> Letozaf_, ok..
[20:07] <Letozaf_> balloons, I checked, I have two blank __init.py__ files and one in the tests dir that is not
[20:08] <Letozaf_> balloons, I copied the __init.py__ file from the old directory (the one I re-named) in the "new" one, but the error is still there
[20:09] <Letozaf_> balloons, so maybe it's that not defined CalendarTestCase...
[20:10] <balloons> you still have to mod it slighty
[20:10] <balloons> Letozaf_, notice they renamed things to calendar_app from ubuntu_calendar_app.. so rename things accordingly and the import should work, and thus the test should work :-)
[20:11] <Letozaf_> balloons, oh fine, sorry missed this, let me check thanks
[20:12] <balloons> Letozaf_, no worries.. basically the define a class in the __init.py__ and there's some helper stuff in there
[20:13] <balloons> the __init.py__ is needed by python so that it sees the resulting .py file as a module.. it's one of those funny python things is all.. but I personally am NOT a fan of having code in __init.py__.. but then again I'm not a python hacker, so perhaps it's good practice
[20:25] <Letozaf_> balloons, I changed all the ubuntu-calendar-app in calendar-app but the error is still there
[20:26] <balloons> can you push your __init.py__?
[20:26] <Letozaf_> balloons, yes
[20:29] <Letozaf_> balloons, done
[20:30] <balloons> Letozaf_, k pulling
[20:33] <balloons> Letozaf_, it looks ok now on this box.. I have to install the sdk now too, lol, so I'll need a moment to run
[20:33] <balloons> let me look at the code though
[20:34] <Noskcaj> balloons, you have at least 5 different merges for manual tests. when do you think you'll be able to start merging them?
[20:35] <balloons> Noskcaj, I believe I'ved fixed the bug I had with syncing
[20:35] <balloons> that's what the holdup is :-)
[20:35] <Noskcaj> ok
[20:35] <balloons> anyways, as soon as I finish with Letozaf_, i'll test it
[20:35] <balloons> if it works I'll merge everything
[20:36] <Noskcaj> ok
[20:36] <Letozaf_> balloons, ok
[20:36] <Letozaf_> balloons, let me know
[20:36] <Letozaf_> balloons, you are on saucy are you ?
[20:36] <balloons> Letozaf_, what error is it giving u?
[20:37] <balloons> Letozaf_, I'm on my raring laptop for this :=)
[20:37] <Letozaf_> balloons, http://paste.ubuntu.com/5778285/
[20:37] <Letozaf_> balloons, oh so it might be a Saucy issue
[20:38] <balloons> Letozaf_, that was the idea to check :-)
[20:38] <Letozaf_> balloons, I hope so, otherwise it means I've got something weired on my laptop :p
[20:39] <balloons> Letozaf_, indeed.. most likely the merge could just go as-is
[20:39] <balloons> sdk almost installed :-)
[20:39] <Letozaf_> balloons, fine
[20:40] <balloons> Letozaf_, seems fine here
[20:41] <Letozaf_> balloons, :)  on Raring right ?
[20:43] <balloons> yes
[20:43] <balloons> merge it :-)
[20:43] <Letozaf_> balloons, ok
[20:45] <balloons> are all your tests broken atm Letozaf_ on saucy?
[20:45] <balloons> and your up to date?
[20:46] <Letozaf_> balloons, yes
[20:46] <Letozaf_> balloons, while you were checking the calendar-app
[20:46] <Letozaf_> balloons, I ran a sudo apt-get update and dist-upgrade and rebooted
[20:47] <balloons> Letozaf_, ok, so it's worth filing a bug against autopilot
[20:47] <balloons> and checking potentially to see if downgrading helps things
[20:48] <Letozaf_> balloons, ok so maybe before filing the bug I will check if the test works on Raring
[20:49] <balloons> worked on raring for me, but sure :-)
[20:50] <balloons> Noskcaj, ok trying to merge your first mp
[20:50] <Letozaf_> balloons, is it a problem if I do it tomorrow evening ? or will it be too late ? I am not sure I have autopilot on my Raring partition and
[20:50] <Letozaf_> balloons, I also have to update it
[20:50] <Letozaf_> balloons, it will take some time
[20:50] <Letozaf_> balloons, or shall I just file the bug ?
[20:51] <Letozaf_> balloons, and check the Raring downgrade tomorrow
[20:53] <Letozaf_> balloons, I am submitting a bug and will check the downgrade tomorrow
[20:56] <Letozaf_> balloons, bug number 1192333
[20:59] <Noskcaj> write it as bug 1192333 and ubot will respond
[21:00] <Letozaf_> balloons, https://bugs.launchpad.net/autopilot/+bug/1192333
[21:01] <Letozaf_> balloons, going to bed :) 'night I will check the Raring downgrade tomorrow (I am quite sure it will work as it worked for you)
[21:15] <balloons> whoa.. sorry, I guess I dc;d and it didn't send anything
[21:15] <balloons> :-(
[21:15] <balloons> hello sak
[21:16] <sak> i have done some testing of the alsa package and everything turned out great.
[21:16] <sak> hello ballons
[21:16] <balloons> Noskcaj, ok so anyways I was merging your stuff and asked if elfy and you could review some of the MP's
[21:16] <Noskcaj> balloons, ok
[21:16] <balloons> I'll merge them all right now :-) the sync is working again.. found one small minor issue that I fixed also after the first test
[21:16] <balloons> sak, wonderful.. no issues is a good sign :-)
[21:17] <balloons> did you see the bug njin found for it though?
[21:17] <balloons> you could try confirming it
[21:18] <sak> there was a bug, the name is pavucontrol1191345)
[21:19] <Noskcaj> sak, in IRC write bugs as bug 1191345
[21:19] <sak> as far as mesa:X-staging, there are no 64bit packages.
[21:20] <sak> ok noskcaj
[21:23] <balloons> sak, no 64-bit packages? what do you mean?
[21:25] <balloons> ok, 2 down
[21:26] <sak> when i installed the ppa for ubuntu-x-swat, and updated my source list, i got an error stating this package was only 32bit compatible and that it did not have a 64bit version
[21:27] <balloons> sak, ohh.. it's having you install from ubuntu-x-swat?
[21:27] <balloons> hmm
[21:27]  * balloons tries to remember
[21:30] <sak> no X-staging. ubuntu-x-swap is the name of the ppa
[21:30] <phillw> balloons: you have mail :)
[21:34] <balloons> phillw, indeed I do :-)
[21:35] <balloons> something pressing you need?
[21:49] <balloons> phillw, that's really cool method for using zsync
[21:52] <balloons> sak, I tried to respond to your posts but feel free to clarify in here if you wish
[21:52] <balloons> the beauty of realtime chatting :-)
[21:59] <phillw> balloons: I'll ask Jonathan if he will take the time to write up what is needed for a cron job, it would be minutes for him and hours for me :D
[22:03] <balloons> phillw, lol indeed.. convert that conversation to a wiki page then just incorporate it into your sesssion
[22:03] <balloons> leverage jonathan's help on making the page
[22:04] <phillw> balloons: I'm already on a capture mission for that :D
[22:07] <phillw> balloons: the only thing I really need to check out is if 'bog-standard' ubuntu has genisoimage as default? it is in lubuntu http://pastebin.com/Pg3RQAwH can  you check?
[22:23]  * Noskcaj is away: school
[23:06] <sak> balloons, what do you need me to clarify?
[23:14] <balloons> sak, just what your question about providing info to developers meant
[23:14] <balloons> see my mail :-)