[05:12] <pitti> xnox: wow -- what is that, a VVVM? :-)
[05:12] <pitti> Good morning
[05:45] <DanChapman> GOod Morning all :-)
[06:02] <pitti> hey DanChapman
[06:27] <DanChapman> pitti, o/
[06:28] <jibel> good morning
[08:49] <slickymaster> good morning all
[08:49] <DanChapman> slickymaster, morning
[08:49] <slickymaster> DanChapman, :)
[08:51] <Noskcaj> evening slickymaster, DanChapman
[08:58] <slickymaster> morning over here, Noskcaj ;)
[08:59] <slickymaster> Noskcaj, yesterday I've pushed this http://bazaar.launchpad.net/~slickymaster/ubuntu-manual-tests/1574_xfce4settings/view/head:/testcases/packages/Xfce/1574_xfce4settings%20tests
[09:00] <slickymaster> Noskcaj, but what elfy got to review was this https://code.launchpad.net/~slickymaster/ubuntu-manual-tests/1574_xfce4settings/+merge/175697
[09:00] <slickymaster> do you have any idea of out is going on, Noskcaj?
[09:02] <slickymaster> of out is going on -> of what is going on
[09:03] <Noskcaj> slickymaster, The test was already made, and it appears you weren't updating it, you were making a new one
[09:04] <slickymaster> Noskcaj, well, I now it was already merged, but I was under the impression that I could still work on it and that by the time I finished it I simply had to push it again
[09:04] <slickymaster> I know
[09:05] <Noskcaj> slickymaster, you can, just make sure you are using the current version of the trunk and you work in the same file
[09:06] <slickymaster> Noskcaj, ok, got it, but now is there any way to circumvent it in order to get the right file merged?
[09:08] <Noskcaj> branch the current trunk, then edit the current test file to include the changes, the commit and push
[09:10] <slickymaster> Noskcaj, as always you're really helpful. I'll do it by lunch time, at home. Presently I'm "working for the man" and behind a proxy and thus unable to bzr
[09:11] <Noskcaj> ok. as always, it great how much work you're doing for xubuntu and ubuntu.
[09:11] <Noskcaj> *it's
[09:12] <slickymaster> Noskcaj, thanks :)
[09:12] <Noskcaj> I'll try and merge tomorrow, if i have time
[09:12] <slickymaster> ok
[09:47] <DanChapman> Noskcaj10, I see you made a start on an autopilot test for transmission a while back, how you been getting on with it?
[09:48] <Noskcaj10> No, i could not understand autopilot. i really need to delete that
[09:51] <DanChapman> lol ok then
[09:51] <DanChapman> :-)
[09:52] <DanChapman> jibel i see there is finally no fails for firefox now :-)
[10:05] <jibel> DanChapman, Excellent \o/
[10:44] <xnox> pitti: jibel: well, the autopackage test runs, but seems to hang at the end. I had to bump the RAM and DISKSIZE parameters for $ ./bin/run-adt-test -S lp:~xnox/ubiquity/autopilot ubiquity     , to start up successfully.
[10:45] <xnox> it's a bit hard to troubleshoot, as there is no direct forwards for vnc and/or ssh into the inner qemu.
[10:46] <xnox> DanChapman: the ubiquity test at the end, seems to loop around checking for warning_dialog  or error/critical _dialog. Is that towards the end of the test? and it doesn't seem to stop, does it mean an error was encountered?
[10:56] <DanChapman> xnox, the test should terminate if one of those dialogs appears. The loop is running on the progress bar while waiting for the 'Installation complete' dialog appears and while in that loop it checks that those dialogs have not popped up by asserting that the visible property is not 1 if it is 1 then test 'should' fail.
[10:57] <xnox> DanChapman: ok, thanks for info. I wonder if the test is setup to display them, or i didn't wait long enough. (it was running for 30minutes or so)
[10:57] <xnox> (test as in my testbed environmet)
[11:05] <DanChapman> xnox, hmmm i wonder if its taking longer through the install before it gets to the progress bar. As the progress bar runs twice 1st for 'copying files' then again for the install. But if it takes a while to get to the progress bar. It might miss the first one. and loop on the second thinking its the first. I'll add a patch to check after the first loop that its going to run again or has install completed
[11:08] <DanChapman> xnox, i ran it on the smallest vm i could i think it had 384MB ram and 1 core anything smaller and it wouldn't run at all and it passed ok. anyway i'll sort that now see if it helps
[11:11] <xnox> DanChapman: not sure if ram/cpu is at stake here, fast IO will result in "installation" seeing the second progress bar straight away.
[11:14] <DanChapman> xnox, are you able to get the output from the test? it should show which loop it was on
[11:16] <xnox> DanChapman: right. i'll get that to you, next time, wiped clean.
[11:16] <xnox> =(
[12:20] <jibel> DanChapman, balloons xnox https://jenkins.qa.ubuntu.com/job/autopilot_ubiquity-saucy/
[12:21] <jibel> with video recordings please :)
[12:21] <jibel> https://jenkins.qa.ubuntu.com/job/autopilot_ubiquity-saucy/ARCH=i386,TESTNAME=ubiquity_lvm_encrypt,label=rabisu/lastSuccessfulBuild/artifact/results/var/local/autopilot/videos/ubiquity_lvm_encrypt.tests.test_lvm_encrypt_install.LvmEncryptInstallTests.test_lvm_encrypt_install.ogv
[12:24] <jibel> some results are odd, it's like the test aborts suddenly
[12:39] <DanChapman> jibel, you got it going. :-) Its strange how its not picking up that the button.sensitive goes to 0 when clicked. I adjust it slightly and see if that helps
[12:40] <jibel> DanChapman, ubiquity_lvm_encrypt failed with a timeout and the VM was too small to create the archive with the videos
[12:40] <jibel> I reduced the timeout and increased the disk size
[12:41] <jibel> DanChapman, for the moment the job is started manually, but I'll update it later to start when a new image is available
[12:44] <DanChapman> jibel jus gotta get my boy from school then will dig into it
[13:34] <DanChapman> jibel looking at the results for all the tests it looks like they timedout on the same thing for all the tests just in different places. Will sort a fix for it now
[13:35] <jibel> DanChapman, the latest version of the code of the runner is in my junk folder https://code.launchpad.net/~jibel/+junk/ubiquity-autopilot-runner
[13:36] <jibel> DanChapman, there is no doc of course :) all you need is an iso then run with ./run-ubiquity-test -t TESTNAME ./saucy-desktop-amd64.iso
[13:36] <jibel> DanChapman, if you want to see what's happening in the VM remove the option "vnc" from qemu command line
[13:37] <DanChapman> jibel, cool cheers mate.
[14:39] <DanChapman> jibel i'm getting this http://paste.ubuntu.com/5890986/ when starting the runner
[14:40] <jibel> DanChapman, could you rerun with bash -x ?
[14:40] <jibel> and paste the output here
[14:41] <jibel> not here, in a pastebin :)
[14:41] <DanChapman> yep 2 secs
[14:42] <DanChapman> jibel, http://paste.ubuntu.com/5890995/
[14:49] <jibel> DanChapman, unless port 43210 is already used I don't see what's wrong with the command. Is there a previous instance of qemu already running on and using this port?
[14:50] <jibel> it could be that clean up didn't kill a previous run
[14:56] <DanChapman> jibel how do i get a list of running instances? i can't find it in the man
[15:00] <xeranas_> good evening
[15:00] <jibel> DanChapman, ps aux|grep qemu
[15:03] <jibel> DanChapman, ps aux|grep qemu
[15:11] <WebbyIT> dpm: about this MR, I asked to mihir to do font bigger, because in design is bigger
[15:11] <WebbyIT> https://code.launchpad.net/~mihirsoni-123/ubuntu-calculator-app/EditIconMainLabel/+merge/175662
[15:11] <WebbyIT> sorry, wrong chan :-/
[15:30] <elopio> balloons: the status of the emulators is that I've finished bringing back the old branches with all tests passing.
[15:30] <elopio> https://code.launchpad.net/~elopio/ubuntu-ui-toolkit
[15:30] <elopio> I've just asked jppiiroinen to review them.
[15:30] <balloons> elopio, wa-hoo!
[15:30] <SergioMeneses> elopio, awesome
[15:30]  * SergioMeneses hugs balloons and elopio 
[15:33] <DanChapman> jibel, hey i'm getting /var/local/autopilot//autopilot.log: timeout: invalid time interval ‘./autopilot’ and then it starts cleaning up ive tried for all tests and its the same
[15:34] <DanChapman> balloons, hey o/
[15:35] <balloons> DanChapman, hey hey
[15:35] <jibel> DanChapman, I forgot to commit the fix
[15:35] <jibel> -        timeout -s 9 -k ./autopilot run $testname $AP_OPTS -o $AP_RESULTS/${testname}.xml
[15:35] <jibel> +        timeout -s 9 -k 30 $TIMEOUT ./autopilot run $testname $AP_OPTS -o $AP_RESULTS/${testname}.xml
[15:36] <jibel> DanChapman, you can pull r29
[15:36] <DanChapman> jibel, :-D sweet
[15:37] <jibel> a duration for a timeout is a nice feature :)
[15:46] <elopio> balloons: do you know who can help me to write a scope in python?
[15:47] <balloons> elopio, write  a scope in python? for unity?
[15:47] <elopio> balloons: yes. Well, for some unity tests. With no real functionality, some hardcoded values.
[15:48] <balloons> elopio, well, afaik they've moved away from python scopes. That said, yea, I could probably point you towards someone
[15:49] <elopio> balloons: yes, I think it wouldn't be so clear if I write it in C, because the autopilot test code is in python.
[15:49] <elopio> I don't care a lot about speed, just readability.
[15:49] <balloons> elopio, gotcha gotcha.. actually, let's just ask mhall119 , he's probably more up to date than me
[15:50] <balloons> mhall119, who's the best point of contact for scope writing today? specifically python scopes however :-)
[15:51] <DanChapman> jibel this is awesome. Wish i had this when i started working on the test. :-) anyway the default ubiquity test just passed no probs
[15:53] <mhall119> balloons: mhr3 or davidcalle
[15:53] <mhall119> but python scopes are out, C scopes are in
[15:54] <balloons> mhall119, indeed, we had that conversation.. ty mhall119 !
[15:54] <mhall119> np
[15:54] <balloons> elopio, ^^
[15:54] <elopio> got it. Thanks mhall119.
[16:14] <DanChapman> jibel, sorry to bother you again. Can you check this out http://paste.ubuntu.com/5891271/ i spoke to prematurely before it failed right at the end
[17:04] <DanChapman> Does anyone know what ubuntu kernel: [  445.307692] serial8250: too much work for irq3 means?
[17:06] <jibel> DanChapman, that's because autopilot outputs too much data too /dev/ttyS0
[17:06] <jibel> DanChapman, it's harmless
[17:07] <jibel> about http://paste.ubuntu.com/5891271/, looks like the FS got corrupted
[17:07] <jibel> maybe it didn't like eatmydata
[17:07] <jibel> it avoids hammering the disk drive too hard
[18:06] <TheLordOfTime> y'all don't mind if I comment on the wiki formatting email on the ubuntu-quality mailing list do you?  Even though I'm not on the QA team.  :)
[18:14] <balloons> TheLordOfTime, ofc not :-p
[18:14] <TheLordOfTime> balloons:  good, because i gave a suggestion just now :)
[18:14]  * TheLordOfTime signed as Ubuntu Member and Ubuntu Bug Triager so people know he's not a tester :)
[18:20] <DanChapman> jibel, does the jenkins test pull the tests from ubiquity trunk or from lp:~dpniel/ubiquity/autopilot?? i see on this runner that its my branch but wasn't sure if you set it the same for jen
[18:51] <slickymaster> got go guys, cy
[20:18] <Noskcaj> balloons, When are we going to be able to run autopilot on ubiquity for ourselves? And does it work with the flavours?
[20:19] <balloons> Noskcaj, you can run it yourself if you wish, but there isn't a reason to
[20:19] <Noskcaj> oh?
[20:19] <balloons> and yes, you could modify it to work with flavors
[20:20] <balloons> Noskcaj, well, it's running now on jenkins, so it will be run for each iso
[20:20] <Noskcaj> I saw that from the twitter link.
[20:20] <balloons> if your installing on your physical box, setting up the test isn't worth the time, well.. imho.. Are you wanting to basically plug in a usb drive and have it run through all the iso tests on your phsyical device?
[20:21] <Noskcaj> In a VM. I was wanting to see how hard it would be to get all the flavours working
[20:22] <balloons> Noskcaj, if you just want to try it in a VM go for it
[20:23] <balloons> are you confused as to how to do it?
[20:23] <balloons> boot up a live iso into a vm
[20:23] <balloons> install autopilot
[20:23] <balloons> grab dan's branch and kick off the test
[20:23] <Noskcaj> yes, so continue explaining
[20:24] <Noskcaj> Sounds simple enough.
[20:25] <balloons> Noskcaj, that's pretty much it.. here, let me find the detailed version
[20:26] <balloons> http://www.ubuntuhackers.com/?p=48
[20:27] <Noskcaj> thanks
[20:28] <knome> hallo balloons
[20:28] <balloons> knome, hello
[20:29] <balloons> I saw your email to stephane, good stuff :-)
[20:29] <knome> good good
[20:31] <xnox> Noskcaj: DanChapman sayed it worked fine with other gtk-fronented based flavours, i think he did test xubuntu for example.
[20:31] <Noskcaj> cool
[20:33] <xnox> jibel: i was merging your runner into the ubiquity codebase, and tests as well. I was thinking to package it as a deb, such that one just need to install ubiquity-autopilot-gtk to have "everything": the tests and the runner. Or do you just need the runner in lp:ubiquity and just the "inner" vm autpilots tests & helper scripts in a package?
[20:33]  * Noskcaj wonders if testdrive could somehow automate setting up autopilot
[20:34] <xnox> jibel: i also had to tweak your runner a little bit, changes committed in lp:~xnox/ubiquity/autopilot in autopilot subdir, to e.g. properly enable universe component and update ubiquity from -proposed before running the test.
[20:35] <xnox> Noskcaj: no, it won't. but you can use anything. jibel's script simply launches qemu with the cd image, but additionally setups vnc and ssh forwarding and serial consoles to collect the VM logs from boot to shutdown (console/kernel messages, syslog and autopilot results)
[20:35] <Noskcaj> ok
[20:36] <jibel> xnox, ah super! a separate package is fine I think.  Did you change the branch name in custom-installation/iso-override/usr/local/bin/run-autopilot.sh because it used Daniel's personal branch
[20:36] <jibel> ?
[20:38] <jibel> this code is also highly experimental, I wrote it during the time it takes to flash phones :)
[20:40] <balloons> jibel, :-p
[20:41] <xnox> jibel: not yet, but since i used "$ bzr join" to include full history of your branch, I can actually pull your updates in ;-) with bzr pull
[20:48] <phillw> balloons: you about?
[20:49] <balloons> si
[20:50] <phillw> balloons: 2013-06-14  Testing/QATracker 20:26 nskaggs marked as deleted by you (I've just pulled up the audit log)
[20:50] <balloons> phillw, where did that page go? I'm super confused
[20:51] <phillw> it was marked as deleted... it didn't "go" anywhere... you requested its deleteion
[20:51] <balloons> phillw, lol, ok.. well, I just was at that page.. clearly it went somewhere
[20:52] <phillw> balloons: scroll down https://wiki.ubuntu.com/RecentChanges?max_days=90 to 2013-06-14 It is there on the log.
[20:52] <balloons> well.. can we get it back?
[20:52] <phillw> the icon means it was deleted.
[20:53] <phillw> afaik, they do not hold deleted pages... they go 'poof' into star dust.
[20:55]  * balloons mind blowm
[20:56] <balloons> well, think hard.. any copies anywhere?
[20:57] <Noskcaj> maybe in one of the classroom sessions?
[20:58] <balloons> well google still has it
[20:58] <balloons> http://webcache.googleusercontent.com/search?q=cache:wiki.ubuntu.com/Testing/QATracker
[20:58] <balloons> but the images are all gone
[20:59] <phillw> I've gobe through the entire logs of 90 days, that deletion entry is all that is there :(
[20:59] <phillw> s/gobe/gone/7
[21:01] <balloons> I made a video a couple weeks ago and visited that page.. it just doesn't make sense
[21:03] <phillw> balloons: I renamed my master page last night and it went 'poof'.... motto of the story is not use rename. I will file a bug early next week if I can get it to recreate. Fortunanately I had made a mistake earlier and there was a pretty decent recent copy on another page.
[21:04] <phillw> balloons, I can recreate the page to a large degree from that cache image if you want.
[21:05] <balloons> that would be most helpful
[21:05] <phillw> But, most of it is already in the new area.
[21:05] <balloons> I'm just surprised and shocked a page can dissappear like that
[21:06] <balloons> phillw that page had the info on the tracker and how to use it with pics..
[21:07] <phillw> the pics cannot be retrieved, I know that from past experience of a saddo deleting attached images.
[21:08] <phillw> does the link to the video still work, as that is not in the new area.
[21:08] <balloons> yes
[22:37] <slickymaster> good night all
[22:37] <knome> night
[22:38] <slickymaster> knome, hi, you got a minute?
[22:38] <knome> sure
[22:39] <slickymaster> tk, thing is I'm trying to push a testcase to my branch but i get this error: bzr: ERROR: These branches have diverged.
[22:39] <slickymaster> knome, any thoughts on how to solve it?
[22:39] <knome> slickymaster, have you bzr pulled before trying to push?
[22:40] <slickymaster> knome, no I just bzr branch lp:ubuntu-manual-tests
[22:40] <slickymaster> then I bzr commit
[22:40] <knome> slickymaster, did you do that recently or some time ago already?
[22:41] <slickymaster> 5-10 minutes ago
[22:41] <knome> ok, then it's a weird error message
[22:41] <knome> but it might be correct; before pushing, try pulling
[22:42] <slickymaster> knome, do you think I should wait until tomorrow and ask balloons or Noskcaj?
[22:42] <knome> that's a bzr issue, not testcase-repository
[22:42] <slickymaster> knome, can you type the pull command
[22:42] <knome> slickymaster, bzr pull
[22:42] <slickymaster> knome, just that, not my branch after pull?
[22:43] <knome> in your branch, after your commit
[22:43] <knome> and no, not your branch
[22:43] <knome> because you want to pull from the main branch
[22:43] <slickymaster> ok, Thanks. I'm going to try it
[22:47] <slickymaster> knome, I get Using saved parent location: bzr+ssh://bazaar.launchpad.net/+branch/ubuntu-manual-tests/
[22:47] <slickymaster> No revisions or tags to pull.
[22:47] <slickymaster> is this expected?
[22:47] <knome> yes and no
[22:47] <knome> what does bzr status say?
[22:47] <slickymaster> knome, nothing
[22:48] <knome> and bzr push still says diverged branches?
[22:48] <knome> are you *sure* you're pushing to the correct location?
[22:48] <slickymaster> knomw,
[22:48] <slickymaster> knome, haven't tried it
[22:48] <slickymaster> doing it
[22:49] <slickymaster> knome, still the same: bzr: ERROR: These branches have diverged.  See "bzr help diverged-branches" for more information.
[22:50] <knome> the problem you're having is that bzr thinks that you have something that's not coming from the branch you are pushing to
[22:50] <slickymaster> knome, damn bzr. Any advises?
[22:51] <knome> slickymaster, 1) make sure the push location is correct (specify if needed)  2) read bzr help diverged-branches if it offers you any good ideas
[22:52] <slickymaster> ok, I want steal your time, for now
[22:52] <slickymaster> knome, thanks
[22:52] <knome> np
[22:52] <knome> good luck
[22:52] <slickymaster> :)