[14:20] <elopio> good morning team.
[14:25] <balloons> morning!
[15:49] <elopio> fgimenez: on your bluetooth branch, you have to add the config option to ubuntu_sanity_tests/config.py
[15:51] <elopio> fgimenez: also, the BluetoothPage class was upstreamed to system settings.
[15:53] <elopio> and ensure_system_settings_closed can be moved to system_settings.py and used in the sim pin test.
[15:55] <fgimenez> elopio: ack, on it
[16:15] <elopio> rhuddie: can I help you with the camera test?
[16:18] <rhuddie> elopio, hey. one thing that i found is that the camera helper to close the bottom edge doesn't seem to work very well.
[16:18] <rhuddie> elopio, i changed so it works in the middle of the screen rather than at 0 x co-ord.
[16:19] <rhuddie> but i'm not sure how it works in the other tests if it fails for me
[16:19] <elopio> rhuddie: I don't know. Might not be used in their tests.
[16:20] <rhuddie> elopio, yes, could be
[16:21] <elopio> rhuddie: what's the name of the method?
[16:22] <rhuddie> elopio, _drag_to_close: http://bazaar.launchpad.net/~phablet-team/camera-app/trunk/view/head:/tests/autopilot/camera_app/emulators/panel.py#L52
[16:23] <elopio> rhuddie: it is used in four times.
[16:23] <rhuddie> elopio, if you see the _drag_to_open method works in the x centre, but the close one doesn't
[16:24] <elopio> rhuddie: ah, it is used four times, but at the end of the test.
[16:24] <elopio> it has no assertions afterwards.
[16:24] <rhuddie> elopio, ah, now it makes sense
[16:24] <elopio> rhuddie: you can report a bug to the camera.
[16:24] <rhuddie> elopio, yep will do
[16:25] <elopio> it's unlikely they'll fix it for us, but it will bring some visibility to what we are doing.
[16:25] <rhuddie> elopio, i'll propose an mp, as my fix seems to work fine
[16:25] <elopio> rhuddie: ok, but ideally your fix has a test with an assertion after the close, so it never breaks.
[16:26] <rhuddie> elopio, well, how about changing the existing 4 instances to assert it is closed afterwards?
[16:26] <elopio> rhuddie: that works too.
[16:27] <elopio> rhuddie: those tests are ugly, you are warned.
[16:27] <elopio> rhuddie: also it would work to add a "wait for closed" in the close method.
[16:27] <fgimenez> elopio: it seems that the upstreamed BluetoothPage is missing the required get_disconnected_list method
[16:28] <rhuddie> elopio, yes, that would be neater solution
[16:29] <elopio> fgimenez: it's called get_disconnected_devices.
[16:29] <fgimenez> elopio: ok thanks, where can i check the code?
[16:31] <fgimenez> elopio: the upstreamed BluetoohPage class, i mean
[16:35] <elopio> fgimenez: that's lp:ubuntu-system-settings
[16:36] <elopio> in the folder tests/autopilot.
[20:27] <elopio> barry: is there a way to call system-image-dbus with --no-reboot?
[20:28] <Letozaf_> balloons, :)
[20:28] <barry> elopio: no, unfortunately there isn't.  in si 3.0 we can set a configuration file option to basically not do a reboot when the update is applied, and in si 3.0 the cli has a --no-reboot flag.  but si 3.0 hasn't been released to vivid
[20:29] <elopio> barry: I'm using system-image-cli --no-reboot on vivid.
[20:30] <barry> elopio: ah, sorry.  si 3.0 renamed --no-reboot to --no-apply.  you're right
[20:30] <barry> elopio: and actually, i think we can hack the config file to not reboot
[20:30] <elopio> barry: that sounds good.
[20:31] <elopio> barry: I got this: http://paste.ubuntu.com/10519178/
[20:31] <elopio> any idea why is the file not there?
[20:31] <barry> elopio: it should be acceptable not to have a blacklist keyring
[20:32] <Letozaf_> balloons, should we chat here about the filemanager app failing tests ?
[20:32] <barry> elopio: but if a blacklist keyring was found and downloaded but then it disappeared, that would be a problem.  i don't know why that would happen in this case
[20:33] <elopio> barry: yes, on the log I see this:
[20:33] <elopio> https://system-image.ubuntu.com/gpg/blacklist.tar.xz -> /var/lib/system-image/keyring.tar.xz
[20:34] <elopio> sorry, this
[20:34] <elopio> https://system-image.ubuntu.com/gpg/blacklist.tar.xz.asc -> /var/lib/system-image/keyring.tar.xz.asc
[20:34] <barry> elopio: can you pastebin the full log?
[20:35] <elopio> barry: http://paste.ubuntu.com/10519237/
[20:35] <elopio> I re-run it, and now it's doing the upgrrade.
[20:36] <barry> elopio: weird!  nothing obvious from the log file
[20:39] <elopio> barry: veebers: this one succeeded :)
[20:39] <elopio> http://paste.ubuntu.com/10519265/
[20:41] <barry> :-o
[20:41] <veebers> elopio: awesome ^_^
[20:41] <balloons> Letozaf_, did you have anything else to chat about? I was concerned about calendar failing in trunk
[20:41] <balloons> but yes, shoot
[20:42] <Letozaf_> balloons, well if you want I can come back tomorrow or when you have more time, it's not urgent I suppose!
[20:42] <balloons> Letozaf_, no time like the present
[20:42] <balloons> :-)
[20:42] <Letozaf_> balloons, :) ok so I will shoot
[20:43] <Letozaf_> balloons, I took a look at the filemanager test failures.
[20:43] <Letozaf_> I am unable to reproduce the failures on my desktop, but a lot of tests
[20:43] <Letozaf_> are failing with a StateNotFoundError on bject not found with name
[20:43] <Letozaf_> 'ActionSelectionPopover' and properties {'objectName':
[20:43] <Letozaf_> 'fileActionsPopover'}, but that object exists an also the objectName is
[20:43] <Letozaf_> correct
[20:44] <Letozaf_> balloons, It could be a timing issue, but the get_action_selection_popover() is in
[20:44] <Letozaf_>  _main.py of ubuntuuitoolkit, so not quite sure if it should be fixed there.
[20:44] <Letozaf_> https://dl.dropboxusercontent.com/u/10083981/Ubuntu%20phone/Actionspopover.png
[20:45] <Letozaf_> balloons, and I created a mp with no changes, just to run filemanager tests on Jenkins...
[20:45] <Letozaf_> Well, the tests passed :O.
[20:46] <Letozaf_> balloons, so do not exactly know why they fail here: http://ci.ubuntu.com/smokeng/vivid/touch/mako/117:20150301.1:20150210/12398/filemanager/
[20:46] <Letozaf_> balloons, any idea ?
[20:47] <Letozaf_> balloons, ah! the mp that is not failing: https://code.launchpad.net/~carla-sella/ubuntu-filemanager-app/just-for-test
[20:52]  * balloons reads
[20:52] <balloons> hehe
[20:52] <balloons> I rebuilt that just for another run
[20:52] <balloons> so where is the mp that is failing?
[20:53] <Letozaf_> balloons, the tests are failing in  http://ci.ubuntu.com/smokeng/vivid/touch/mako/117:20150301.1:20150210/12398/filemanager/
[20:53] <elfy> evening balloons Letozaf_
[20:53] <balloons> evening elfy
[20:53] <balloons> ohh, on the dashboard
[20:53] <Letozaf_> elfy, evening to you
[20:54] <balloons> Letozaf_, so right, no worries on jenkins
[20:54] <elfy> balloons: it got delivered to my mum today - picking it up tomorrow :)
[20:54] <balloons> elfy, excellent. enjoy yourself now
[20:54] <elfy> eventually I will ;)
[20:59] <balloons> Letozaf_, so if you want to reproduce the results on the CI dashboard you'll need to follow some directions.
[20:59] <balloons> ci is actually working on it right now
[21:00] <Letozaf_> balloons, ok so should I leave it to them?
[21:01] <balloons> Letozaf_, no lol, I meant they are working on proper directions for you to reproduce results from the dashboard locally
[21:01] <Letozaf_> balloons, oooh! thats even better :P
[21:01] <balloons> in the interim however, do you know about looking at subunit files using trv?
[21:01] <balloons> Letozaf_, https://code.launchpad.net/~canonical-ci-engineering/ubuntu-test-cases/testing-docs/+merge/251507
[21:02] <balloons> Letozaf_, so save http://jenkins.qa.ubuntu.com/job/vivid-touch-mako-smoke-daily/349/artifact/clientlogs/filemanager/test_results.subunit/*view*/
[21:02] <Letozaf_> balloons, I remember looking at a video time ago about trv but do not remember...
[21:03]  * Letozaf_ is reading 
[21:06] <balloons> you can grab trv from https://launchpad.net/~thomir/+archive/ubuntu/trv/+build/6626488
[21:06] <elfy> balloons: is https://wiki.ubuntu.com/Touch the go to page?
[21:06] <Letozaf_> balloons, yes I found it and also this: https://www.youtube.com/watch?v=jkLtbmQxXYc
[21:07] <balloons> elfy, that's an excellent place to begin yes
[21:07] <elfy> ta
[21:09] <balloons> Letozaf_, so looking at the screenshots it's clear the popover didn't appear
[21:10] <Letozaf_> balloons, yes I see :) nice this trv
[21:11] <balloons> Letozaf_, so I think you are correct in thinking it's a timing thing
[21:11] <Letozaf_> balloons, yes looks like, I will try to find a solution
[21:13] <balloons> so Letozaf_ once you think you have a solution, feel free to follow the instructions in: http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/view/head:/README-cli.rst. But it means wiping your device completely
[21:13] <Letozaf_> balloons, :O
[21:13] <balloons> I would mess around on the desktop and merge it in jenkins before worrying about that part :-)
[21:13] <Letozaf_> balloons, well I still have my Nexus4, can wipe that :)
[21:14] <Letozaf_> balloons, sure
[21:14] <balloons> right
[21:15] <balloons> Letozaf_, a little sneak preview: http://people.canonical.com/~nskaggs/test-index.html
[21:17] <Letozaf_> balloons, woow!!! :)