[00:00] <balloons> darran, sak, Noskcaj10 thank you for coming
[00:01] <sak> enjoyed, it, thank you balloons
[00:03] <Noskcaj10> i'll read the logs when i get home, thanks balloons
[00:04] <balloons> Noskcaj10, :-)
[00:04] <balloons> video is up as well: http://www.youtube.com/watch?v=qD_e_xqlBbg
[00:39] <asac> plars: ho ... can you see if maguro and mako are still alive :)?
[00:40] <asac> and if autopilots are in queue on those?
[01:11] <plars> asac: autopilot jobs already ran on mako, and all failed
[01:12] <plars> as could be related to a bug I filed a bit ago, I tried on mako locally and the ui didn't come up on first boot. surfaceflinger segfaulted
[03:08] <asac> plars: how about maguro?
[03:11] <plars> asac: that one's not set up currently, I think the existing ones on grouper and mako are still being debugged
[03:15] <asac> plars: grouper matches what was expected
[03:15] <asac> however its super unimportant device
[03:15] <asac> top prio i maguro
[03:16] <asac> second is mako
[03:16] <asac> unless stuff failed completely dont debug on the infrastructure side... we saw exactly what i see on the dashboard locally as well
[03:16] <asac> all failing on mako should be looked at yes.
[03:17] <asac> but i have no local results to cross check
[03:17] <asac> only maguro i have
[03:17] <asac> thats what is in here:
[03:18] <asac> https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0Au6idq7TkpUUdDhEUy1nM1Jab3N4VGNQS0dQR19lTFE
[03:18] <asac> plars: is setting up maguro scripted?
[03:18] <asac> can you do that and kick them off?
[03:18] <asac> in the hope ... :)
[03:19] <asac> thomi: can you do n4 manual checks on the tests?
[03:19] <asac> seems infrastructure has issues and i want to give folks a heads up tomorrow
[03:19] <asac> default apps would be good enough
[03:19] <thomi> asac: veebers has the nv, and I'm kneck-deep trying to un-bork the unity8 tests.
[03:19] <asac> just to see if they all fail localy as well
[03:19] <asac> kk
[03:19] <asac> veebers: ?
[03:19] <thomi> sorry :(
[03:19]  * veebers reads backlog
[03:20] <asac> yeah... i think now we should kill n7 right away
[03:20] <asac> veebers: its about getting manual results for the tests for n4
[03:20] <asac> seems folks always prefer n7 even though its like zero prio :)
[03:21] <asac> veebers: its trying to run https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0Au6idq7TkpUUdDhEUy1nM1Jab3N4VGNQS0dQR19lTFE#gid=0
[03:21] <asac> on n4
[03:21] <asac> plars: try to just check if its infrastructure issue
[03:21] <veebers> asac: right, can do. Although I may have lead you astray when I said it's a nexus 4, its actually a Galaxy Nexus (the samsung one)
[03:21] <asac> damn
[03:21] <asac> that one i already have
[03:21] <veebers> asac: ah, sorry
[03:21] <asac> plars: can you in some way kick off GN?
[03:22] <asac> i am not sure why we didnt do GN first :)
[03:22] <asac> i thougth i told everybody that GN is first prio :)
[03:22] <asac> and N4 second and all the tablets are somewhere later
[03:22] <asac> i really need those results to give people a heads up tomorrow...
[03:22] <asac> otherwise i will just send what i did on the spreadsheet
[03:22] <plars> asac: working on it, I need to make some changes to the script. Please be aware that these just ran for the first time today, and are not yet considered "in production" tests
[03:22] <asac> which is outdated
[03:23] <veebers> asac: I take it you don't need me to run that manually any more?
[03:23] <asac> plars: well.. i see all devices succeed executing commands every day
[03:23] <asac> why would running the autopilot stuff be different?
[03:23] <plars> asac: I'm talking specifically about the autopilot stuff
[03:23] <asac> so my suspicion is that the n4 really fails all tests
[03:23] <asac> even if run locally
[03:23] <asac> but cant validate locally
[03:24] <asac> plars: iknow... but ultimately its not much than running commands on a provisioned device, no?
[03:24] <plars> asac: no
[03:24] <plars> asac: it's a pretty big difference
[03:24] <asac> really... odd
[03:25] <asac> well. ok.
[03:25] <asac> lets try to get maguro over the line tomorrow
[03:25] <asac> then
[03:25] <plars> asac: I can get it running tonight, if you'll give me just a minute
[03:25] <asac> hehe
[03:25] <plars> asac: but as I said, they are still not "in production"
[03:26] <asac> i dont need warnings... i know its all hot iron... i just need one run on todays images
[03:26] <plars> there are some changes we still need to experiment with on the jenkins side to ensure that they don't allow a job to slip in between them and muck things up
[03:26] <plars> asac: and I'm doing that now
[03:26] <asac> veebers: actually i think if plars cannot get it done getting one more run of the default apps tests on todays image would be helpful
[03:26] <asac> but i really hoped we would get those results from automation :)
[03:27] <asac> plars: yeah. well. dont stress yourself out :)... in worst case i veebers will do a few on GN and i will do a few tomorrow morning here and then send the results :0... but it would be slam dunk to see that on the dashboard
[03:29] <veebers> asac: ack, will run some app tests in a short while
[03:29] <plars> asac: ok, I added it to the job generation scripts, regenerated the jobs, and kicked it off, if you have vpn access you can watch it in progress
[03:38] <asac> yeah if i would be anything less than a moron i would still have VPN access.... but my NM somehow forgot the config and i didnt mangae to set it up when realizing it :)
[03:38] <asac> will check out tomorrow moring
[03:39] <asac> veebers: yeah... can you just put it in the column next to mine for the 08 build?
[03:39] <asac> i will see how far you got and finish off tomorrow
[03:39] <asac> remember to put the right build id on top
[03:39] <asac> thanks a bunch
[03:40] <asac> plars: thanks!! ... dont bother to wait... if they go through they will show up and i will be happy if not. no big deal. we can check tomorrow
[03:40] <veebers> asac: can do
[03:40] <asac> and will just send my disappointing mail with the manual results we are now getting :)
[03:40] <asac> i will also get someone to run through n4 tests locally to see if everything fails
[03:40] <asac> :)
[03:40] <asac> most likely ogra :-P
[03:43] <plars> asac: I'd offer, but my n4 is tied up testing something else at the moment, and I think my isp has finally throttled me
[03:43] <asac> plars: i checked the dashboard
[03:43] <asac> it looks reasonable for mako
[03:43] <asac> http://reports.qa.ubuntu.com/smokeng/saucy/image/2935/
[03:43] <plars> my download rates have slowed to a crawl
[03:43] <asac> share-app succeeded
[03:43] <asac> that means for me infrastructure is clean
[03:43] <asac> and you shouldnt try to figure on your own what the problem is
[03:43] <asac> i am almost 100% sure we will see the same stuff when run locally without utah
[03:44] <asac> so all green from QA infrastructure side for now
[03:44] <asac> dont spend time debugging... i will have ogra check locally and if he sees the same just throw it to the owners of those apps/tests to do everythinhg
[03:44] <asac> triage/fix
[03:44] <asac> etc.
[03:44] <plars> asac: something went awry on notes-app it seems, no tests were run
[03:45] <asac> really?
[03:45] <asac> its 2/2
[03:45] <asac> thats exactly what i would expect
[03:45] <asac> http://reports.qa.ubuntu.com/smokeng/saucy/image/2935/share-app-autopilot/
[03:45] <asac> thats looks realy ok
[03:45] <plars> asac: not share-app, notes-app
[03:45] <plars> asac: notes-app is 0/0
[03:45] <asac> ah-autopilot run -v share_app.tests.test_share.TestShare.test_cancel
[03:46] <asac> right
[03:46] <veebers> asac: to clarify, which order would you like me to test: core apps then default?
[03:46] <asac> thats a bit of a mystery i agree
[03:46] <asac> veebers: default first... then core apps (aka community)
[03:46] <veebers> asac: ack, thanks
[03:47] <plars> dns problems it looks like
[03:47] <asac> well spotted
[03:48] <plars> incidentally, I think having dnsutils in the touch images would be handy
[03:48] <asac> veebers: you might want to be lazy and wait a bit and see if we get results matching roughly what i have in the spreadhseet for the GN
[03:48] <asac> if so you dont need to invest in manual testing i can just through the automated results at folks
[03:48] <veebers> asac: cool, sounds good
[03:48] <asac> not sure how long you are still on, but if you dont see results until 3 hours before your EOD just start manually
[03:50] <veebers> asac: heh, that's about now. But I'll be back on later so can check then
[03:51] <asac> veebers: right. well. i really just care about getting fresh results for GN (maguro) and mako for defaults apps... because those are the apps where we have paid developers doing the work :)
[03:51] <asac> and unity is scheduled for later :)
[03:52] <asac> and unity is being fixed with lots of enthusiasm by saviq and thomi so i am sure they will be great
[03:53] <asac> veebers: so just focus on getting a bunch or all of them done when you find time... as long as i dont have to run all tomorrow i am happy :) (i only have a half day for travel reasons tomorrow to fill out and send mail to folks)
[03:54] <asac> plars: can you send doanac a ping to remind me to talk about dnsutils with me while you are gone? i am completely brain wrecked right now and surely wont remember :)
[03:54] <plars> doanac`: ping
[03:54] <plars> :)
[03:55] <plars> asac: yes, we have a sync tomorrow, I'll tell him to nag you about it
[03:55] <veebers> asac: I see that you don't have the -n flag for phablet-test-run (disables the shell for the app test). I seem to recall that being a requirement for the apps tests, although that may be out of date now
[03:55] <doanac`> plars:  hey
[03:56] <asac> veebers: dunno ... i saw tests go completely green without it
[03:56] <veebers> asac: ah ok, I just had 7 failures with the camera_app (marked green in spreadsheet)
[03:56] <asac> and the grouper results on dashboard seem close enough to believe that what i did manyually is ok
[03:56] <asac> veebers: yeah further to the right you see thomi's n7 results
[03:56] <asac> i think he didnt get the scheme so its not clear :)
[03:57] <asac> moved :)
[03:57] <veebers> asac: right, but I also have a GN and more than tests fail for me, whereas you get green
[03:57] <asac> but its a throwaway spreadsheet anyway :)
[03:58] <asac> veebers: which build?
[03:58] <asac> 09 was completely busted
[03:58] <asac> i had to go back to 08
[03:58] <asac> i woul dhope that -n would give more green :)
[03:58] <veebers> asac: hmm how do you get the build date, I see "JENKINS_BUILD=saucy-41" in /system/ubuntu_stamp
[03:58] <asac> i dont know :(
[03:59] <asac> i dont have the 08 image anymore
[04:00] <asac> i have it still one sec
[04:00] <asac> Downloads/phablet-flash/ubuntu-touch/20130708/saucy-preinstalled-touch-armhf.zip
[04:03] <veebers> asac: ah good point, just did a listing of those directories to get the most recent files
[04:04] <asac> dman
[04:04] <asac> that ziup doesnt even have the ubuntu_stamp file
[04:04] <asac> so *shrug*
[04:04] <doanac`> asac: the maguro results are starting to show up now: http://reports.qa.ubuntu.com/smokeng/saucy/image/2934/
[04:05] <asac> nice
[04:05] <asac> green for share
[04:05] <asac> 84.2% for notes
[04:05] <asac> wait
[04:05] <asac> i had 15 out of 19 failures
[04:05] <asac> if that is 84.2% you calc the success wrong :)
[04:06] <asac> hmm. thats 78.something
[04:06] <asac> feels scary close
[04:06] <asac> to the upside down calc
[04:06] <asac>  :)
[04:06] <asac> doanac`: sure you guys interpret the fail/total and not as success/total?
[04:07] <asac> both me and thomi had 78% failyures
[04:07] <asac> on different devices
[04:07] <asac> i hope this turned to 84% success :) ... but maybe worth checking
[04:07] <asac> that the real output agrees with that number
[04:08] <asac> nice ... phone-app == success :)
[04:08] <doanac`> asac: notes is 16/19
[04:08] <asac> i didnt have a SIM so that would explain my RED
[04:09] <asac> doanac`: in the log? ... what the stuff outputs is fail/total and not success/total.. unless my eyes were on crack the other day
[04:09] <plars> asac: http://reports.qa.ubuntu.com/smokeng/saucy/image/2934/ is starting to show results
[04:09] <plars> ah, doanac` beat me to it :)
[04:09] <asac> plars: :)
[04:09] <asac> dejavu :)
[04:09] <asac> its great
[04:10] <asac> so i love that dejavu :)
[04:10] <doanac`> asac: i think the timing is just perfectly bad, and the rest of the results won't show for another 30 minutes, when the dashboard polls jenkins again
[04:12] <plars> doanac`: what's odd, is that webbrowser was the last one to run, but it's here
[04:12] <asac> that effect is called: race :)
[04:12] <asac> or fail :)
[04:12] <asac> i hope its race
[04:13] <asac> doanac`: can we greedily kick another poll because its late and we love to watch how it goes :)?
[04:13] <asac> or is tha trisky?
[04:13] <asac> (i mean: more risky than landing all thist stuff :))
[04:13] <doanac`> asac: cjohnston and josepht are the guys with access to do that
[04:14] <doanac`> they aren't on
[04:14] <asac> lazy guys.
[04:14] <asac> sleep is for the weak i used to say when i was still a core-dev :)
[04:14] <josepht> doanac`: I'm on, what do you need?
[04:14] <asac> lol
[04:14] <asac> see if we can brute force getting jenkins reults on the dashboard was the idea
[04:15] <asac> see a few lines above
[04:15] <josepht> smoke results?
[04:15] <doanac`> josepht: can you make the qa-dashboard to a quick sync of smoke?
[04:16] <asac> plars: so the maguro tests really got results super fast imo
[04:16] <asac> given that it flashes everything etc.
[04:16] <josepht> doanac`: it's runnning
[04:16] <asac> e.g. 30 minutes for all
[04:16] <asac> hmm. maybe my perception of time is just off
[04:17] <doanac`> asac: i flash once, then run each test only doing reboots in-between
[04:18] <asac> are all jobs going on the same device?
[04:18] <doanac`> yes
[04:18] <asac> thought we had a pool and they are parallized
[04:18] <asac> ok
[04:18] <asac> ic
[04:18] <asac> how is that done in jenkins?
[04:18] <plars> doanac`: unless you beat me to it, I'll experiment with locking that master job to the subordinate jobs in the morning
[04:18] <asac> nevermind
[04:18] <asac> lets talk about that at another time
[04:19] <doanac`> plars: give it a shot. i'm a bit overloaded with a couple of other things.
[04:19] <doanac`> asac: yeah - you don't want to know the world of jenkins
[04:19] <asac> "remember sammy jenkins" :)
[04:19] <plars> doanac`: I'd do it tonight, but staring at xml at 12 am can only spell disaster
[04:19] <asac> http://images.search.yahoo.com/images/view;_ylt=A0PDoQ3eg99RKHwAC0GJzbkF;_ylu=X3oDMTFxMzBjMGUyBHNlYwNzcgRzbGsDaW1nBG9pZAMyMjllNjZhMDQxMjIxZGEwZjU5ZGE0NGQyNWZiYzEzZQRncG9zAzQ-?back=http%3A%2F%2Fimages.search.yahoo.com%2Fsearch%2Fimages%3F_adv_prop%3Dimage%26va%3Dremember%2Bsammy%2Bjenkins%26fr%3Dcrmas%26tab%3Dorganic%26ri%3D4&w=461&h=279&imgurl=i.stack.imgur.com%2FFfq6w.jpg&rurl=http%3A%2F%2Fmovies.stackexchange.com%2Fquestions%2F10526%2Fwhat-is-th
[04:20] <asac> oops... damn long urls
[04:20] <asac> i forgot :)
[04:21] <josepht> the dashboard pull is done
[04:21] <asac> nice... 0% :)
[04:21] <doanac`> josepht: we have a small bug
[04:22] <asac> plars: doanac`: can you confirm that http://reports.qa.ubuntu.com/smokeng/saucy/image/2934/ shows all jobs that were supposed to run?
[04:22] <doanac`> we are missing 2 jobs
[04:22] <doanac`> josepht: mediaplayer and camera. let me share links ...
[04:22] <doanac`> https://jenkins.qa.ubuntu.com/view/All/job/smoke-saucy-touch-apps-maguro/
[04:25] <pitti> Good morning
[04:25] <asac> 6:25 and pitti is booting up :)
[04:25] <asac> thats ... err... scary
[04:27] <doanac`> i usually take it a sign i should go to sleep when I see pitti logging in for the day
[04:27] <pitti> heh
[04:27] <asac> seems we need NZ after all to get a 24/7 sprint going
[04:27] <asac> we dont need NZ i mean
[04:27] <asac> THATS scary
[04:27] <asac> pitti: go to bed :)
[04:27] <asac> for 2h
[04:27] <pitti> asac: I hope you aren't in Germany ATM
[04:27] <asac> no... east coast :)
[04:28] <asac> monday i am back in central europe ... working 24/7 :)
[04:30] <pitti> hah
[04:30] <pitti> asac: don't forget to work in the plane :)
[04:30] <asac> german mode
[04:30] <asac> :)
[04:33] <asac> josepht: did you figure whats going on with those?
[04:34] <asac> otherwise i believe we all can go to sleep ... and plars to early vacation :)
[04:34] <josepht> asac: yeah those two jobs don't have any utah artifacts
[04:34] <plars> asac: no, I'm here tomorrow for sure
[04:34] <josepht> doanac`: ^^
[04:34] <asac> plars: man. its a great achievement to cut and just take overhours swap day :)
[04:34] <asac> but wll.. i know you wont listen
[04:35] <asac> veebers: so can you do camera and mediaplayer only?
[04:35] <doanac`> josepht: sorry. I could have sworn i saw yamls for them.
[04:36] <doanac`> i'll dig into the job
[04:36] <doanac`> sorry to waste your time
[04:36] <josepht> doanac`: no worries
[04:36] <asac> plars: josepht: doanac`: thanks. great stuff. talk to you tomorrow! i have all i need for now
[04:36] <asac> dont sweat it :)
[04:36] <asac> folks should now go and run stuff locally and fix :)
[04:36] <veebers> asac: I've done cam, friends and gallery was about to do media player
[04:36] <asac> nice
[04:36] <asac> veebers: thanks!
[04:36] <asac> i have enough data
[04:36] <asac> and folks will have enough work for the rest of the week
[04:37] <asac> :)
[04:37] <doanac`> plars: josepht: asac: the problem: https://jenkins.qa.ubuntu.com/view/All/job/saucy-touch-maguro-smoke-mediaplayer-app-autopilot/1/console
[04:37] <doanac`> we have a disappearing maguro in the lab
[04:38] <plars> doanac`: that can't be good
[04:38] <plars> looking
[04:38] <asac> yeah. i have the results i want... so now you can do the fixes needed like fixing the locking etc.
[04:38] <asac> :)
[04:38] <plars> doanac`: it's actually there, looks like an adb race
[04:38] <doanac`> ugh - i worry adb doesn't scale well
[04:39] <doanac`> this is awesome. i think gema just got online
[04:39] <doanac`> we are literally working around the clock
[04:39] <asac> hehe
[04:39] <asac> as i said
[04:39] <josepht> I'm wearing my "Quite Awesome" shirt
[04:39] <asac> even without NZ we could work 24h
[04:39] <asac> thats scary
[04:39] <asac> hence... guys.. you did an amazing job
[04:40] <asac> i have all i needed... why not start digging into whats going on tomorrow (at least you guys in texas :))
[04:40] <asac> thanks
[04:40] <josepht> good night
[04:40] <asac> n8!!
[04:40] <asac> see y0ou tomorrow
[04:42] <pitti> n8 asac
[06:54] <jibel> good morning
[08:23] <Saviq> asac, ping
[08:34] <DanChapman> Good Morning all :-)
[08:41] <elfy> hi DanChapman
[08:44] <DanChapman> Hey elfy :-)
[12:02] <asac> Saviq: bongo
[12:03] <Saviq> asac, hey, we want to start looking into memory / performance / resource testing in unity8
[12:03] <Saviq> asac, can you point me at someone who I could talk to about that?
[12:04] <Saviq> asac, ideally integrated with whatever reporting / shooting $dev solution you have for regressions
[12:04] <asac> yeah... let me wake up and think :)
[12:04] <asac> maybe you can join a hangout in a couple minutes with tvoss?
[12:04] <asac> lets say at :15?
[12:05] <asac> will ping you once ready :)
[12:05] <asac> could be a couple minutes later than that
[12:06] <Saviq> asac, hmm in McDo's now for power (outage at home) - not the best place to hang out
[12:07] <Saviq> asac, should be back 1300UTC
[12:07] <asac> Saviq: :) hope its not breakfast time for you
[12:07] <asac> Saviq: thats in one hour?
[12:07] <Saviq> yes
[12:07] <asac> sounds good
[12:07] <Saviq> asac, ah, wrong...
[12:07] <Saviq> asac, thought I'm free until 1330UTC
[12:08] <Saviq> asac, but I've a meeting from 1300UTC to 1450UTC
[12:08] <Saviq> asac, can we do later? or Monday?
[12:09] <asac> Saviq: monday would be best. qa team has pulled huge things last nights and i think they need some moment for recovery :).
[12:09] <asac> Saviq: is this for desktop or phone?
[12:09] <Saviq> asac, phone
[12:09] <asac> cool. yeah. maybe lets chat a bit here...
[12:10] <asac> Saviq: do you alreayd have some kind of tests and just want to sort how to run it on infastructure and how to make the reporting happen?
[12:10] <asac> or do you want to first check sanity on your test approach?
[12:11] <Saviq> asac, we have a set of unit tests (dpkg-build-time), isolated ui tests (CI-time) and some autopilot tests (not nearly enough)
[12:12] <Saviq> asac, but none of them had any performance measurement in mind
[12:12] <Saviq> asac, so we simply need to pick brainz about how to approach that
[12:12] <asac> right.
[12:13] <asac> i think tvoss would be the right guy to discuss the high level approach etc. first
[12:13] <asac> he has been good in setting good standards for the memory budgeting thing.
[12:14] <asac> and gema should appoint someone from QA team i would think to have this discussion. let me talk abit around today.
[13:46]  * cjohnston blames balloons for breaking the dashboard :-)
[14:05] <balloons> wah!
[14:05] <balloons> is everything I ever wanted on the dashboard done cjohnston ?
[14:05] <cjohnston> balloons: I blame you.. http://reports.qa.ubuntu.com/smokeng/saucy/image/2933/webbrowser-app-autopilot/
[14:10] <balloons> finally these things are coming online, sheesh!
[14:10] <balloons> is mir online yet?
[14:34] <slickymaster> balloons: hi balloons. sorry for bothering, when we get the time can you take a look at this?
[14:34] <slickymaster> when you
[14:34] <slickymaster> https://code.launchpad.net/~slickymaster/ubuntu-manual-tests/xfce4-power-manager-settings/+merge/174360
[14:38] <balloons> slickymaster, yes of course
[14:38] <DanChapman> balloons, Morning! .... it is morning where you are right lol
[14:40] <balloons> Yes, still morning DanChapman :-)
[14:40] <balloons> whew, so today is all about reviewing code and helping out.. so if you've got something for me to look at today's the day :-)
[14:42]  * DanChapman is seeing if he has anything for balloons to look at
[14:44] <asac> doanac`: did you recover yet?
[14:44] <asac> :)
[14:46] <asac> plars: :)
[14:46] <plars> asac: we're in a meeting right now
[14:47] <asac> kk
[14:47] <asac> talk in a bit then
[15:04] <DanChapman> balloons, I'm looking at the Terminal test in the dev branch at the moment. And can see that it can now be introspected which i will do. What would you say are the requirements of the test? I can't see how we can test the actual xterm emulator window anymore than create a file and check the file system for it. Would you say more focus on the dialog windows i.e. profiles, shortcuts, search. Aswell as the usual fullscreen, tabs e
[15:04] <DanChapman> tc
[15:05] <balloons> DanChapman, yes terminal is a bit more funny, but worth checking out.. Window management is a good one. we can't test the color stuff sadly.. I wonder about the fonts or "other" profile things
[15:08] <DanChapman> balloons, ok cool I was going to strip the colours and backgrounds out. I'll have a play and see how it goes
[15:09] <balloons> sounds fine.. Keep it simple for now and see what happens. Introspection is already going to make the whole thing saner!
[15:10] <DanChapman> It is pretty wild atm!
[15:22] <slickymaster> balloons: thanks, let us see what noskcaj and elfy had to say about it
[15:23]  * elfy is happy with it as it is currently
[15:24] <slickymaster> elfy: thank you, I'll leave it as it is and consider it ready to merge
[15:25] <slickymaster> balloons: if it's also ok with noskcaj, I consider the test good and done to be merged
[15:28] <elfy> slickymaster: I'll check spelling and format in a moment and approve if it's ok
[15:28] <slickymaster> elfy: Thanks. I appreciate it :)
[15:29] <balloons> elfy, thanks mate
[15:31] <elfy> slickymaster: "The Display Power Management Signaling (DPMS) is disabled" too L's in signalling - but I'm really not too concerned about that
[15:31] <elfy> given that American's can't spell colour properly ... :p
[15:31] <elfy> but you can change it if you want
[15:32] <DanChapman> elfy, hey mate. :-) I have made a start on getting some autopilot tests together for xubuntu. Evince worked straight away without any mods but firefox and fileroller ( which has a diff UI to ubuntu) are not working. Although I haven't tried the new firefox test yet. I will try to get those two working over the weekend :-)
[15:32] <elfy> you are a superstar :)
[15:32] <slickymaster> elfy: LOL
[15:34] <slickymaster> elfy: I'll fix tonight. Right now I'm at work and behind a proxy and not able to push the branch
[15:35] <elfy> I've approved it slickymaster - really not worried about that.
[15:35] <elfy> I could come up with hundreds of spelling/grammar errors in testcases
[15:35]  * DanChapman looking forward to seeing 0 fails on jenkins tonight 
[15:36] <elfy> balloons: I've approved that one now - if I knew how to actually merge it I would
[15:36] <slickymaster> elfy: ok, elfy, I'll leave as it is, then and assign myself to a new one (while continuing the settings manager)
[15:36] <balloons> elfy, merging isn't so bad at all
[15:36] <elfy> yep - cool slickymaster :)
[15:36] <balloons> DanChapman, wahoo! 0 fails!
[15:37] <elfy> balloons: I doubt it is - but trying to get someone to walk through bzr things doesn't always work out :D
[15:37] <balloons> DanChapman, not today, but we need to get the ubiquity stuff added too.. I know we talked about it. There's some technical work and ideas to be done
[15:39] <DanChapman> balloons, yeah pitti said he had talked with jibel about it and he was going to look into how to fake a disk drive to get it working.
[15:40] <balloons> right, that was going the otto route I believe... it'll be more of a challenge that way I think :-)
[15:40] <balloons> he's up to it!
[15:40] <elfy> balloons: I would have assumed that doing bzr merge lp:~slickymaster/ubuntu-manual-tests/xfce4-power-manager-settings would do the job - but then again it might not :)
[15:40] <balloons> elfy, checkout the trunk branch
[15:40] <balloons> then do a bzr merge lp:~slickymaster/ubuntu-manual-tests/xfce4-power-manager-setting
[15:41] <balloons> then commit and push back to trunk
[15:41] <balloons> that's it.. you already knew how :-)
[15:41]  * elfy wanders off to try and to get a rest from writing stuffs
[15:42] <elfy> balloons: hang on - don't you add numbers or something?
[15:42] <DanChapman> balloons, what route do you think would be better?
[15:42] <balloons> elfy, I do, but that's for the sync to the tracker itself
[15:43] <elfy> k
[15:43] <balloons> so if you wanted to do that step manually, basically you would copy and paste the testcase into a new test on the tracker. Then name it id_Name
[15:43] <balloons> that's the format. But you don't have to do that at all. Just merge without it and I'll add the id later when I run the sync
[15:43] <balloons> I'd give everyone the sync tool, but it uses my apikey :-)
[15:43] <elfy> see  - knew it - not as simple as you said - you always forget the steps you know :D
[15:44] <balloons> I'm telling you not to worry about that part :-)
[15:44] <balloons> just merge and ignore the id stuff :-)
[15:44] <elfy> balloons: no, not that - the other "that's it.. you already knew how :-)" bits
[15:45] <balloons> elfy, lol.. you did.
[15:45] <elfy> don't worry about it now - I'll catch up with you some time early next week
[15:45] <elfy> what you mean - lol you did - all I get here are errors
[15:45] <balloons> enjoy your weekend mate!
[15:45] <balloons> I hear even the UK is warm this week :-
[15:45] <elfy> yep
[15:46] <elfy> and little one is off to Big Town with her school - dad is free ... ;)
[15:46] <balloons> NICE!
[15:46] <DanChapman> elfy enjoy it!!
[15:46] <elfy> balloons: on a serious note I will catch up early next week about this - I'd like to sort out the howto
[15:47] <balloons> DanChapman, did you attempt or plan to attempt getting through the video I put together on autopilot?
[15:47] <elfy> DanChapman: I shall
[15:50] <DanChapman> balloons, I plan to have a look tonight once the  little devils are asleep. :-)
[15:50] <elfy> balloons: of course I could hassle knome  about it as well :)
[15:50] <knome> what?
[15:50] <slickymaster> elfy: yeah elfy, have agreat weekend with no strings attached
[15:51] <elfy> knome: I could hassle you about going through merging approved testcases in the main thingy
[15:52] <knome> elfy, 15mins, ok? :)
[15:52] <elfy> ok - cheers :)
[16:46] <knome> elfy, you still around? :)
[16:47] <elfy> I am
[16:51] <elfy> knome: whenever you've time
[16:54] <knome> elfy, i have time now, just go ahead and shoot ;)
[16:55] <elfy> knome: so how do I merge this https://code.launchpad.net/~slickymaster/ubuntu-manual-tests/xfce4-power-manager-settings/+merge/174360
[16:55] <knome> elfy, the page says: To merge this branch: bzr merge lp:~slickymaster/ubuntu-manual-tests/xfce4-power-manager-settings
[16:55] <knome> elfy, so in your lp:ubuntu-manual-tests branch directory, run that command
[16:56] <knome> then commit and push
[16:56] <knome> (you probably want to move the file under Xfce before you commit)
[16:56] <knome> i created the Xfce directory to keep the repository clean
[16:57] <knome> the status will be changed to "merged" automatically
[16:57] <elfy> knome: that's better - getting there
[16:59] <elfy> knome: ok - moved the file to XFCE - so if I commit it tells me there's stuff missing now - do I have to bzr add first?
[16:59] <elfy> alternatively I can just move it later to XFCE :)
[16:59] <knome> what does it say is missing?
[17:00] <elfy> the one I'm trying to merge - it expects it in packages
[17:00] <knome> can you paste the line so i can paste you an exact command to run
[17:00] <knome> (i'll also explain why it thinks you have it missing)
[17:01] <elfy> knome: http://pastebin.com/c3a8Djg8
[17:01] <knome> great, so as usually, when you add new files into a repository, you'd run: "bzr add ."
[17:01] <elfy> I can understand why it thinks it's missing - it is - I can also understand why it's unknown - it is
[17:01] <knome> that would make the unknown -line go away
[17:01] <elfy> yep
[17:02] <knome> for the missing line; bzr expects you to have files that were in the merged branch
[17:02] <elfy> should I do that then?
[17:02] <knome> if you moved those, you should run "bzr del old-name", in this case "bzr del testcases/packages/xfce4-power-manager-settings\ tests"
[17:03] <knome> yup, run both the add and del command
[17:03] <knome> then you shouldn't get either of the warnings when you do the commit (or see the status with "bzr status")
[17:03] <elfy> testcases/packages/xfce4-power-manager-settings tests does not exist
[17:03] <knome> did you use "\ " ?
[17:04] <elfy> yea
[17:04] <knome> weird
[17:04] <elfy> status shows the added and the pending one now
[17:04] <knome> but no missig ones?
[17:04] <knome> *missing
[17:04] <elfy> nope
[17:04] <knome> ok, then you're fine!
[17:04] <elfy> commit shows the added and pending merges
[17:05] <knome> yup, that's fine
[17:05] <elfy> k commited it
[17:05] <knome> when it does that, it automagically handles setting the status of the MP merged
[17:06] <knome> now push
[17:06] <elfy> ok - bit more help then :p
[17:07] <elfy> push how
[17:07] <knome> bzr push
[17:07] <knome> (you did the local commit, now push to the parent branch)
[17:07] <elfy> bzr push :parent ?
[17:07] <knome> or bzr push if you've done :parent at least once
[17:08] <elfy> never done pasrent
[17:08] <knome> then do :parent, yep
[17:08] <elfy> seems to have done something :)
[17:08] <knome> you should only need to do that once
[17:08] <knome> yup! so in https://code.launchpad.net/~ubuntu-testcase/ubuntu-manual-tests/trunk
[17:08] <knome> you'll see your commit #165
[17:08] <knome> and in https://code.launchpad.net/~slickymaster/ubuntu-manual-tests/xfce4-power-manager-settings/+merge/174360
[17:08] <knome> the status is merged
[17:09] <knome> and effectively the merge proposal is now "closed"
[17:09] <elfy> thanks :)
[17:10] <slickymaster> elfy: I can confirm that, just received the email from LP stating it.
[17:10] <knome> np
[17:10] <knome> anything else you need help with?
[17:10] <elfy> knome: nope - that's cool - thanks :)
[17:10] <elfy> just make some notes now lol
[17:10] <knome> quickly re: the id's you were asking before:
[17:10] <elfy> slickymaster: thanks
[17:11] <elfy> id's ?
[17:11] <slickymaster> elfy: it's me who thnak you, elfy. not the other way around
[17:11] <elfy> :)
[17:11] <knome> elfy, 18:43  balloons: so if you wanted to do that step manually, basically you would  copy and paste the testcase into a new test on the tracker. Then name  it id_Name
[17:11] <slickymaster> elfy: i wish a very good (free) weekend
[17:12] <elfy> knome: oh I see - the numbering thing
[17:12] <knome> elfy, so basically, now that a new test is in the repository, you go ahead and add it to the testing tracker (no bzr black magic included)
[17:12] <knome> elfy, and once you've added it, the tracker will give you a test ID
[17:13] <knome> elfy, once you have that, rename the file in the local branch to "thatID_testname" and commit+push
[17:13] <elfy> ok - that all obviously makes loads of sense to you ;)
[17:14] <elfy> leave it for the time being - I'll look at that a bit later
[17:14] <knome> elfy, so the ID's are more for us humans to track that the tests have been added to the tracker and on the other hand, find those tests in the tracker easily. does that make sense?
[17:14] <knome> elfy, well as balloons said, he can handle it
[17:14] <elfy> yep
[17:14] <knome> (i've let him do that before, and i think he might have some tool for it)
[17:14] <elfy> indeed - just want to get my head around all of these things so I can at least keep up with our stuff
[17:15] <knome> yup
[17:15] <elfy> but for the moment - that's either another day or an SEP
[17:16] <knome> SEP? :P
[17:16] <elfy> someone else's problem :)
[17:16] <knome> hehe
[17:16] <knome> yup
[17:16] <knome> if you need a new test in the tracker quickly, feel free to ping me
[17:17] <knome> and i'll handle that stuff
[17:17] <elfy> one thing at a time
[17:17] <elfy> knome: ok :)
[17:17] <elfy> knome: while on the subject of tests - someone who actually uses gmb should do the testcase ...
[17:18] <knome> i'm not using gmb
[17:18] <knome> ....right now
[17:18] <knome> ;>
[17:18] <elfy> LOL
[17:19]  * elfy can write the testcase ... open/close/wait 6 hours for it to read library/give up/use clementine :D
[17:19] <knome> lol
[17:19] <elfy> knome: thanks for your help though :)
[17:20] <knome> no problem at all
[17:20] <knome> if nobody seems to be writing the gmb test later in the cycle, i can do that at some point
[17:20] <elfy> ok
[19:07] <Letozaf_> balloons, Hi
[19:13] <Letozaf_> balloons, I wanted to do some other tests on sudoku app, but I see there is a merge proposal pending, do I have to wait for the merge to be accepted before pulling the branch ?  what happens If I pull it now and work on it and the merge gets accepted ?
[19:13] <balloons> Letozaf_, hello!
[19:13] <Letozaf_> balloons, :)
[19:14] <balloons> Letozaf_, no worries on active mp
[19:14] <Letozaf_> balloons, ok thanks
[19:14] <balloons> unless the merge proposal is changing something your going to change or want to change (literally the same lines) it won't have an effect
[19:14] <balloons> so I was looking at this: https://code.launchpad.net/~carla-sella/ubuntu-rssreader-app/ubuntu-rssreader-test-add-view-feeds/+merge/173316
[19:15] <balloons> did you want to make those changes? The team was ready to merge as-is but we should fix it up as francis talked about
[19:16]  * Letozaf_ did not see the last part
[19:16]  * Letozaf_ is reading it now
[19:20] <Letozaf_> balloons, I will try to fix what's asked, sorry I probably missed the email
[19:20] <balloons> no worries.. I just didn't want to do something you might be working on ;-)
[19:21] <Letozaf_> balloons, :D  Let's say I kind of got used to it :D
[19:21] <Letozaf_> balloons, funny eh! if I pick something, someone else does it
[19:21] <Letozaf_> balloons, lol
[19:25] <Letozaf_> balloons, just another doubt, when I've done the changes to the rssfeed app, do I just have to commit an push it to the same branch it's now , will it be ok ?  never made changes to an already proposed to merge branch so no quite sure what's the right way
[19:28] <balloons> yes, push to the same branch
[19:28] <balloons> you'll see it'll just update the diff below on the merge proposal :-)
[19:29] <Letozaf_> balloons, thanks
[20:18] <Letozaf_> balloons, the ubuntu-rssreader-app test should be fine now, I applied fginther's suggestions
[20:18] <balloons> Letozaf_, cool :-)
[20:18] <Letozaf_> balloons, :)
[20:18] <balloons> hopefully you'll stop being followed on writing tests eh?
[20:19] <elfy> balloons: hi - got that thing merged in the end - I'll try and keep an eye on manual tests - most seem to be coming from xubuntu atm anyway :)
[20:24] <Letozaf_> balloons, :p yeah hope so :D it's a bit weired
[20:24] <elfy> balloons: while I remember do you not want underscores in testcase names then?
[20:24] <Letozaf_> balloons, well I'm doing a lot of exercise in autopilot tests "for nothing" lol
[20:29] <balloons> elfy, please no underscores :-)
[20:29] <elfy> :)
[20:30] <balloons> Letozaf_, lol, I think it's over for now.. no one is following you on rss reader for sure
[20:30] <balloons> oh I should approve so jenkins will merge your fixes
[20:32] <balloons> Letozaf_, odd, does the changes run on your box/
[20:36] <Letozaf_> balloons, yes I tried the test before pushing it
[20:36] <balloons> wild.. I guess it just dislikes me!
[20:36] <Letozaf_> balloons, isn't it working on yours
[20:37] <Letozaf_> balloons, let me try  to move the test to another dir and pull the one that's in the branch
[20:37] <Letozaf_> balloons, maybe the push did not work correctly
[20:37] <balloons> no worries.. the build bot will solve it for us
[20:37] <balloons> if it works for jenkins, it works :-)
[20:37] <balloons> give it a couple mins to pick it up and try it
[20:37] <balloons> i have funny things on my box sometimes
[20:38] <Letozaf_> balloons, ok because it already happened that push sort of left files on my box and did not find them in the branch
[20:40] <balloons> what's bzr status say?
[20:40] <balloons> if it doesn't look right to you, then it's worth fixing :-)
[20:41] <balloons> ideally bzr status should be blank and show nothing after you commit and push
[20:41] <balloons> if there's stuff in there, then you have local modifications that didn't get pushed up
[20:43] <balloons> Letozaf_, ^^ what's bzr status say?
[20:44] <Letozaf_> balloons, nothing
[20:45] <balloons> Letozaf_, then you should be good :-)
[20:45] <Letozaf_> balloons, hope  so :) anyway I ran the test again and it worked
[20:45] <Letozaf_> balloons, I mean the one on my box
[20:45] <balloons> right right..
[20:46] <balloons> me wonders where the build bot is\
[20:46] <balloons> ohh silly me, I didn' thit approve
[20:46] <balloons> argh
[20:51] <Letozaf_> balloons, :( I see a fail
[20:52] <balloons> Letozaf_, so if you click that link it links to this page
[20:52] <balloons> http://91.189.93.70:8080/job/generic-mediumtests/78/?
[20:52] <balloons> which has videos of the runs :-)
[20:54] <Letozaf_> balloons, cool, but there must be something wrong with my browser, I only see a black screen with a white mouse pointer
[20:54] <balloons> http://91.189.93.70:8080/job/generic-mediumtests/78/artifact/ubuntu_rssreader_app.tests.test_rssreader.TestMainWindow.test_view_feeds%20%28with%20mouse%29.ogv
[20:55] <balloons> one of the tests the app doesn't launch.. so it's blank
[20:55] <balloons> that one shows the other test run
[20:55] <Letozaf_> balloons, now I saw the other one
[20:56] <Letozaf_> balloons, cool, let me try to pull the branch on my box and see if the same happens, because it works here
[20:57] <Letozaf_> balloons, I pulled the branch and it says 17 revisions, they should be 18
[20:57] <balloons> ll
[20:57] <balloons> ahh
[20:57] <balloons> did you bzr push?
[20:58] <balloons> maybe you forgot to push that last one :-)
[20:58] <balloons> ohh wait, no I do see i have r18
[20:58] <Letozaf_> balloons, that's strange
[20:59] <Letozaf_> balloons, I mean that I pulled the branch and see 17 instead of 18 :?
[20:59] <balloons> ahh.. I did get rev 18 when I pulled is all
[20:59] <Letozaf_> balloons, I will try again
[21:01] <Letozaf_> balloons, zzz I pulled the lp:ubuntu-rssreader-app and not mine lol
[21:01] <Letozaf_> balloons, mabye if I pull the right one ....
[21:03] <Letozaf_> balloons, I confirm it works on my box
[21:03] <Letozaf_> balloons, that's quite weired
[21:05] <balloons> Letozaf_, lol gotcha!
[21:05] <balloons> ok, well let's fix this before it's too late for you there :-)
[21:05] <balloons> got 10 mins?
[21:06] <Letozaf_> balloons, ok
[21:07] <Letozaf_> balloons, but I pulled the right branch now and it works :?
[21:08] <balloons> Letozaf_, hmmm.. so yea, i see some changes we can still tweak in here
[21:09] <balloons> I think fginther is saying that the buildbot will randomly not work
[21:09] <balloons> if I approve again it may work just fine
[21:09] <balloons> so his fixes and suggestions are to try and prevent it from randomly failing
[21:09] <Letozaf_> balloons, hope so :)
[21:10] <balloons> so your lambda: self.assertThat lines
[21:10] <balloons> he was trying to explain how to do that a bit differently
[21:11] <balloons> you want to use lambda: to allow you to use the eventually operator
[21:11] <balloons> so you can do this:
[21:11] <balloons> canonical_feed = lambda: self.main_window.get_canonical_feed()
[21:11] <balloons>         #does it exist?
[21:11] <balloons>         self.assertThat(canonical_feed, Eventually(NotEquals(None)))
[21:11] <balloons> vs
[21:12] <balloons> canonical_feed = self.main_window.get_canonical_feed()
[21:12] <balloons>         #does it exist?
[21:12] <balloons>         lambda: self.assertThat(canonical_feed, Eventually(NotEquals(None)))
[21:12] <balloons> make sense?
[21:13]  * Letozaf_ is looking at here code
[21:13] <Letozaf_> balloons, yes
[21:15] <fginther> Letozaf_, let me take a look at some of those failures, one of them looks like the app couldn't start
[21:15] <balloons> go for it.. I'm going to try and clean up the code a little with some edits I would make.. we'll see what we think
[21:15] <fginther> Letozaf_, also I can't view the pretty videos from chromium, I have to use firefox or wget
[21:16] <Letozaf_> fginther, same here had to use firefox
[21:31] <fginther> Letozaf_, new tests results http://91.189.93.70:8080/job/generic-mediumtests/79/testReport/
[21:32] <fginther> Letozaf_, 78 failed because the jenkins config had been reset and lost my latest changes.
[21:32] <Letozaf_> fginther, :(
[21:33] <fginther> Letozaf_, The error in 79 is caused by a missing import for "StateNotFoundError". I gave you some incomplete advice.
[21:33] <fginther> let me find the right module for that
[21:33] <Letozaf_> fginther, thanks
[21:33] <balloons> fginther, I just changed it to be an open expect
[21:33] <balloons> *except
[21:33] <balloons> my wip is herE: lp:~nskaggs/ubuntu-rss-reader/carla-feed-commit
[21:33] <fginther> that works too :-)
[21:34] <balloons> we don't really care why it didn't work :-)
[21:34] <balloons> so Letozaf_ your before and after piece for the insert
[21:34] <balloons> we can long tap on the feed name and tell it to update
[21:34] <fginther> sometime we do :-)  It can mask the real failure and make it a pain to debug
[21:34] <balloons> otherwise I don't see how it will work
[21:35] <balloons> fginther, well, true I suppose
[21:35] <balloons> but your blind returning anyway
[21:35] <balloons> if it's a non state error, then it could be confusing
[21:37] <fginther> Letozaf_, "from autopilot.introspection.dbus import StateNotFoundError"
[21:37] <Letozaf_> fginther, ok let me insert this
[21:38] <Letozaf_> balloons, fginther or are you guys going to do it ?
[21:39] <fginther> Letozaf_, I'll give it a try, don't want to have to tell you I was wrong twice :-)
[21:40] <Letozaf_> fginther, :-)
[21:41] <balloons> mm ok I'm seeing why I'm having issues
[21:41] <balloons> this return self.app.select_single('Subtitled', objectName='feedItem')
[21:41] <balloons> more than 1 feed means this returns multiple
[21:43] <fginther> balloons, yeah, the testing expects a clean slate
[21:46] <balloons> wahoo success
[21:46] <Letozaf_> balloons, fginther \o/
[21:54] <balloons> bah
[21:56] <balloons> wow..
[22:00] <fginther> Letozaf_, balloons, I pushed my wip attempt here: lp:~fginther/ubuntu-rssreader-app/test-update-take-2
[22:01] <fginther> Letozaf_, balloons, I have to drop off soon
[22:02] <balloons> this is my as-is code:  lp:~nskaggs/ubuntu-rssreader-app/carla-feed-commit
[22:03] <Letozaf_> balloons, fginther my problem is I cannot test on jenkins ... so I have to rely on you
[22:04] <balloons> basically the one test works
[22:04] <fginther> Letozaf_, I understand. I sometimes use a VM (like virtual-box to create an environment similar to jenkins)
[22:04] <balloons> the other doesn't
[22:05] <balloons> the issue is the bloody select_single call for grabbing the feed AttributeError: 'NoneType' object has no attribute 'text'
[22:05] <fginther> balloons, that probably means the feed object wasn't available yet
[22:05] <Letozaf_> fginther, but how is it configured, I mean the VM
[22:05] <balloons> fginther, I'm sure your right.. but the check isn't working.. I suppose looping on sleep
[22:06] <fginther> Letozaf_, balloons, I gotta go (my wife will yell at me if I don't) I'll try to help out later this evening
[22:07] <Letozaf_> fginther, :)
[22:07] <fginther> Letozaf_, the general idea of a VM is that it just runs a raring desktop, the fact that it runs *really* slow is what makes it interesting for running autopilot tests, you get completely different timings
[22:07] <slickymaster> balloons: Hi, do you mind I ask you a quick question?
[22:07] <Letozaf_> fginther, oh so maybe I will try on a VM
[22:07] <Letozaf_> fginther, thanks
[22:08] <balloons> there's actually a cooler trick you can do
[22:08] <balloons> use Xephyr
[22:09] <balloons> nest an xserver and launch the app into it
[22:09] <balloons> you can make it unaccelerated
[22:09] <Letozaf_> balloons, Xephyr ? never heard of it but I will google  to find out
[22:12] <slickymaster> Noskcaj: Hi, do you mind I ask you a quick question?
[22:13] <Noskcaj> slickymaster, sure
[22:13] <Noskcaj> !ask
[22:14] <slickymaster> Noskcaj: so, I'm continuing, in order to finish it, to work on the settings manager test. But I see that this test already has an ID abd is on the XFCE folder
[22:15] <Noskcaj> Just branch ubuntu-manual-tests and work on it. Request a merge when you think what you have should be added
[22:15] <slickymaster> iand now, when I'll want to bzr push the some  alterations I've made, do i use the bzr branch lp:~slickymaster/ubuntu-manual-tests/
[22:15] <slickymaster> or do i use bzr branch lp:~slickymaster/ubuntu-manual-tests/
[22:15] <slickymaster> Xfce ?
[22:15] <balloons> Letozaf_, well it's all around late
[22:15] <balloons> I'm leaving my branch as is..
[22:16] <balloons> I guess we fail.. for now :-(
[22:16] <Letozaf_> balloons, quite...
[22:16] <Letozaf_> balloons, ok maybe during the week end I can try on a VM or xephyr...
[22:16] <slickymaster> Noskcaj: is the bzr any different?
[22:16] <Letozaf_> balloons, and see if I get your problems
[22:16] <balloons> Letozaf_, yes, until then ;-)
[22:17] <balloons> have a good weekend
[22:17] <balloons> food time for me!
[22:17] <Letozaf_> balloons, enjoy
[22:17] <Letozaf_> bye
[22:17] <Noskcaj> slickymaster, the for bzr, just skip the "add" bit
[22:18] <Noskcaj> use lp:~slickymaster/ubuntu-manual-tests/WHATEVER-YOU-WANT
[22:18] <slickymaster> Noskcaj: and do I keep the ID number in the test name?
[22:18] <Noskcaj> yep
[22:19] <slickymaster> Noskcaj: ok, thanks a lot. I won't bother anymore
[22:19] <slickymaster> * bother you
[22:19] <Noskcaj> remember: The changes don't do anything till balloons or i merge the test, and we won't do anything that breaaks the tracker
[22:19] <slickymaster> Noskcaj: good to hear it, and to know it
[22:19] <Noskcaj> slickymaster, it's not bothering us. Being on IRC is good because it's easier to contact you
[22:20] <phillw> balloons: can you have a look at the latest email posting from Vasudevan Kottilil i'm not a unity user.
[22:20] <slickymaster> Noskcaj: I know that, thing is during the day it's difficult for me to conciliate work hours and 'this' hours
[22:20] <phillw> or anyone? :)
[22:21] <Noskcaj> slickymaster, ok.
[22:21] <slickymaster> Noskcaj: I'll try to show up here more. anyway, thanks, again
[22:21] <Noskcaj> This does count as volunteering and can be used as a referral or previous experience
[22:22] <slickymaster> see you tommorow :)
[22:22] <Noskcaj> ok, bye.