[00:21] <phillw> hi kot
[00:21] <phillw> hi kotux
[00:25] <kotux> hey phillw, what's the current plan for lubuntu manual?
[00:27] <phillw> hi kotux we seem to have decided upon the version of LaTex to use, Jonathan is going to start populating the bzr branch
[00:28] <kotux> Cool. Where can I find information to start helping?
[00:28] <phillw> kotux: I'm just waiting on Jonathan to publish the install script.
[00:30] <kotux> oh ok
[00:33] <phillw> kotux: JasonO Jonathan is not on-line at the moment, I'll email him.
[00:34] <JasonO> Alright
[00:36] <kotux> phillw, has there been any activity around quickshot lately?
[00:38] <phillw> kotux: Thomas is looking into it. I have a python guy possibly available to assist, but have not been asked to get assistance.
[02:08] <samgabbay> hi i cant hear anything on my username but on others i can
[02:08] <samgabbay> oops
[05:14] <pitti> Good morning
[06:51] <jibel> good morning
[08:57] <jibel> pitti, did you look at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711209 in autopkgtest?
[08:58] <pitti> jibel: no, not yet; but I probably should, it seems my workaround in umockdev only works in run-adt-test, but not in Jenkins for some reason
[08:58] <jibel> pitti, okay, I'll see if I can fix it.
[08:59] <pitti> umockdev's debian/tests/upstream currently has
[08:59] <pitti> # work around broken "build-needed" behaviour (Debian #711209)
[08:59] <pitti> cd $ADTTMP/../../ubtree0-build/real-tree
[08:59] <pitti> that fails in jenkins
[09:00] <pitti> but I was hoping for a clarification what this flag should really mean
[09:00] <pitti> jibel: it seems it conflates two distinct things: building the *tests* for running against the installed system, or building the package and installing the *built debs* to run the tests against
[09:15] <Noskcaj> balloons, ping
[09:47] <DanChapman> Good morning :-)
[12:01] <shadeslayer> jibel: did you have a chance to look at the logs I left you on IRC?
[12:02] <shadeslayer> regarding otto
[12:03] <jibel> shadeslayer, hey, nope, sorry I didn't see you left logs on IRC. What are they ?
 hmm ... when trying out otto + kubuntu I get : lxc container failed to recieve answer for command
 also : lxc container failed to send command
[12:04] <shadeslayer> it does mount the ISO from what I could tell
[12:04] <shadeslayer> and also made the lxc container
[12:04] <shadeslayer> that was on raring btw
[12:05] <jibel> shadeslayer, ah, that's a generic error and lxc logs nothing when using the API (bug 1181136) . lxc-start -n <container> should be more verbose.
[12:05] <shadeslayer> okay, lemme try
[12:05] <jibel> basically this message means that the container failed  to start :)
[12:06] <shadeslayer> I can see that :P
[12:06] <shadeslayer> I just couldn't figure out why because there was nothing in the log files
[12:07] <shadeslayer> jibel: is there a way to make it not kill my current X session?
[12:07] <shadeslayer> because whenever I ran sudo bin/otto start saucy-otto it killed my host lightdm and X
[12:09] <jibel> shadeslayer, not in the current state because it uses VT7, the same then lightdm. To make it not kill the current session, we'd need to add vt8 and make lightdm start on this VT inside the container. Patches welcome :)
[12:09] <shadeslayer> okay, will have a go at that
[12:11] <shadeslayer> jibel: http://paste.kde.org/772274/
[12:12] <jibel> pitti, did you already run umockdev testsuite run once successfully with autopkgtest and your workaournd?
[12:13] <jibel> shadeslayer, chroot: failed to run command ‘useradd’: No such file or directory
[12:14] <jibel> there is no useradd command on the livecd ?
[12:15] <shadeslayer> lemme check the manifest
[12:15] <shadeslayer> manifest says : passwd	1:4.1.5.1-1ubuntu4
[12:15] <shadeslayer> so it should be there
[12:15] <jibel> that's weird, from the trace the squashfs is not mounted
[12:16] <jibel> sounds like a bug
[12:16] <pitti> jibel: yes, as I said it works fine locally; I tried run-adt-test -skPS file://`pwd` umockdev
[12:17]  * pitti tries "run-adt-test -s umockdev", it's published now
[12:17] <shadeslayer> jibel: nvm, apparmor issue, I forgot to run the apparmor commands there
[12:18] <shadeslayer> + chroot /var/lib/lxc/saucy-otto/rootfs useradd --create-home -s /bin/bash ubuntu
[12:18] <shadeslayer> useradd: user 'ubuntu' already exists
[12:18] <shadeslayer> jibel: new log http://paste.kde.org/772286/
[12:19] <shadeslayer> lines 81 to 83
[12:23] <jibel> shadeslayer, for the error lxc-start: Error setting memory.memsw.limit_in_bytes to 2560M you'll need to enable swap resource control or remove this config paramter from lxc.defaults/config
[12:23] <jibel> shadeslayer, swap resource control will guard you against killing your host if something goes wrong with the test
[12:24] <shadeslayer> I have enough memory :P
[12:24] <jibel> to enable it set swapaccount=1 on the kernel boot command line (change it permanently in in /etc/default/grub then run update-grub)
[12:24] <jibel> shadeslayer, okay, I easily killed test machines with 8GB or more
[12:24] <jibel> your pick
[12:24] <shadeslayer> O_O
[12:25] <shadeslayer> 8 GB's? :O
[12:27] <jibel> autopilot run -r -rd /tmp/videos unity
[12:27] <jibel> run it twice and it'll use more than 10GB
[12:39] <jibel> shadeslayer, RELEASE is extracted from the image, I don't understand why it would fail. What's image are you using and what is its checksum?
[12:50] <shadeslayer> jibel: latest kubuntu saucy image
[12:50] <shadeslayer> jibel: got it to work
[12:50] <shadeslayer> kinda
[12:51] <shadeslayer> lightdm starts, it shows the ubuntu user, but I can't input anything via the keyboard
[12:55] <shadeslayer> jibel: df68d11b44b23bbef8ac42af59196105 is the md5sum
[12:55] <jibel> shadeslayer, thanks, I'll try with this image
[12:56]  * shadeslayer ponders how this will work on EC2
[13:25] <cjohnston> stgraber: pign
[13:25] <cjohnston> ping
[13:26] <stgraber> cjohnston: pong
[13:27] <cjohnston> stgraber: do you know how often the iso tracker updates its list of bugs?
[13:27] <cjohnston> or, more accuratly, the bug data..
[13:28] <stgraber> cjohnston: every 10 minutes for milestones marked as testing, every hour for milestones marked as released and once a day for disabled/archived milestones
[13:28] <cjohnston> cool. thanks
[13:31] <cjohnston> stgraber: is the script gaining anything by being authenticated?
[13:32] <stgraber> cjohnston: yes, the script comments on bugs and add tags, so if you use that feature, it needs a valid auth token
[13:32] <cjohnston> gotcha.. ty again
[13:32] <stgraber> (for ISO bugs we add iso-testing and add a comment with a URL back to a tracker page listing all results related to the bug number)
[13:33] <cjohnston> Interesting..
[13:50] <gema> apw: I finally got to install your kernel today, I am not completely convinced the saucy image I have works, but anyway
[13:51] <gema> apw: do you have any insights on this error: http://paste.ubuntu.com/5761460/
[13:58] <stgraber> gema: tried apt-get -f install? The error says you're missing wireless-crda so running apt-get -f install should install that for you and finish installing the new kernel
[13:59] <gema> yep, I did
[13:59] <gema> and i still don't see what apw added on sysfs, so I am not sure what I am missing
[13:59] <apw> gema, you don't install kernels in the image anyhow do you to use them, you have to abootimg them into the boot partition
[13:59] <gema> apw: ok, do you have any instructions on how to do that?
[14:00] <gema> apw: (I rather not break my n4 by doing something silly)
[14:09] <ePierre> Hi guys!
[14:18] <gema> apw: if you don't have time I can get help from ogra on this one
[14:22] <apw> https://wiki.ubuntu.com/Kernel/Dev/AndroidKernel
[14:22] <apw> gema, ^^ is hwat i use, the bit about abootimg
[14:23] <gema> apw: thanks
[14:37] <ePierre> Guys, a few questions regarding manual tests
[14:37] <ePierre> 1. who is going to run the manual tests written by the community?
[14:38] <ePierre> 2. I cloned the bar repo on my hard drive, and there are only manual tests for a handful of applications
[14:38] <balloons> ePierre, hello. We as a quality community team run the manual testcases
[14:38] <ePierre> for instance, no tests for Gimp for the moment
[14:38] <balloons> we run them normally on a regular basis during the cycle
[14:38] <ePierre> does it mean no one as ever written manual tests for Gimp before?
[14:38] <ePierre> ok
[14:39] <balloons> ePierre, yes there isn't one for gimp but you could help add one
[14:40] <ePierre> but
[14:40] <ePierre> there is not one for 13.10?
[14:40] <ePierre> or there never were any, even for previous versions?
[14:40] <balloons> check out the bugs list to see all of the needed testcases
[14:40] <ePierre> yes, I am checking this page right now :) that's why I pointed out Gimp
[14:40] <balloons> http://bugs.launchpad.net/ubuntu-manual-tests/+bug/1183009
[14:41] <balloons> yes it means nothing exists for gimp -- not just for 13.10.
[14:41] <ePierre> oh wah
[14:41] <ePierre> but when did you start making this quality process then?
[14:42] <ePierre> (no reproaches or anything, I'm just curious)
[14:42] <ePierre> and in that case, shouldn't we add the version number in the test case?
[14:42] <balloons> so you can see the repository of tests has grown a lot since earlier this year, but still has needs :-)
[14:42] <ePierre> so that someone willing to update the tests would know against what version this test has been written
[14:42] <ePierre> ?
[14:43] <balloons> ePierre, you mean a version number of the package in question?
[14:43] <ePierre> yes for instance
[14:43] <ePierre> cause for instance
[14:43] <balloons> when a package changes the test fails and we update it
[14:43] <ePierre> Gimp is not installed by default
[14:43] <balloons> the tracker retains the old testcase and old result
[14:44] <balloons> on ubuntu gimp is not installed by default
[14:44] <ePierre> but how do you know what version was used to write and run the test?
[14:44] <ePierre> sorry yes, on the original flavour :)
[14:44] <balloons> everything listed on the bugs list is a default application for at least one flavour
[14:44] <balloons> we started by getting tests for all the default ubuntu apps and now are branching out to get the flavors too
[14:45] <ePierre> ok I see
[14:45] <balloons> the version that was used to write the test? we always write the first version against ubuntu development
[14:45] <ePierre> ok
[14:45] <ePierre> but say I commit a test case today
[14:45] <ePierre> and it's not updated anymore for 3 months
[14:45] <ePierre> and in those 3 months, Gimp sees one or two updates
[14:46] <balloons> I do see point for concern about versioning but it's not been an issue
[14:46] <balloons> ePierre, yes indeed that could happen
[14:46] <ePierre> say current version is 2.8.1, and after 3 months it's 2.8.3
[14:46] <ePierre> ok
[14:46] <balloons> right
[14:46] <balloons> and odds are your test won't be broken
[14:46] <ePierre> that's why I was proposing to write the version number somewhere in the test case
[14:46] <ePierre> ok I see
[14:46] <balloons> if gimp decided to re-write everything then perhaps
[14:46] <ePierre> so when people run this test again in three months
[14:47] <balloons> it will still work, but they will be testing a newer version
[14:47] <ePierre> if it fails, it's either because there is indeed a bug in Gimp, or there is an issue with the test case itself
[14:47] <ePierre> ok I see
[14:47] <balloons> we have had major UI changes on a default app
[14:47] <ePierre> so manual test cases are to test pretty simple steps for the moment, right?
[14:48] <balloons> the nautilus testcase had to be updated. however it served us for a couple cycles and the new one is likely to do the same
[14:48] <balloons> once a test is written we endeavor as a team to keep it up to date and add to it if needed
[14:48] <balloons> ePierre, we try and have our manual tests hit the big stuff of the application
[14:49] <balloons> or something that has caused regressions/bugs in the past
[14:49] <ePierre> ok
[14:49] <ePierre> since Gimp is still test-free, I'll start with the big features
[14:50] <ePierre> and how can I know about the most annoying bugs/regressions for Gimp in the past?
[14:50] <ePierre> (for Gimp or for anything in general?)
[14:51] <balloons> if you don't know, then you can ask as you are doing, or check the buglist on gimp. i can't remember gimp ever giving us specific regressions or trouble so i think your fine
[14:51] <balloons> basically when we hit a nasty bug during the cycle for gimp we might decide to add it if we think it could occur again and us testing something would prevent it
[14:52] <balloons> this isn't a common thing persay, just something we can do
[14:52] <balloons> as far as developing an initial version of a test you needn't worry about it ;-)
[14:52] <balloons> get the big features in there
[14:53] <balloons> thanks ePierre ! let me know if you need anymore help
[14:54] <ePierre> thanks for your clarifications!
[14:54] <ePierre> can I assign the Gimp issue to me in launchpad?
[14:54] <balloons> ePierre, yes indeed go for it
[14:54] <ePierre> ok
[14:54] <balloons> DanChapman, howdy siir
[14:54] <balloons> how's the new laptop?
[14:56] <ePierre> to name the test cases, do I do it myself? like gmp-001 etc.?
[14:56] <ePierre> or will it be done automatically?
[14:57] <balloons> ePierre, yes you can number each one inside the file if you wish
[14:57] <balloons> the testcase itself will be given an id automatically
[14:58] <balloons> have you see the wiki guide?
[14:58] <ePierre> ok
[14:58] <ePierre> yes I'm reading it at the same time
[14:58] <ePierre> I knew about the test case ID
[14:58] <ePierre> was not sure about inside the test case :)
[14:58] <ePierre> thanks!
[15:01] <dpm> balloons, can you put this one on reddit? ;)  http://developer.ubuntu.com/2013/06/help-making-the-ubuntu-touch-core-apps-rock-solid/
[15:02] <ePierre> balloons: when writing the test steps, should I write prerequisites too?
[15:02] <balloons> dpm,  sure
[15:02] <ePierre> like for Gimp, say I want to test opening a big file
[15:02] <ePierre> I may want to put an URL to the file for reference
[15:04] <balloons> ePierre, I was speaking of this reference for style guidehttps://wiki.ubuntu.com/QATeam/ContributingTestcases/ManualStyleGuide
[15:04] <balloons> hopefully your questions are addressed there.. if not, I'll expand that page :-)
[15:04] <ePierre> ok, I'll have a look, thanks!
[15:04] <balloons> ePierre, what do you mean for prereq's too?.
[15:06] <ePierre> hm
[15:06] <ePierre> say my test is to make sure Gimp can open an image
[15:06] <ePierre> if I just say open an image
[15:06] <balloons> morning chilicuil
[15:06] <ePierre> the guy running the test may open a 32x32 pix image, and everything works fine
[15:06] <ePierre> but I may open a 50 MB picture
[15:06] <ePierre> that may crash Gimp
[15:06] <ePierre> in both cases
[15:07] <ePierre> we would have followed the same test steps
[15:07] <ePierre> yet different result
[15:07] <ePierre> if I specify the prerequisite is this 50MB picture
[15:07] <ePierre> then everyone will run the same test
[15:07] <ePierre> you know what I mean/
[15:07] <ePierre> ?
[15:07] <balloons> ePierre, yes I understand
[15:07] <knome> ePierre, i'd imagine big images could have their own test
[15:08] <ePierre> or am I being too picky here?
[15:08] <ePierre> yes, true
[15:08] <ePierre> a first test could be to open an image
[15:08] <ePierre> and another test would be for instance opening a very big image over the internet
[15:08] <ePierre> (cause there is such a feature in Gimpa after all)
[15:08] <balloons> ePierre, you could certainly specify opening a big picture if you wish.. however, part of the community testing of the testcase means that we'll all have slightly different setups
[15:09] <ePierre> ok
[15:09] <ePierre> ok ok
[15:09] <ePierre> :)
[15:09] <ePierre> I'l start with more simple tests
[15:09] <ePierre> we can always refine them later on
[15:10] <balloons> ePierre, yes indeed.. iterating is the way to go
[15:11] <balloons> knome how are you today?
[15:11] <balloons> feeling better now I hope
[15:11] <knome> balloons, fine - let me get back to you after our meeting :)
[15:31] <elopio> balloons: I'm going to take this one
[15:31] <elopio> https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1188732
[15:31] <balloons> elopio, excellent
[15:31] <ePierre> balloons: My first Gimp test is to check I can open an image
[15:32] <ePierre> it's called gmp-001
[15:32] <balloons> elopio, if possible have a look at the emulator I tried to make for these and let me know your thoughts
[15:32] <ePierre> in a lot of following tests, I will need to have an image open
[15:32] <elopio> balloons: is it on the filemanager branch?
[15:32] <Oranger> Hello everybody ! Is someone here working on a testcase for Ubuntu-Docviwer-App ?
[15:32] <balloons> elopio, lp:~nskaggs/+junk/ubuntusdk_autopilot_emulator
[15:32] <ePierre> can I just say, in my gmp-002 test case for instance: Run gmp-001 --> gmp-001 passes.
[15:32] <elopio> balloons: ack. I will.
[15:33] <ePierre> and then proceed to the rest of gmp-002 test steps?
[15:33] <balloons> elopio, the full details are here: https://plus.google.com/104307250302998042813/posts/XCaRM6W4Cnx
[15:33] <balloons> ty :-)
[15:33] <balloons> Oranger, hello!
[15:33] <Oranger> balloons: Hey ! :)
[15:34] <balloons> Oranger, no one is working on ubuntu doc-viewer atm
[15:34] <balloons> I was just sharing the emulator for these qml tests if your curious to write one.. check out the g+ link I pasted
[15:34] <Oranger> balloons: Ok :) Because if someone do, I can help
[15:35] <Oranger> balloons: Oh good, yes I will have a look
[15:35] <balloons> ePierre, yes you can say the pre-req is to have run an earlier test
[15:35] <balloons> ePierre, in general the tests are run in order so it's not an issue :-)
[15:36] <ePierre> ok
[15:36] <ePierre> thanks
[15:36] <balloons> also, if you need a specific image to test with you can check out the example content.. or even have people screenshot there desktop and create one
[15:42] <elopio> balloons: the emulator looks really useful. But how would we share it between projects?
[15:42] <balloons> elopio, well that's an open question. I wanted to have some folks try using it and get feedback on what might be missing and see if it's useful, etc
[15:43] <balloons> atm we've just branched it and put it into the sourcetree of the project using it
[15:43] <elopio> balloons: I'll copy the parts I will use in this test
[15:43] <elopio> and when we have it in a common project, just let me know and I'll update.
[15:43] <balloons> elopio, so if you take a look you can incorporate it into the test setup so it's just a file you can update
[15:44] <DanChapman> Hey balloons it still hasn't arrived!!! :-( So im trying to do it on an old box I have, but its a bit to old for the job I think :-) will keep battling with it. ANd keep an ear out for that delivery man aswell ;-)
[15:44] <balloons> the question is -- is having a versioned file you can pull to update at any point enough./
[15:44] <balloons> DanChapman, ohh sorry to hear mate!
[15:44] <balloons> elopio, so for instance nik90 and I added it to ubuntu-clock and he's using it there
[15:45] <balloons> you modify the __init.py__ to include it and through it in the emulators folder along with something like your main_window.py emulator, etc
[15:46] <DanChapman> I was gonna get my self a thinkpad would have arrived on monday, but thought no i'll get myself a sputnik, regretting it at the moment, hope the wait is worth it
[15:46] <balloons> then all he has to do to get a new version is re-pull the branch
[15:46] <elopio> balloons: yes. I'm on it. It will make things a lot easier than I thought :)
[15:48] <balloons> Oranger, so have you ever tried writing an autopilot test for ubuntu-docviewer?
[15:49] <balloons> I see there is a basic setup for autopilot on your project already.. Care to give it a whirl with me? I'll help :-)
[15:49] <Oranger> balloons: No I don't, I didn't have the time for ^^'
[15:50] <Oranger> balloons: Yes of course :)
[15:50] <balloons> Oranger, alright.. so looking over the buglist, let's see
[15:53] <balloons> Oranger, can we try something simple like opening a file? https://bugs.launchpad.net/ubuntu-docviewer-app/+bug/1188757
[15:54] <Oranger> balloons: Yes :) This testcase will change soon because the way docviewer is opening a file is temporary, but for training why not !
[15:55] <balloons> ok great.. So let me branch the code and see how it works.. then we'll automate it :-)
[15:55] <balloons> well actually I don't think the branch has been updated since my last pull :-0
[15:56] <Oranger> nope :)
[15:56] <Oranger> i'm currently working on the update, but it's a big update, that's why nothing was added ^^'
[16:04] <elopio> do you know where can I get this package from?
[16:04] <elopio> qtdeclarative5-nemo-qml-plugins-folderlistmodel
[16:05] <balloons> is it in qtdeclarative5-*?
[16:05] <balloons> qtdeclarative5-folderlistmodel-plugin?
[16:06] <ePierre> ok balloons , I have pushed my Gimp tests to my repo, and proposed it to be merged
[16:06] <ePierre> it's rev 123
[16:06] <balloons> ePierre, excellent I'll review in a moment
[16:06] <balloons> Oranger, ok I think I'm all setup
[16:06] <ePierre> (I tested the file against the tidying up script and it's clean)
[16:06] <balloons> ePierre, perfect :-)
[16:06] <ePierre> it's time for bed here, but I'll keep doing this later
[16:07] <balloons> ePierre, thanks mate!
[16:07] <Oranger> balloons: Ok :)
[16:07] <elopio> balloons: I have that one installed. But I get file:///home/elopio/workspace/ubuntu/ubuntu-filemanager-app/trunk/ubuntu-filemanager-app.qml:20 module "org.nemomobile.folderlistmodel" is not installed
[16:07] <ePierre> in the meantime, should I just de-assign the bug from me, or should I keep it?
[16:07] <balloons> elfy, see 2 manual tests in already today ;-p
[16:07] <elfy> xubuntu ones?
[16:07] <knome> ePierre, keep it if you're definitely getting back to it
[16:07] <elfy> :p
[16:08] <balloons> elfy, one xubuntu one
[16:08] <ePierre> ok then I'll keep it for the moment
[16:08] <balloons> and the next could be yours
[16:08] <elfy> balloons: cool :)
[16:08] <elfy> my what?
[16:08] <knome> balloons, btw, give elfy all the permissions he asks for :P
[16:08] <balloons> knome, elfy scares me.. of course he gets what he wants
[16:08] <elfy> lol
[16:08] <ePierre> I'm off for tonight. Bye everyone!
[16:08] <knome> haha:)
[16:09] <balloons> ePierre, night!
[16:12] <balloons> ok Oranger, so how can I open a text file.. do I have to pass it as an argument?
[16:13] <Oranger> balloons: For the time being yes ! But you have to pass it as an absolute path
[16:13] <Oranger> This is something I have to fix..
[16:14] <balloons> ohh, that's why it failed :-) Ok
[16:15] <Oranger> balloons: Ahah, sorry. I should write it on the README ^^
[16:19] <balloons> Oranger, odd it doesnt' like  me
[16:19] <balloons> I remember using it before
[16:19] <balloons> I'm trying to open the README from the branch using doc-viewer
[16:19] <elopio> somebody knows the Arto Jalkanen's nick on IRC?
[16:20] <Oranger> balloons: It should work :)
[16:20] <elopio> mhall119?
[16:24] <balloons> Oranger, qmlscene ubuntu-docviewer-app.qml path/to/file
[16:24] <Oranger> balloons: Nop. ubuntu-docviwer-app path/to/file
[16:25] <balloons> ahh :-)
[16:25] <Oranger> like every core apps, you don't have to use qmlscene :)
[16:25] <balloons> ok perfect
[16:33] <balloons> Oranger, ok, so I think what we'll do is write a test to open the file, but function out the file open as a common function because we'll need it later
[16:34] <balloons> in addition since we have to use absolute filenames, I'll generate a temp file for us to use
[16:34] <balloons> that way we have the absolute path
[16:36] <Oranger> balloons: Sound good :)
[16:36] <Oranger> balloons: But we really need to generate a temp file to use absolute path ?
[16:37] <balloons> we could include test data.. but how are we to know where the test is being run from
[16:37] <balloons> we're stuck copying it to /tmp
[16:37] <balloons> well, I'm being silly
[16:37] <balloons> your right
[16:42] <Oranger> balloons: Ok :) So, how can we start writing it .?
[16:42] <balloons> Oranger, ok so I've made some small tweaks to your base setup with autopilot
[16:43] <balloons> so we commit those, then share a pad to hack on?
[16:43] <balloons> http://pad.ubuntu.com/VHU5Nu253n
[16:44] <balloons> hello Vasudevan !
[16:45] <Vasudevan> Hi balloons, good morning
[16:45] <balloons> Oranger, so I'll hack away in here: http://pad.ubuntu.com/VHU5Nu253n
[16:45] <balloons> join in :-)
[16:48] <balloons> hello SergioMeneses
[16:48] <balloons> so Vasudevan how's nautilus treating you?
[16:48] <Vasudevan> no luck yet - I will copy the code to past in a minute
[16:48] <SergioMeneses> balloons, hi! how's everything?
[16:49] <Vasudevan> I tried to use a tool called gtkparasite, does not run on saucy
[16:50] <Vasudevan> google code had some patch for it - tried to apply that  (both #5 and #6)and still did not work
[16:50] <balloons> Vasudevan, I'm not sure why you need that tool?
[16:51] <Vasudevan> ballons, it is supposed to dump out the props of a gtk child window for quick debugging
[16:52] <Vasudevan> when you click on a widget , it will show its  internal id, label, name  etc
[16:53] <balloons> ahh.. probably needs accesibility stuff anyway
[16:53] <balloons> you can use the vis tool, but I agree it's cubersome at times
[16:53] <balloons> SergioMeneses, not too bad, yourself/
[16:55] <elopio> is there a way to inspect with the vis an app running in qmlscene?
[16:55] <SergioMeneses> balloons, still working but all fine here :D
[16:55] <balloons> elopio, there is
[16:57] <SergioMeneses> ok guys see yoo soon, lunchtime here
[16:58] <balloons> elopio,
[16:58] <balloons> autopilot launch -i Qt qmlscene /path/to/file.qml
[16:58] <balloons> autopilot vis
[16:58] <elopio> thanks balloons.
[17:00] <balloons> Oranger, I'm hacking on the init.py to make setup behave
[17:01] <Oranger> balloons: ok :)
[17:03] <Vasudevan> Hi DanChapman
[17:07] <balloons> bah, the only horrible thing about copy paste python
[17:07] <balloons> spaces matter :-(
[17:08] <samgabbay> BALLONS :P
[17:11] <elopio> balloons: that shows me just a QQuickView, not the whole app tree :(
[17:12] <balloons> mmmm.. not sure what you need that might be missing, but the folks on #ubuntu-autopilot might be able to point you further.. if not, bug filing time
[17:12] <balloons> samgabbay, hello
[17:12] <balloons> broccoli, howdy
[17:13] <balloons> Oranger, bah, this is annoying
[17:13] <balloons> I'm not sure off the top of my head how to get this call to work properly
[17:13] <Oranger> balloons: I'm doing some research to find out how to make it work too..
[17:14] <balloons> the executable isn't working
[17:14] <Oranger> the executable ?
[17:14] <balloons> can't we just use qmlscene?
[17:14] <Oranger> it won't start ?
[17:14] <balloons> autopilot is throwing up on me
[17:15] <Oranger> balloons: Currently not, in a near future yes. Ubuntu-docviewer use a modified qmlscene :/
[17:15] <balloons> Oranger, yes launch_test_application fails
[17:16] <Oranger> balloons: With qmlscene, it will not work, that's sure
[17:17] <Oranger> balloons: This is the ubuntu-docviewer-app binary that send the file to open to qml
[17:20] <balloons> right but autopilot can't find it
[17:20] <balloons> it's not there
[17:21] <balloons> in the root folder of the branch, what's providing the binary?
[17:21] <balloons> you see I'm just passing ubuntu-docviewer-app as the app to start and it fails
[17:22] <Oranger> balloons: Yes I see it
[17:23] <Oranger> balloons: Hum.. You compiled by "hand" ?
[17:28] <DanChapman> Hey Vasudevan :-)
[17:29] <balloons> Oranger, what do you mean by hand?
[17:30] <balloons> I'll push the whole branch :-)
[17:30] <elopio> balloons: my suggestion for the sdk emulator is to make it an abstract parent for the real view emulators
[17:30] <balloons> the real view emulators?
[17:31] <Oranger> balloons: I mean maybe the binary is located somewhere else ? I don't know ^^
[17:31] <elopio> balloons: on your currency example, if the MainWindow class could inherit from ubuntusdk
[17:31] <balloons> I didn't compile anything
[17:32] <elopio> I could do thinks like main_window.open_toolbar
[17:32] <balloons> elopio, ahh yes.. I messed around with trying to make it integrate better, but didn't have success
[17:32] <balloons> if you can do it, go for it and share ;-)
[17:32] <balloons> Oranger, lp:~nskaggs/ubuntu-docviewer-app/autopilot-hacking
[17:33] <elopio> balloons: I can try. But tell me what when wrong with yours, so I don't repeat it :)
[17:33] <Oranger> balloons: Oh, because you have to compile the "special" qml scene :)
[17:33] <Oranger> balloons: thanks :)
[17:33] <Vasudevan> Hi Dan, please review the code - I am trying to get the widget props for right side pane  with in nautilus - http://paste.ubuntu.com/5762109/
[17:33] <balloons> elopio, ahh I simply had trouble getting everything lined up sanely. namely mainwindow has non-abstractable things in it
[17:34] <balloons> Oranger, yes help me out :-)
[17:34] <balloons> the test does nothing atm, just trying to get the launch to work.. that's the hard part in this case lol
[17:34] <balloons> the rest will be easy
[17:34] <Oranger> balloons: apparently yes ^^
[17:34] <elopio> I think the problem would be to define what things will be shared by all the views. I need to dig more on the sdk, so don't expect anything soon ;)
[17:34] <balloons> elopio, at the same time you need to integrate somewhat with __init__.py
[17:35] <DanChapman> Vasudevan ok will take a look
[17:35] <Vasudevan> Danchapman , thanks
[17:35] <balloons> I would very much like to simplify the default setup.. I dislike making lots of files and folders for things
[17:36] <balloons> but not everyone agrees I'm sure ;-) heck, I don't like using underscores etheir :-p
[17:36] <balloons> I prefer the camelCase
[17:36] <balloons> Oranger, so what needs to happen to get this launched?
[17:38] <balloons> I can go to the root of the tree and run ubuntu-docviewer-app, presumably from the desktop file.. ahh hmm
[17:44] <Oranger> balloons: Hum not, you don't need to do that normaly
[17:44] <Oranger> balloons: Wait few minutes ;) I finish my work on poppler, and i'm to you !
[17:45] <balloons> kk
[17:48] <Oranger> balloons: You know, with the alpha oncoming I have a lot of things to finish ^^'
[17:51] <balloons> indeed
[18:05] <elopio> balloons: can you give me a hand? I can't get the buttons on the filemanager app.
[18:05] <balloons> elopio, sure thing
[18:05] <balloons> can you push what you've got and I'll take a look/
[18:05] <elopio> self.app.select_many("Action")
[18:06] <elopio> I thought that was all I needed.
[18:06] <elopio> balloons: sure, one second.
[18:06] <phillw> Oranger: you can heave a sigh of relief, the Alpha1 is going to be knocked back a week. The release team are just re-scheduling https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule as it has some errors (e.g. there will be no A3)
[18:06] <phillw> I'm just awaiting the revised version to be completed :)
[18:08] <Oranger> phillw: June 20th ? This is the new date ?
[18:08] <elopio> balloons: https://code.launchpad.net/~elopio/ubuntu-filemanager-app/fix1188732-test_open_directory/
[18:09] <phillw> Oranger: those dates still have to be altered, I've been watching (and involved with) the discussion on -release. Expect an email soon with the new details
[18:11] <phillw> I'm just pulling in the new lubuntu with Ffox instead of chromium etc which has just built. The -release team will get the new dates edited in soon :)
[18:12] <balloons> philipballew, finally rescheduling :-)
[18:12] <Oranger> phillw: Ok :) I thought the alpha-1 was for the JUne 16th
[18:13] <Oranger> phillw: But that's good, I'm waiting for the poppler team to commit my patch for displaying pdf on docviewer-app
[18:15] <balloons> phillw, so did elfy end up chatting with them/
[18:15] <elfy> not yet
[18:15] <elfy> #busybeingdad
[18:16] <balloons> ok elopio so you can't get to the buttons?
[18:16] <elopio> balloons: nop. It fails here http://bazaar.launchpad.net/~elopio/ubuntu-filemanager-app/fix1188732-test_open_directory/revision/37/tests/autopilot/ubuntu_filemanager_app/emulators/main_window.py
[18:17] <balloons> mine doesn't seem to launch
[18:17] <phillw> balloons: IDK, inifinity realised he hadn't updated it from vUDS. A quick chat was had, and it is to be edited with A1 going a week later, dropping A3 and moving A2. That's the news so far. I await the edited version so that we can tell people about it (and I reschedule the lubuntu general meetings)
[18:17] <balloons> I get the lovely: module "org.nemomobile.folderlistmodel" is not installed
[18:19] <elopio> balloons: I had to get the branch and make install
[18:19] <balloons> phillw, yea I had been waiting on him and noticied her never did change it
[18:19] <balloons> why does filemanager want it though
[18:19] <balloons> so weird
[18:20] <balloons> elopio, so how can I get it?
[18:20] <elopio> https://code.launchpad.net/~ajalkane/ubuntu-filemanager-app/qml-folderlistmodel
[18:20] <elopio> there's a read me inside.
[18:20] <elfy> phillw: dropping a3 ?
[18:20] <elopio> I was looking for ajalkane to ask about the package, because according to the debian folder there's one.
[18:21] <phillw> elfy: indeed, the schedule *should* have been more like https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule
[18:22] <elfy> as far as I know it's exactly like that :D
[18:22] <elfy> a3 included :p
[18:22] <phillw> elfy: raring did not have A3
[18:23] <elfy> that wiki ^^ does :p
[18:23] <balloons> elopio, bah I can't run it
[18:23] <phillw> elfy: soz, wrong link... it *should* have been more like https://wiki.ubuntu.com/RaringRingtail/ReleaseSchedule
[18:23] <elfy> :)
[18:23] <balloons> elopio, anyways if that button is a toolbar button you can use the emulator to get it
[18:23] <phillw> darn copy & paste!
[18:23] <elfy> I blame joeb
[18:23] <balloons> let me just look at the code
[18:24] <elfy> phillw: so xubuntu just had a meeting and agreed to not do a1 but do both a2/a3 :)
[18:24] <elopio> balloons: ah, right.
[18:25] <balloons> elopio, ahh yes it is. I see it in FolderListPage.qml
[18:25] <elopio> balloons: I tried that, but the tooldbar is of type ToolbarActions
[18:25] <balloons> elopio, ok so the emulator failed you.. let's fix it :-)
[18:26] <elopio> balloons: yes, now I see the rest of get_toolbar_button will work.
[18:26] <balloons> if you want to click it, click_toolbar_button
[18:26] <balloons> so the get_toolbar should probably be modified actually
[18:27] <balloons> perhaps not.. I'm wondering if a name should be passed or not
[18:29] <phillw> elfy: I sent out all our monthly meetings based on the milestone releases..... These things happen! (we weren't going to do A2 as our testers asked for one full suite per ~month)
[18:29] <elfy> :)
[18:29] <elfy> we do fortnight meetings at the moment
[18:30] <phillw> we're going to ~monthly based on the milestones as that is when 'things happen' :)
[18:30]  * phillw is glad he did not book -meetings room :D
[18:31] <elfy> :)
[18:33] <balloons> elopio, things working ok now?
[18:33] <phillw> elfy: I've just poked infinity. As long has he does not kick-ban me, he should get onto it real soon :)
[18:33] <elopio> balloons: haven't tried yet. I'm going slow because I have to do stuff for my job, you know ;)
[18:34] <balloons> lol, that thing!
[18:34] <elfy> phillw: well I'm subscribed to the page so I'll find out :)
[18:34] <balloons> just ping if you get stuck again
[18:35] <phillw> elfy: " infinity: phillw: It'll be done this afternoon/evening."
[18:35] <elfy> :)
[18:35] <phillw> USA time, I assume
[18:36] <elfy> balloons: tomorrow I need to try and tie up a couple of things - will you be about?
[18:37] <Letozaf_> balloons, Hi
[18:37] <balloons> Letozaf_, hello
[18:37] <Letozaf_> balloons, what are you guys hacking on ?
[18:38] <balloons> Letozaf_, we had a couple manual tests this morning and now we're hacking on autopilot qml apps
[18:38] <balloons> elopio is working on file manager and I was working with Oranger on doc-viewer..
[18:38] <Letozaf_> balloons, good yesterday I was trying out the ubuntu_calendar_app
[18:39] <Letozaf_> balloons, what is Oranger
[18:40] <phillw> Letozaf_: it is *who* is Oranger :)
[18:40] <Oranger> Letozaf_: Yes ? :)
[18:40] <Letozaf_> Oranger, oh! sorry thought your were a sofware of something like that :D
[18:41] <Oranger> Letozaf_: Ahah I can be ! :D
[18:41] <phillw> lmfao :D
[18:41] <Letozaf_> Oranger, pleased to meat you
[18:41] <balloons> Letozaf_, Oranger lol
[18:41] <phillw> that's as bad as people on lubuntu keep thinking unit193 is a bot :)
[18:42] <balloons> I'm just a helium filled toy
[18:42] <balloons> Letozaf_, calendar app sounds like a good plan.. how'd you do?
[18:42] <balloons> There's an emulator for autopilot to make things easier.. care to share your branch?
[18:43] <Letozaf_> balloons, I get stuck after opening the new event window
[18:44] <Letozaf_> balloons, emulator ? cool, thought I read something quickly on that but I always got little time
[18:44] <Letozaf_> balloons, sure I will share what I did, I will push it , just a second
[18:46] <balloons> Letozaf_, we'll get you hacking in no time.. :-p
[18:46] <Letozaf_> balloons, great !
[18:47] <Letozaf_> balloons, I pushed the calendar app
[18:51] <balloons> Letozaf_, grabbing it
[18:51] <Letozaf_> balloons, ok thanks :)
[18:51] <balloons> k 2 tests ;-)
[18:52] <balloons> so let's have a look.. what test where you trying t odo
[18:52] <balloons> ahh test new event I see
[18:52] <Letozaf_> balloons, with autopilot vis I see the "visible" attribute, but instead I get an error saying it-s not there
[18:54] <balloons> that's odd.. I think there might be a bug on one of those attributes.. that might be it
[18:54] <Letozaf_> balloons, if you comment line 55 you get an error on the self.pointing... line, to me it looks ok, do not know where the error is
[18:54] <balloons> but it shouldn't be an issue at all
[18:55] <balloons> I'm gonna make some edits to add the emulator I made and push it
[18:55] <Letozaf_> balloons, looks like everything is in the new event window is spooky
[18:56] <Letozaf_> balloons, great! (I mean for the emulator)
[19:00] <balloons> ok, running and pushing it back
[19:04] <balloons> hehe..I broke it Letozaf_
[19:04] <balloons> let me push so you can see though
[19:05] <Letozaf_> balloons, :-) sure
[19:05] <balloons> lp:~nskaggs/ubuntu-calendar-app/sdk-emulator-hack
[19:05] <balloons> so inside the emulators folder you'll see a file called ubuntusdk.py
[19:05] <balloons> it has some utility functions making life easier
[19:07]  * Letozaf_ is looking at ubuntusdk.py
[19:10] <elopio> balloons: I'm peeking at the sdk, and this looks like a good place for your emulator: http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/files/head:/tests/autopilot/UbuntuUiToolkit/emulators/
[19:10] <balloons> elopio, that does look great, thanks!
[19:10] <elopio> or somewhere up, in testing/autopilot/
[19:10] <balloons> right right
[19:11] <balloons> so Letozaf_ where did you get stuck on calendar anyway?
[19:14] <Letozaf_> balloons, after opening the new event window, not only line 55 with the assertion give me problems, if I comment that then I get stuck on line 57 trying to click on any filed in the new event windos
[19:14] <Letozaf_> sorry window
[19:14] <balloons> like         #self.pointing_device.click_object(people_field)
[19:15] <Letozaf_> balloons, yes but also the event_name_filed
[19:15] <Letozaf_> balloons, I've kind of tried them all, but I get errors so I commented them
[19:16] <balloons> gotcha
[19:16] <balloons> ok what error do you get?
[19:16] <balloons> I've changed things now and broken it
[19:17] <balloons> ohh.. LOLOLOLOL
[19:17] <balloons> I was modifying the wrong file !
[19:18] <Letozaf_> balloons, http://paste.ubuntu.com/5762425
[19:19] <balloons> Letozaf_, ahh so when you see those errors it means you failed to get an object
[19:20] <balloons> so event_name_field is blank
[19:20] <balloons> so get_new_event_name_input_box must not be working
[19:21] <Letozaf_> balloons, also the others seem to not work :(
[19:21] <balloons> did you check the qml to make sure newEventName is degined/
[19:21] <balloons> ahh I see it
[19:22] <Letozaf_> balloons, yes
[19:22] <balloons> it's in NewEvent.qml
[19:22] <balloons> ah-ha
[19:22] <balloons> looks like it's a popover
[19:22] <balloons> so you can use the popover stuff in the emulator to help (I hope)
[19:22] <balloons> so let's see
[19:24] <balloons> self.ubuntusdk.set_popup_value("popover" ...)
[19:25] <Letozaf_> balloons, ok let me try
[19:25] <balloons> let me figure out why the toolbar functions don't seem to like this app
[19:25] <balloons> it's growing pains for the emulator :-)
[19:25] <balloons> works great on the other apps I've tried
[19:26] <balloons> Letozaf_, the trouble is you need to define a button
[19:26] <balloons> and it's a little different than the original intent of the function.. but we should be able to craft something new to help you and others I hop
[19:27] <Letozaf_> balloons, ok
[19:27] <balloons> let me push an update I think might owkr
[19:30] <balloons> Letozaf_, perhaps -- http://paste.ubuntu.com/5762467/
[19:30] <balloons> add that to the ubuntusdk.py file
[19:30] <balloons> then call it with
[19:30] <balloons> self.ubuntusdk.set_popup_value("popover","newEventName")
[19:30] <balloons> err
[19:31] <balloons> self.ubuntusdk.click_popup_field("popover","newEventName")
[19:31] <Letozaf_> balloons, ok
[19:42] <balloons> howdy Noskcaj
[19:42] <balloons> Letozaf_, hmm.. no fine
[19:42] <Noskcaj> morning balloons
[19:42] <balloons> you always like to find the problematic stuff eh? :-0
[19:43] <Letozaf_> balloons, it looks like
[19:43] <Letozaf_> balloons, I'm also having trouble here :)
[19:44] <balloons> Letozaf_, yea no fun.. If you want something that is working well, check out the clock app
[19:45] <balloons> bzr branch lp:~nskaggs/ubuntu-clock-app/sdkemulator
[19:45] <balloons> for what it's worth.. looks like I've got some more hacking on the emulator to do to figure out why it's not working
[19:45] <balloons> and also to add support for your popover text fields
[19:46] <balloons> that was part of the plan today.. glad you found the holes :-)
[19:46] <elopio> balloons: it's not working. I can get QQuickLoader, though.
[19:46] <elopio> I don't understand this part of your code. Can you please explain it to me?
[19:46] <Letozaf_> balloons, ok I will take a look at the clock-app  :) well let's say you dont' get bored with my stuff :)
[19:46] <elopio> http://paste.ubuntu.com/5762515/
[19:47] <balloons> elopio, I'm noticing that isn't working with the calendar app for some reason :-(
[19:47] <balloons> elopio, however it's intended to check the list of buttons found on the toolbar
[19:48] <balloons> you match based on the button label
[19:48] <Noskcaj> balloons, when you have a second, you need to give a final decision on "this should happen" vs "this happens" because we need the same format across all testcases
[19:48] <elopio> balloons: but get_objects expects an objectName as the second parameter
[19:49] <balloons> Noskcaj, we decided it should be 'this' happens
[19:49] <elopio> and what you are passing is a QQuickLoader
[19:49] <balloons> elopio, it may very well be broken ;-)
[19:49] <balloons> let's see
[19:49] <Noskcaj> balloons, ok, i'l convert stuff to that and edit the wiki if you haven't already
[19:49] <balloons> ty Noskcaj
[19:50] <Letozaf_> balloons, nice the clock-app I mean :-)
[19:50] <balloons> elopio, ok yes I see I have a QQuickLoader
[19:50] <elopio> balloons: that's my first problem. The second is that get_objects does self.app.select_many("Actions")
[19:50] <elopio> and that doesn't anything here.
[19:50] <balloons> what's wrong with the select_many?
[19:51] <elopio> balloons: I don't know. It just seems it's not finding any actions elements.
[19:51] <balloons> elopio, yes that's the issue in the calendar app also
[19:52] <elopio> balloons: I'll ask on the autopilot channel.
[19:52] <balloons> so I'm going to try changing how we get stuff
[19:53] <balloons> elopio, just grabbing buttons instead of the quickloader
[19:53] <elopio> balloons: with buttons, do you mean actions?
[19:56] <balloons> elopio, I'm introspecting to have a deeper look
[19:56] <balloons> QQuickLoader has a Button child
[19:58] <elopio> balloons: are you introspecting the files app?
[19:59] <balloons> elopio, no the calendar
[20:00] <balloons> I think I can simplify the original code
[20:01] <elopio> I'll take a look at the calendar to see why I can't introspect the others.
[20:03] <balloons> elopio, I only have QQuickView
[20:03] <balloons> I'm not sure what your expecting to see
[20:03] <elopio> balloons: the children of QQuickView
[20:04] <balloons> click them they are there
[20:04] <balloons> I can't run filemanager so I can't check :-)
[20:04] <balloons> but yea, I've never had issues with seeing things
[20:05] <elopio> http://ubuntuone.com/3V9upWTm8ld2p4zpMHk5vd
[20:05] <elopio> balloons: ^ is that what you see?
[20:06] <balloons> elopio, ahh no.. that expands for the whole tree
[20:07] <balloons> elopio, http://imgur.com/DemSzqx
[20:08] <elopio> :( I've tried the calendar with the same result. So it must be something in my machine.
[20:08] <balloons> wild
[20:08] <balloons> i'm on saucy
[20:09] <balloons> I used the launch tool and vis
[20:09] <balloons> it *should* work.. sadly thomi is out ;-(
[20:12] <balloons> got it.. fixed the toolbar button
[20:13] <balloons> this is what happens when you take shortcuts kids
[20:15] <elopio> I'm on raring
[20:18] <balloons> boom, perfect answer
[20:18] <balloons> blame raring :-)
[20:23] <elopio> I can upgrade later.
[20:23] <elopio> still, that doesn't solve the problem of the actions.
[20:23] <elopio> well, maybe it does :)
[20:24] <elopio> tomorrow I'll let you know how it went.
[20:24] <balloons> the actions?
[20:24] <balloons> there will be an update to the emulator.. I fixed some things
[20:24] <balloons> and I've got more to add for Letozaf_
[20:24] <elopio> balloons: yes, here self.select_many("Actions") return nothing.
[20:24] <balloons> in the emulator or just in general?
[20:25] <balloons> the function in the emulator is fixed now as soon as I push it :-)
[20:27] <elopio> balloons: in the files app. It works with the calculator.
[20:31] <balloons> elopio, the files app author is around
[20:31] <elopio> \o/
[20:31] <elopio> hello ajalkane.
[20:31] <ajalkane> howdy
[20:33] <elopio> ajalkane: where can I get the qtdeclarative5-nemo-qml-plugins-folderlistmodel package?
[20:34] <popey> https://launchpad.net/~ubuntu-touch-coreapps-drivers/+archive/daily
[20:34] <elopio> thanks popey!
[20:34] <popey> np
[20:35] <ajalkane> ^ what popey said about the packages. If sources are needed, then it's an answer with more multitude of options
[20:36] <ajalkane> But basically if this is about autopiloting the FileManager app, only that package is needed
[20:36] <elopio> ajalkane: yes, I don't need the source.
[20:36] <elopio> I'm having some problems, but we will blame raring for now
[20:37] <elopio> so if everything works on saucy, I'll have a couple of tests tomorrow.
[20:37]  * Letozaf_ will be back tomorrow evening to see the new things you have found o/
[20:37] <ajalkane> That's great. You can of course do some copy-pasting on the problem, and I can tell immediately if I have an idea what it's about
[20:38] <elopio> ajalkane: https://code.launchpad.net/~elopio/ubuntu-filemanager-app/fix1188732-test_open_directory/
[20:38] <elopio> that's what I have.
[20:38] <elopio> autopilot select_many is not finding the action elements
[20:39] <ajalkane> elopio: right on. Unfortunately anything relating to autopilot I'm no good on just yet :)
[20:40] <elopio> I'm not that good at autopilot either. But I have weird behaviors that the people on saucy are not having.
[20:40] <elopio> so, I'll first try saucy.
[20:40] <balloons> elopio, we can blame raring for that too hah!
[20:41] <balloons> the point is if autopilot vis can't see it, neither is running autopilot going to work
[20:41] <ajalkane> elopio: but if you're trying to do some specific test, can you update (if it's possible) this page: https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/initial-filemanager-development
[20:41] <elopio> balloons: that's a weird thing, because autopilot sees some other stuff, like ActionSelectionPopover
[20:41] <elopio> not the vis, but on the test case.
[20:42] <balloons> elopio, ahh.. your just special.. I would try and run it on my box.. but I couldn't before
[20:42] <ajalkane> There's "work items for coreapps-13.10-month-3" with the test cases... just put it to INPROGRESS with your nick so that I or someone else does not try to duplicate the work
[20:42] <balloons> I guess popey gave us the package so I would try again
[20:43] <balloons> so I'll install, and I'd be happy to run your filemanager test to try it on saucy
[20:43] <ajalkane> Ah hum... people are already on saucy? :) I just recently upgraded to raring as everyhing started breaking on 12.10
[20:43] <elopio> ajalkane: done.
[20:43] <ajalkane> elopio: thanks!
[20:44] <balloons> ajalkane, we're always running ubuntu development
[20:44] <elopio> ok, I'll break for a while.
[20:45] <elopio> here it's raining like it's the end of the world. The perfect moment for a nap :)
[20:45] <balloons> elopio, if you have something for me to try ping
[20:45] <ajalkane> balloons: aah, but you're some hardcore canonical hacker ;)
[20:45] <balloons> enjoy your nap :-)
[20:45] <Noskcaj> balloons, i've pushed a fix for all the dd issues
[20:45] <balloons> ajalkane, lol not really.. the quality team all does
[20:45] <elopio> balloons: I will. Please push your changes to the emulator so I can use them too.
[20:45] <balloons> elopio, sure thing
[20:45] <balloons> Noskcaj, thanks
[20:46] <balloons> I'll review and merge in a few mins
[20:46] <balloons> thanks for iterating on all those tests
[20:46] <balloons> everything is so much nicer, but when you crack open the box and find a mess sometimes it turns out to be bigger than you thought
[20:46] <balloons> but hey since you opened the box, we needed to fix it all :-)
[20:47] <balloons> weird apt doesn't see the package even though i've had that repo tha whole time :-(
[20:47] <ajalkane> Glad there's some people in the frontlines making it safer for the rest uf ;)
[20:48] <balloons> ohh it's qtdeclarative5-nemo-qml-plugins-folderlistmodel
[20:48] <balloons> grumble grumble
[21:31] <Noskcaj> balloons, why does testcase 1521 test wireless a? i doubt anyone still uses that
[21:31] <balloons> Noskcaj, it still exists and is supported
[21:31] <balloons> technically b is the most unused
[21:31] <balloons> it's a,g or n
[21:32] <Noskcaj> balloons, ok, then why don't we test n or ac?
[21:32] <balloons> we should test n :-)
[21:32] <Noskcaj> oops, just saw that. why don't we test ac?
[21:32] <balloons> c doesn't exist
[21:32] <Noskcaj> ac does
[21:32] <Noskcaj> also, a lot of touch testcases still need numbers
[21:32] <balloons> ahh yes
[21:33] <balloons> no one is likely to have ac, haha.. but yea once it's supported in network manager we should add it
[21:36] <Noskcaj> If network manager doesn't support it, that a pretty big bug
[21:39] <Oranger> balloons: Ok, I have watch your code, and it don't work for me too ^^
[21:39] <balloons> Noskcaj, I don't know if it does or not
[21:39] <Oranger> balloons: I'm trying to find how to fix it :)
[21:39] <balloons> elopio, et la, the new version of the emulator is pushed
[21:42] <balloons> Oranger, ohh the doc view app
[21:42] <balloons> well I fixed 2 apps today now.. heh, let's go back to it I suppose
[21:42] <balloons> i only have a couple more mins
[21:42] <balloons> first I must merge Noskcaj's changed
[21:43] <Oranger> balloons: Because you had the same problem with other apps ?
[21:47] <balloons> Noskcaj, whew, ok small fixes
[21:47] <balloons> time to push ;-)
[21:48] <Noskcaj> should i start converting all the testcases to "this happens"
[21:48] <balloons> Noskcaj, I would prefer it just happens naturally
[21:49] <Noskcaj> ok
[21:49] <balloons> meaning, if you edit an old testcase bring it up to date
[21:49] <balloons> it's easier and saner for everyone that way ;-)
[21:49] <Noskcaj> makes sense
[21:49] <balloons> the linux kernel has a similar thing about trailing spaces
[21:53] <balloons> ohh a new case.. 1485 is gone now.. so interesting
[21:53] <Noskcaj> balloons, which was 1485?
[21:53] <balloons> memtest
[21:53] <balloons> need to gut it on the tracker
[21:53] <Noskcaj> You said we should delete t
[21:54] <balloons> yes yes your right
[21:54] <balloons> i'm saying deletion are not automated in the sync
[21:54] <balloons> for sanity purposes :-)
[21:54] <balloons> so i have to manually do it
[21:57] <balloons> Noskcaj, k all done and synced
[21:59] <balloons> Noskcaj, you see the diff?
[21:59] <balloons> Diff against target: 	3088 lines (+1098/-1352) 40 files modified
[22:00] <balloons> that's insane!
[22:04] <SergioMeneses> lol
[22:04] <balloons> thanks to everyone who hacked today
[22:04]  * SergioMeneses coffee time
[22:04] <balloons> I'm starved, gotta find some food
[22:04] <balloons> thanks again everyone.. lots of good merges :-)
[22:04] <SergioMeneses> Im going to hack to night
[22:05] <balloons> SergioMeneses, try and keep up with Noskcaj :-) He just got a 3k line merge in
[22:05] <SergioMeneses> balloons, are you kidding me?
[22:05]  * balloons notes this is NOT a line contest. His brain will explode
[22:05] <balloons> SergioMeneses, lol.. please don't send a merge that big
[22:05] <balloons> but yes he did :-)
[22:05] <SergioMeneses> jajaja
[22:06] <SergioMeneses> Audacity is abig test but i dont think it'll be so big
[22:40] <SergioMeneses> balloons, where can i find more information about this new site or project?
[22:41] <SergioMeneses> referent about #community conversation
[22:41] <balloons> SergioMeneses, it's a little thing called discourse
[22:41] <balloons> umm, let me see
[22:42] <balloons> SergioMeneses, test.ubuntu-discourse.org/t/lets-kick-the-tires-aka-the-feedback-thread-read-me-first/
[22:42] <balloons> I really like :-)
[22:43] <SergioMeneses> balloons, perfect, I read more about this to night :) it sounds pretty good - imho
[22:43] <balloons> feel free to join in.. it's another discussion platform but has some niceties
[22:44] <SergioMeneses> it is something like askubuntu but nice
[22:44] <balloons> made by the same folks who made trello
[22:44]  * SergioMeneses runs
[22:56] <SergioMeneses> ok balloons see you later!
[22:56] <SergioMeneses> Im going out from work