[03:56] <kotux> good evening
[03:57] <kotux> ping balloons
[05:07] <pitti> Good morning
[07:11] <jibel> good morning
[09:10] <gema> apw: nicely fixed that regression
[09:10] <gema> apw: thanks for spotting it and getting it fixed
[09:11] <apw> gema, yeah it looks much better now
[09:11] <gema> indeed
[09:11] <pitti> boot speed?
[09:11] <gema> yup
[09:11] <apw> pitti, yeah
[09:11] <pitti> cool
[09:11] <gema> pitti: i.e. http://reports.qa.ubuntu.com/bootspeed/machine/1/i386/
[09:11] <gema> kernel + kernel_init
[09:12] <apw> pitti, and i think if we are to believe the numbers there may have beeen a small improvement as a result
[09:12] <gema> apw: I'd wait a bit longer for the trend to show, but if you look at when we started running them
[09:12] <gema> we seemed to be better back then
[09:12] <gema> in january
[09:13] <apw> gema, hard to say what is going on there as the same 'better' ones kerenl side are much worse overall
[09:14] <gema> yep, but that is because of the desktop regression, but if you look only at the kernel
[09:14] <gema> it was better in jan, then it regressed, I wonder if we updated the kernel between those two
[09:14] <apw> gema, probabally that is when we had broken ureadahead, so overall bootspeed was in the crapper
[09:14] <gema> apw: ah, ok
[09:15] <apw> gema, and then we fixed ureadahead, perhaps that is affecting our overall kernel init numbers
[09:15] <gema> uhmmm, well, anyway, it looks really good now
[09:16] <apw> kernel is a tricky one as it is actually "kernel + userspace until root is mounted and we chroot in"
[09:16] <apw> it would be very helpful if we could click on those columns to get the detail page for that run
[09:16] <gema> apw: it is in our todo
[09:17] <gema> apw: but since all the mobile stuff has piled up, it's going to take a while
[09:17] <apw> yep
[09:17] <gema> we may get it sorted for other mobile graphs and then use it here as well
[12:06] <samgabbay> hello peeps
[12:50] <asac> plars: how can i find out more about failure of https://jenkins.qa.ubuntu.com/job/raring-touch-grouper-smoke-default/44/
[12:51] <asac> ?
[12:51] <asac> not sure where i could find more logs
[12:53] <shadeslayer> jibel: did you have time to look at otto + kubuntu ? :)
[12:56] <jibel> shadeslayer, hey, not yet, I'm trying to make it run with Ubuntu on a tablet at the moment. But it's on my list, I'll keep you posted.
[12:56] <shadeslayer> oh, which tablet :D
[12:56] <shadeslayer> N10?
[12:56] <shadeslayer> erm, I meant, Nexus 10?
[12:58] <jibel> shadeslayer, nexus7
[12:58] <shadeslayer> ah
[13:09] <plars> asac: error: device not found
[13:09] <plars> asac: it's in the console log there
[13:09] <plars> asac: looks like adb failed, which happens every once in a while unfortunately
[13:10] <plars> asac: I'll have to get someone in the lab to investigate, could be the device itself died too
[13:17] <asac> plars: ok. more info about device is not avail?
[13:17] <asac> guess not
[13:17] <asac> ;)
[13:18] <asac> lab == lexington?
[13:18] <plars> asac: it's a nexus7, and the system it's connected to can't see it over usb
[13:18] <plars> asac: yes
[13:18] <asac> who is supporting us there?
[13:19] <asac> e.g. what is the support channel if i see such behaviour? any lab gent that ican poke and he checks?
[13:20] <plars> asac: already poked, just waiting on a reply
[14:31] <zyga> asac: welcome back!
[14:39] <asac> :)
[14:39] <asac> not sure what back means though :)
[14:39] <asac> its different place, different time, different look :)
[15:26] <samgabbay> poop
[17:37] <cking> doanac`, does the --runlist option to run_utah_phablet.py specify the path to where the tests are stored on the host or on the client phone?
[17:38] <doanac`> cking: i normally point to a bzr branch. however, if you don't do that it should be a path on client
[17:39] <cking> doanac` ta
[17:39] <doanac`> bzr is slow for test development though
[17:39] <cking> indeed, so I will hack some scripts up on the client and then shove them in bzr or git or something
[17:40] <cking> doanac`, i was just hoping the --runlist option was going to copy the files up from the driving host to the client :-)
[17:40] <doanac`> cking: plars asked for the same thing. so I should probably add support for that.
[17:41] <cking> doanac`, that is a ++beer request :-)
[17:41] <doanac`> so persuasive
[17:41] <plars> indeed, from both of us! :)
[17:41] <cking> double good :-)
[17:41] <plars> ++(++beer)
[17:43] <plars> cking: I have found that in some cases it's enough to be able to get to the device or vm after utah has provisioned, then run utah client from there and adjust my runlist to use the "dev" checkout method and point to the path on the device of the test
[17:43] <plars> do some in-place modifications to try things, and go from there
[17:43] <plars> but not always ideal
[17:45] <cking> especially if one accidentally re-provisions the device
[18:43] <cking> doanac`, i've got some simple tests now running on the phone with UTAH - thanks for all your help and for putting up with all my questions
[18:49] <doanac`> cking: thanks for the input. sorry things are still so rough around the edges
[18:50] <cking> doanac`,  no probs
[18:51] <cking> now I have my head around it it's less of a mystery and I can get crackin' on writing some tests for my personal use :-)
[20:33] <balloons> Noskcaj, howdy
[20:33] <Noskcaj> hey balloons
[20:35] <balloons> so did you see my comments on the merges?
[20:36] <Noskcaj> balloons, yep
[20:36] <Noskcaj> i forget what the changes on the second merge where, checking now
[20:37] <balloons> sure thing.. did it make sense?
[20:38] <balloons> it's ok to have 4 or 5 or more merge requests.. as you know it gets really hard if the merge is too big, and it can be complicated if there's a minor issue with one line, but the rest is good. Can't merge everything :-)
[20:39] <Noskcaj> ok. the second change in merge 2 was because i was trying to get it in line with the shotwell test (the example testcase).
[20:39] <Noskcaj>  4 or 5 or more merge requests.. as you know it gets really hard if the merge is too big, and it can be complicated if there's a minor issue with one line
[20:40] <Noskcaj> oops, ignor the second paragraph
[20:40] <Noskcaj> https://bazaar.launchpad.net/~ubuntu-testcase/ubuntu-manual-tests/trunk/view/head:/testcases/packages/1428_Shotwell%20Tests
[20:42] <Noskcaj> I could only make one merge because i didn't have access to the internet until i had finished
[20:47] <balloons> Noskcaj, ok so let's go through them one at a time and try and clean up everything so they can be merged
[20:47] <balloons> you have a few mins?
[20:48] <balloons> I think xchat can just go in
[20:48] <balloons> https://code.launchpad.net/~noskcaj/ubuntu-manual-tests/minor-xchat-fix/+merge/168368
[20:48] <Noskcaj> yeah
[20:48] <balloons> this one however I have some stuff I don't want
[20:48] <balloons> https://code.launchpad.net/~noskcaj/ubuntu-manual-tests/random-improvements/+merge/168354
[20:49] <balloons> why did you remove the <ul> stuff? for example - <li>Your system have at least the amount a space indicated</li>?
[20:49] <balloons> knome actually just made a nice fix to display that and bring it inline with proper convention ;-)
[20:49] <Noskcaj> i was  trying to get the testcases down to just <dl> <dt> <dd>
[20:50] <balloons> on the non-english changes, Non-English Installation Full Network Support, I like fact you expanded the testcases but I'm wondering if we can't just link to the proper testcase and hmm.. I'm undecided
[20:50] <Noskcaj> and i hadn't seen/heard about knome's fix
[20:50] <balloons> anyways, I would merge those as-is
[20:50] <balloons> I think the <ul> changes are the big thing to undo if possible
[20:50] <balloons> you need help undoing the changes?
[20:51] <Noskcaj> yep
[20:51] <balloons> you can revert the specific files with the changes in it and/or use a diff tool
[20:51] <balloons> have you ever used meld?
[20:51] <Noskcaj> no
[20:51] <balloons> go ahead and install it
[20:51] <balloons> sudo apt-get install meld
[20:51] <balloons> it's a gtk app
[20:52] <balloons> then you can use this command to visually see all the file differences: bzr diff --using meld
[20:54] <balloons> well, so here's what I would do when your ready
[20:54] <balloons> in a new folder
[20:54] <balloons> bzr pull lp:ubuntu-manual-tests
[20:54] <balloons> bzr merge lp:~noskcaj/ubuntu-manual-tests/random-improvements
[20:54] <balloons> bzr diff --using meld
[20:55] <balloons> That will show all the differences and let you easily edit/undo your changes as needed, one file at a time
[20:55] <balloons> once it's all done
[20:55] <balloons> bzr commit
[20:55] <Noskcaj> ok.
[20:55] <balloons> bzr push lp:~noskcaj/ubuntu-manual-tests/random-improvements-fixed
[20:56] <balloons> or you can overlay it on top if you wish
[20:56] <balloons> bzr push lp:~noskcaj/ubuntu-manual-tests/random-improvements
[20:56] <balloons> I hope that makes sense? ping with questions :-)
[20:57] <Noskcaj> i keep getting: bzr merge lp:~noskcaj/ubuntu-manual-tests/random-improvements
[20:57] <Noskcaj> bzr: ERROR: Not a branch: "/home/jackson/bzr/.bzr/branch/": location is a repository.
[21:03] <balloons> Noskcaj, ohh sorry
[21:03] <balloons> after you bzr pull, you need to cd into the directory you pulled
[21:03] <Noskcaj> nevermind, i used branch and it worked
[21:03] <balloons> so cd ubuntu-manual-tests
[21:03] <Noskcaj> so far : branch, cd, merge
[21:03] <balloons> you need to merge it into the source tree, else the diff won't work.. lol
[21:03] <balloons> sorry, I said pull
[21:04] <balloons> that's git terms mixing in
[21:04] <balloons> my bad
[21:04] <balloons> you got it :-)
[21:04] <Noskcaj> everything's working. i'm in meld
[21:06] <Noskcaj> is the <ul> the only change you want undone?
[21:12] <Noskcaj> balloons, for the CJK install, do i still put <ul> back in?
[21:12] <balloons> Noskcaj, if you would
[21:13] <Noskcaj> ok
[21:13] <balloons> Noskcaj, you figure out the app simply enough.. you can click to move changes back and forth and then save and edit if needbe :-)
[21:16] <Noskcaj> balloons, i think i'm done,pushing now
[21:16] <balloons> Noskcaj, ok
[21:16] <balloons> if you push to the same branch everything will update in the merge request
[21:19] <Noskcaj> balloons, done, i need to get food
[21:19] <balloons> Noskcaj, k, I'll have a look
[21:23] <balloons> Noskcaj, looking good so far ;-)
[21:24] <balloons> does this affect your https://code.launchpad.net/~noskcaj/ubuntu-manual-tests/minor-xchat-fix/+merge/168368 at all I wonder -- hopefully not, we'll see
[21:24] <Noskcaj> it shouldn't
[21:27] <Noskcaj> balloons, to clarify, is <dd> written as "this should happen", "this happens" or "does this happen"?
[21:27] <Noskcaj> that need proper definition because it changes in every testcase
[21:27] <Noskcaj> *needs
[21:29] <balloons> dd should be this should happen
[21:29] <balloons> perform an action, then expected result
[21:29] <balloons> so the <DD> contains the expected result
[21:29] <balloons> I realize some aren't so uniform on that front.. I saw you converting some of the questions to statement
[21:29] <balloons> that's the right way
[21:31] <balloons> Noskcaj, ohh I do have one more potential snafu
[21:32] <Noskcaj> yeah?
[21:32] <balloons> the slideshow might not be in the language of the person installing.
[21:32] <balloons> however I suppose it's a bug regardless eh :-)
[21:32] <balloons> there aren't translations for every language on the cd for slideshow I don't believe
[21:33] <Noskcaj> balloons, so only the network tests should required a localised slideshow?
[21:35] <balloons> I'm going to leave it in for now, but it's an open question
[21:35] <balloons> I'm not 100% sure of the behavoir
[21:35] <balloons> if it's not localized, it's a bug. it might be a bug they won't fix for space or something, but it's still a bug and I'm ok with it
[21:36] <balloons> if we hit it we can address it and update the test as needed
[21:38] <balloons> Noskcaj, do you know about the format check script? https://wiki.ubuntu.com/QATeam/ContributingTestcases/ManualStyleGuide/test_case_format_script
[21:40] <balloons> excellent all looks good
[21:40] <balloons> time to push the first one in :-)
[21:41] <Noskcaj> i only just saw the format script.
[21:42] <Noskcaj> i'll spend the day at school converting all the testcases to <dd> this should happen </dd>
[21:42] <balloons> well everything passed through it.. just one minor snafu found
[21:42] <balloons> a missing < from a  </dd>
[21:42] <Noskcaj> oops
[21:42] <balloons> lol, the script helps
[21:43] <balloons> that's amazing it was the only issue with all those changes
[21:43] <balloons> you did really well ;-)
[21:45] <Noskcaj> thanks
[21:46] <Noskcaj> balloons, is there a way we can make geany highlight the parts of the testcase?
[21:46] <balloons> I'm sure there is.. Try using the html syntac
[21:47] <balloons> let's see
[21:48] <balloons> ahh yep worked for me
[21:48] <balloons> Document->Set Filetype->Markup Lang->HTML
[21:48] <balloons> make it all nice and pretty :-)
[21:52] <balloons> k, you are all merged Noskcaj
[21:53]  * balloons is ready for more :-)
[21:53] <Noskcaj> balloons, there will be more when i'm back from school.
[21:55] <balloons> Noskcaj, enjoy! have a great day
[21:59] <Noskcaj> balloons, one other thing. should we just remove the gnome classic parts completely?
[22:03] <balloons> Noskcaj, I think so.. gnome classic really doesn't exist anymore.. I think we left them for 10.04
[22:11] <Noskcaj> balloons, for the part at the very bottom of each testcase, do we want one line or two?
[22:11] <balloons> I think we use two?
[22:11] <Noskcaj> ok, i'll fix that too
[22:11] <balloons> however knome also is working on not having to have that in every testcase
[22:12] <balloons> so I wouldn't worry about changing it
[22:12] <balloons> does that make sense? we'll probably gut them all
[22:12] <Noskcaj> ok. just <dd> should </dd> and fixing the hardware tests then
[22:12] <balloons> perfect mate
[22:14] <Noskcaj> :)
[22:20] <phillw> I'll be glad when the test cases settle down a bit. I'm aware I still have work to do on the server ones :)
[22:21] <balloons> ^^
[22:21] <Noskcaj> phillw, it's a big improvement over when i joined.
[22:21]  * Noskcaj goes off to school
[22:22] <balloons> lol.. I love his part message
[22:23] <phillw> balloons: that's Aussie humour for you, and possibly true at times :D
[22:23] <balloons> lol
[22:23] <balloons> indeed
[22:37] <phillw> balloons: how does http://pastebin.com/aDU4RVzY look?
[22:37] <balloons> phillw, cool.. you script that?
[22:38] <phillw> no, one of our PPC team, there was a bug in it which Jonathan has just corrected.
[22:39] <phillw> well, when I say bug.. It seems to work fine on PPC-Macs, but needs a flag setting for non PPC-Macs :)
[22:41] <phillw> not sure why it didn't find my battery, but that's not too important as to what hardware we're running :) Is that enough details for hardware registration?
[22:42] <balloons> phillw, it's certainly worth contributing to the dialog about it
[22:42] <balloons> I'm open to whatever everyone wants to adopt
[22:42] <balloons> I'd like to move to hexr, but until then.. I'm happy to do something.. and we've been waiting more than one cycle now, so it's best to do something
[22:44] <phillw> indeed, I was thinking of using the laptop version of scheduling up a machine, but that is a bit more involved
[22:45] <phillw> try this on your machine (ignore the errors), you should have the pastebin URL after it runs.....
[22:45] <phillw> hardinfo -ram devices.so | sed '/\*\*\*\*\*\*\*/,/\*\*\*\*\*\*\*/d' | pastebinit -b http://pastebin.com | clipit -c
[22:47] <phillw> It is specifically set up to have no personal information, the sed stuff is just to tidy it up
[22:56] <balloons> i needed all three binaries
[22:57] <balloons> http://pastebin.com/iCTaA4D3
[22:59] <phillw> balloons: ahh... yes.... sorry, my Bad! I'll ensure any wiki page is updated to download them 1st...
[22:59] <balloons> phillw, it told me
[22:59] <phillw> I've been more concetrating in getting the last bit to work.
[22:59] <phillw> Oh, indeed, it screams like a scalded pig :)
[23:00] <balloons> it's nice like that.. it's like "The program 'hardinfo' is currently not installed. You can install it by typing:"
[23:00] <balloons> pretty slick
[23:00] <phillw> that's part of apt, the command simply calls all three of them.
[23:01] <phillw> hardinfo is standard for lubuntu, but the other two did need adding in.
[23:02] <phillw> balloons: So, until hexr is up and running, do you think that should give the devs enough information to work out what we have as hardware?
[23:13] <balloons> phillw, I would think so
[23:13] <balloons> dinner time for me now mate
[23:13] <balloons> have a wonderful evening yourself
[23:31] <phillw> balloons: have a good dinner, I'll knock up a wiki page which you can peruse later (00:31 here, so I may well be in bed :) )