[04:47] <pitti> Good morning
[05:12] <DanChapman> Good Morning all :-)
[08:54] <slickymaster> good morning evrybody
[09:14] <xeranas__> good day
[09:17] <xeranas__> I notice that autopilot tests for some touch core apps need aditional dependecies (or additional setup) in order to run. For example music-app I get "ModuleImportFailure"  or something wrong with my enviroment :/
[13:25] <slickymaster> good afternoon everybody
[13:44] <SergioMeneses> slickymaster, morning here :D
[13:51] <slickymaster> SergioMeneses: :) over here it's past lunch time
[13:53] <SergioMeneses> slickymaster, jeje
[13:53] <SergioMeneses> time zone things
[13:54] <slickymaster> SergioMeneses: yeah, it's a big world :D
[13:56] <SergioMeneses> slickymaster, it is not as big as we think :S
[13:57] <slickymaster> SergioMeneses: yes, you're right. At least nowadays it isn't
[13:57] <slickymaster> SergioMeneses: it used to be for the generations of our fathers and grandfathers
[14:01] <knome> slickymaster, you're clearly talking about subjective opinions on how big or small something is. may i notice you that the world feels awfully big for many people even now; for example, the front door might seen really far away for a depressed person - so how far away would another continent seem to be?
[14:03] <slickymaster> knome: no argues there. I was referring to the general perception that nowadays people have of the world
[14:03] <knome> ;)=
[14:03] <SergioMeneses> jeje
[14:05] <slickymaster> knome: and once I have let me ask you something, in the manual tests, when we're writing terminal commands we open it with a <code> tag, right?
[14:05] <slickymaster> knome: onve I have your attention
[14:05] <knome> slickymaster, that's the preferred way to do it, yeah
[14:06] <slickymaster> knome: my question is, isn't there a closing </code> tag?
[14:06] <knome> yes, sure
[14:07] <knome> blahblah <code>terminal command</code> blahblah
[14:07] <slickymaster> knome: I assumed so, but wasn't sure of it. Thanks
[14:55] <elopio> balloons: an update. All my branches are on trunk and released on the PPA. However, before using them, it might be better to get tha package namespaces right.
[14:55] <elopio> I'll rename UbuntuUIToolkit to ubuntuuitoolkit.
[14:56] <balloons> elopio, ahh yes.. what's the ppa again?
[14:57] <elopio> balloons: https://launchpad.net/~ubuntu-sdk-team/+archive/ppa
[14:57] <balloons> elopio, I thought you were trying to say it was in your personal ppa somewhere :-p
[14:58] <qengho> Hi all. On the mailing list, in response to Phill, I (chad.miller@c.c.) asked for guidance and help automating some quality tests for chromium.  I don't think my message went through the moderation queue.
[14:58] <elopio> oh, no.
[14:59] <qengho> I have a simple autopktest smoke test (with Xvfb), and I run some unit tests at pkg build time.
[14:59] <asac> pitti: dont we have existing network-manager tests that we could try to land on phones before we have rild working?
[14:59] <asac> or is that not usable on phone?
[14:59] <asac> (answer after call)
[14:59] <qengho> I think I need more automated test for chromium-browser, and I would love some help or pointers to the state of the testing art.
[15:00] <balloons> qengho, nothing is in the queue that I see.. did you send to ubuntu-quality? anyways, what's up?
[15:01] <qengho> balloons:  Message-ID: <CAE1yU5wTm4R1001A8-vYeMiHL5Dy3-jiL-hwhhbSQTJvpBZ=RA@mail.gmail.com>
[15:03] <qengho> Here is a wishlist of things I know I would like to test about webapps.  http://bazaar.launchpad.net/~chromium-team/chromium-browser/saucy-working/view/head:/debian/tests/webapps
[15:03] <pitti> asac: we do have NM tests, yes
[15:03] <pitti> asac: we run them as part of autopkgtest now
[15:03] <pitti> asac: https://jenkins.qa.ubuntu.com/view/Saucy/view/AutoPkgTest/job/saucy-adt-network-manager/
[15:03] <pitti> asac: that's also using simulated wifi and eth devices (not with umockdev, though)
[15:04] <pitti> asac: it should in principle also work on a phone, we just don't run autopgktests on arm ATM
[15:04] <asac> pitti: we dont run autopkgtests on images unfortuntely
[15:04] <pitti> asac: but that's a totally different story than telephony/rild
[15:04] <asac> what does it take to get those into autopilot tests? or in a simple run-cmd-list
[15:04] <qengho> I can fire up a virtual X server, easy.  I am wondering what tools there are that I should consider for trying to test those.  I suppose it might need to inject X events to test things.
[15:05] <pitti> asac: apt-get source network-manager; sudo debian/tests/nm
[15:05] <asac> pitti: it is separate, yes, but we have NM on the phone and want to test it is how i see it
[15:05] <qengho> I remember some accessibility-exercising test tools, but not the name.  I don't know if they would work.
[15:05] <asac> pitti: that won't report results nicely to dashboard. if we could get single commands for each test that that suite runs it would be easier
[15:06] <asac> (or i am wrong :))
[15:06] <asac> mayube check with real folks like doanac what is easiest to get those run on images as well
[15:06] <pitti> asac: hm, we don't have a python unittest parser?
[15:06] <asac> no clue. assume it would be another test suite integration abstraction that needs to be invented
[15:06] <asac> so far we have support for autopilot
[15:06] <pitti> asac: it would seem to me that grabbing individual tests from a python unittest program is a rather common situation
[15:07] <asac> and suites that have alist of commands to run (each exit 0 if succeed to count as 1 in dashboard)
[15:07] <pitti> asac: autopilot uses the python unittest framework as well; it reformats its output though as it has its own runner
[15:08] <asac> we only support simple exit code based command lists ... otherwise test suites need to produce compatible output on their own
[15:08] <asac> but yeah. maybe a place to invest if thats common
[15:08] <asac> and will stay common (like python for testing not going away)
[15:11] <balloons> qengho, did you get my reply to you at all? the primary method for testing the app at a UI level would be autopilot but it didn't seem to work out of the box. Now, we could file a bug and see if pitti might now why or might be able to make it work.
[15:13] <balloons> assuming autopilot is off the table, what does upstream do for there UI testing?
[15:17] <jibel> qengho, the moderation queue for ubuntu-quality is empty when did you send it?
[15:17] <jibel> qengho, was it your message https://lists.ubuntu.com/archives/ubuntu-quality/2013-July/004090.html
[15:17] <qengho> balloons: I did get your message, thank you.
[15:18] <qengho> jibel: Yes, that's it.  Huh.  The moderation message said I'd get a confirmation when it was accepted or rejected.  Ah well.
[15:19] <qengho> balloons: So, that helps.  "autopilot" is The Way to test these days.  Awesome. I'll focus on that.
[15:25] <balloons> qengho, yes, but chromium doesn't let you introspect it out of the box
[15:26] <balloons> Meaning, chromium eitheir isn't listing anything on dbus or otherwise is doing something "different" than other gtk apps which prevent autopilot from being able to get at what's going on. SO, we'll need some help from pitti to see if we can solve that problem or not
[15:26] <balloons> If we can't, we'll have to come up with a plan b
[15:27] <qengho> balloons: Yeah, I don't think it's a proper GTK app.  It's gtk2, at that.
[15:27] <pitti> balloons: I have some feeling that it's not actually using the system GTK library
[15:27] <pitti> balloons: oh, and gtk2 too, there is no ap plugin for that; but we might be able to create one rather easily
[15:28] <balloons> pitti, are firefox and thunderbird in a similar boat?
[15:28] <pitti> balloons: I guess, they also still haven't changed, although I'm hearing promises like "it will land RSN" very often :)
[15:28] <pitti> the firefox gtk3 branch has existed for like two years now
[15:29] <balloons> pitti, yea, not sure what the true holdup is.. ok, so a gtk2 app plugin eh?
[15:29] <pitti> balloons: yes, unless these programs bundle GTK
[15:29] <pitti> an ldd on the binary should be enough to check
[15:29] <pitti> if it links against /usr/lib/.../libgtk2, then we can provide an ap plugin
[15:29] <qengho> pitti: ldd grep gtk : libgtk-x11 only
[15:30] <pitti> qengho: that's it
[15:30] <pitti> nice
[15:30] <balloons> pitti, k let's have a lok
[15:30] <jibel> qengho, isn't selenium more appropriate to test webapps?
[15:30] <pitti> balloons: qengho just checked
[15:31] <qengho> jibel: that's why I'm here.  I have no idea what selenium is.
[15:32] <jibel> qengho, I think that's their website http://docs.seleniumhq.org/ and there is a driver for chromium
[15:32] <balloons> jibel, looking at qengho's list I can see selenium working out for some of his needs, but other pieces are intended to check the application state.. It was my first backup option :-p
[15:33] <pitti> hm, I thought selenium was for testing webapps
[15:33] <pitti> not for testing the browser itself?
[15:33] <balloons> pitti, indeed
[15:35] <jibel> true, I read chromium / tests / webapps in the initial question which matched with selenium :)
[15:36] <jibel> if you need to interact with the webapps and check the state of the desktop, then that would be a mix of selenium + autopilot
[15:36] <qengho> jibel: Right, I don't wish to test any web-app, just that the patches to chromium that enable webapps do what we expect.
[15:36] <balloons> ok well so it looks like a gtk2 app lib for autopilot would allow this to work, n'est pas?
[15:48] <pitti> balloons: right
[15:56] <qengho> pitti: I don't want to push something onto your to-do list if I can do it.  I'll give it a try, if you don't care.
[15:56] <pitti> qengho: absolutely, good luck! please let me know if you have some questions
[15:56] <pitti> qengho: worth filing a bug against ap-gtk anyway though, for tracking
[15:58] <balloons> pitti, qengho ty.. If I can help by filing a bug, I'll do it
[15:59] <qengho> done, balloons.  lp#1204163
[16:07] <elfy> balloons: got a comment on a merge proposal for a manual test - "For terminal comands, type <code> at the start." I assume that you'd do </code> at the end of it ?
[16:08] <elfy> and hi :)
[16:08] <balloons> elfy, hello
[16:09] <balloons> elfy, yes, that's correct with the closing code tag
[16:09] <elfy> cool - just checking - amazing how people forget that their only born knowing how to cry and suckle :p
[16:10]  * balloons stops himself from making a bad joke
[16:11] <elfy> probably one I would have made before I stopped myself from making bad jokes :p
[16:18] <balloons> elfy, they are the only jokes I know how to make!
[16:19] <elfy> :)
[16:24] <balloons> biab
[16:24]  * balloons shouts hello to dkessel as he jets
[16:25] <dkessel> balloons, hello :)
[16:31] <rbasak> psivaa: the job related to bug 1203048 looks good now. Is that enough to consider it Fix Released?
[16:31] <psivaa> rbasak: I am fine with that.
[16:32] <rbasak> psivaa: great. Thanks for flagging that!
[16:32] <psivaa> rbasak: yw
[17:09] <DanChapman> jibel, hey :-) how often is ubiquity set to run on jenkins? is it daily?
[17:10] <DanChapman> balloons, elfy, hey o/
[17:10] <elfy> hi DanChapman
[17:35] <xeranas> evening
[17:38] <xeranas> Did music-app can be launched? To me it says module "org.nemomobile.folderlistmodel" is not installed did I missing some package?.
[17:48] <jibel> DanChapman, hi, when a new image is published
[17:48] <jibel> or manually
[18:55] <balloons> xeranas, is the music app still not running for you/
[18:55] <balloons> xeranas, the easiest way to make sure you have the dependencies is to install the version published in the core apps ppa
[18:56] <xeranas> balloons: ok I will tried to install it
[19:22] <qengho> pitti: I didn't see an easy way to have this coexist in the same location. Do you want another bzr branch and source package, or another directory in the same branch?
[19:22] <qengho> Sorry.  This = gtk2 support.
[19:41] <dkessel> wow, so late already... and no good deed done for ubuntu today... :/
[19:43] <balloons> dkessel, I'm sorry mat
[19:44] <balloons> dkessel, how's things this week?
[19:46] <dkessel> balloons, weather's hot in germany...
[19:46] <balloons> dkessel, we've been underwater here, lol.. lots of rain. rain every day.. it's raining now.. lol
[19:49] <dkessel> 30°C here... the poor cat lies on the (relatively) cold parquet floor all day... maybe i should go and lie next to her...
[19:50] <balloons> dkessel, hehe.. my dog does similar things.. we have almost no carpeting in the house. tile or wood, so the floors stay cooler
[19:55] <dkessel> oh btw i tried to build jenkins locally... multiple times... and failed with different results. with yesterday's git version one junit test failed... with todays, one test gets stuck forever....
[19:59] <balloons> dkessel, pulling from the stable tree for jenkins or ?
[20:00] <dkessel> balloons, from git://github.com/jenkinsci/jenkins.git . i don't know what branch/tree that is even...
[20:03] <balloons> dkessel, it looks like maybe they have stable branches
[20:04] <dkessel> i'm unsure about if the whole thing makes sense. what exactly happens when a jenkins package for ubuntu gets built? does that not also execute the main build script, which also causes the junit tests to be run? in that case... enabling autopkgtests would be pointless
[20:05]  * dkessel goes to find source of smell...
[20:05] <balloons> dkessel, probably not.. hence the autopkg test :-) however, I'll defer to jibel a bit here, but I would probably start with the ubuntu source, not the upstream source
[20:06] <balloons> as that's kind of the point eh? and it should properly build to boot !
[20:15] <dkessel> balloons, right. i'll give it another try with the ubuntu source... some other day
[20:16]  * dkessel opens a nice cold beer
[20:16] <balloons> dkessel, you understand how to get the source right?
[20:16] <balloons> just want to make sure your set :-)
[20:17] <dkessel> lp:ubuntu/jenkins - i guess
[20:20] <dkessel> balloons ^
[20:38] <balloons> dkessel, sorry, umm sure.. but I was thinking just grabbing the source package
[20:39] <dkessel> hm... too easy :)
[20:39] <balloons> http://archive.ubuntu.com/ubuntu/pool/universe/j/jenkins/jenkins_1.480.3+dfsg.orig.tar.gz
[20:39] <balloons> or whatever else.. again I'll defer to jibel on this
[20:39] <dkessel> balloons, np. anyway... not tonight. good night :)
[20:39] <balloons> indeed
[20:40] <balloons> good night
[21:24] <slickymaster> good night, all
[22:16] <elopio> fginther: ping. Can you please enable the pep8 check on ubuntu-ui-toolkit?
[22:16] <fginther> elopio, yes
[22:18] <elopio> thanks man.
[22:37] <fginther> elopio, it's been added
[22:37] <elopio> nice