[13:41] <nik90> balloons: hey, can you ping me later when you are free..I am having trouble running clock app autopilot tests on my vivid laptop (log http://paste.ubuntu.com/10596507/ )
[13:49] <balloons> ohh theres a queue in here :-)
[13:49] <balloons> morning all!
[14:04] <balloons> rpadovani, I re-ran it. It returned nothing to jenkins so it's hard to say what went wrong
[14:04] <rpadovani> ty!
[14:06] <balloons> nik90, so this log.. how do you generate it?
[14:06] <balloons> ohh is this a fresh checkout? if it's on the desktop, it's not finding the binary
[14:07] <balloons> we should put the python in to find the binary rather than require it be in a specific location.. there's a cmake parser, which does work to do this
[14:08] <nik90> balloons: yeah is on a fresh vivid install on the desktop
[14:09] <nik90> what do you mean put python in to find the binary?
[14:13] <balloons> nik90, heh, I'm rambling aloud. Ok, so to fix your issue make sure you build as instructed in the README. Unless someone has changed something the tests expect the binary in that specific folder
[14:14] <balloons> there is some python code we can add to the testsuite that would read the cmake build file instead of requiring a specific folder for the binary. So during test startup, it reads the cmake build file and looks for the binary that way, instead of requiring a fixed relative path
[14:15] <nik90> balloons: omg, I am an idiot, I forgot to build the binary...(QtC usually does that for me)
[14:15] <balloons> nik90, right :-) not building it also causes that, heh
[14:21] <nik90> balloons: so after building the binary, and runnig autopilot run test_name works... however i tried using autopilot3 but it fails and complains something about  DisplayConnectionError http://paste.ubuntu.com/10609916/
[14:22] <nik90> I figured if I could use autopilot3 it would help me use autopilot3-sandbox-run and the other cool features
[14:22] <nik90> I see the clock app show up and then get closed almost immediately while using autopilot3
[14:25] <balloons> nik90, autopilot3 causes you problems.. interesting
[14:25] <balloons> trusty ofc, and what version of autopilot3?
[14:26] <nik90> balloons: no no this is on vivid
[14:26] <balloons> oh nice
[14:26] <nik90> balloons: version info http://paste.ubuntu.com/10609963/
[14:26] <balloons> just your normal desktop?
[14:27] <nik90> yup
[14:27] <nik90> (my old laptop)
[14:27] <nik90> running vivid daily build 1386
[14:28] <balloons> well I guess let me try as well locally here. However, autopilot2 works fine for you
[14:28] <balloons> ot
[14:28] <nik90> yeah autopilot works fine, so I guess I can use it for now
[14:28] <balloons> I can't imagine the backend code is substantially different, but we can look
[14:29] <nik90> I have been asked to improve the clock app's AP status..so I will be adding back the functional tests for editing alarms, etc that currently only exist in the QML test suite
[14:30] <balloons> nik90, ohh.. what's clock look like on the dashboard anyway?
[14:31] <nik90> balloons: every AP test fails :/ due to the location prompt
[14:31] <nik90> so I cannot release a new click to the store as a resutl
[14:32] <balloons> nik90, ahh well I guess we should start by fixing that eh?
[14:33] <nik90> balloons: I can't since it requires upstream helpers to be added in the trust-store, let me grab the MP we have currently that requires upstream fix
[14:33] <balloons> and there is nothing wrong with keeping your AP test suite smaller.
[14:33] <balloons> nik90, we can bundle the helpers locally for now and transition later
[14:33] <nik90> https://code.launchpad.net/~brendan-donegan/ubuntu-clock-app/disable_location_prompt/+merge/242682
[14:34] <nik90> check out the last reply from iahmad
[14:34] <balloons> nik90, right so that's all landed.. it means we can write helpers now and bundle them locally. And ofc upstream them and transition after
[14:34] <balloons> make sense?
[14:35] <nik90> yes
[14:38] <balloons> nik90, I get the same error as you, nice
[14:39] <nik90> ooh :P
[14:39] <balloons> and indeed, autopilot works..investigation and bug filing time
[14:39] <nik90> balloons: just for clock app? Since otherwise this might have been spotted earlier on
[14:41] <balloons> nik90, no it's for everything.. Something must have broken it recently
[14:41] <balloons> I have a small update I can do so I'm doing that first
[14:41] <balloons> are you fully up to date?
[14:42] <nik90> yeah I am fully up to date
[14:42] <balloons> yea nothing in here will change anything so I suspected as much
[14:43] <balloons> let me try and pinpoint what broke it
[14:43] <balloons> rpadovani, looks like you got a valid run that time: http://91.189.93.70:8080/job/generic-mediumtests-utopic/2357/testReport/junit/ubuntu_calculator_app.tests.test_main/MainTestCase/test_sin/
[14:43] <balloons> at least a log
[14:58] <balloons> nik90, so carry on with autopilot2 for now.. This should be fun to track down for someone else :-)
[15:00] <nik90> balloons: yes, I have started writing some new tests. I haven't had any success with running AP tests on the phone (using all the methods that I could find), so the location-prompt thing will have to wait for now.
[15:31] <paulliu> hi. If I add some cout/cerr in platform-api. How do I print those out when using autopilot3?
[15:33] <balloons> nik90, you don't have a spare phone just for testing do you?
[15:53] <nik90> balloons: I use my S4 Android as my primary phone, and the N4 just for testing and developing for UT. I tried the script popey and also adt-run on devel-proposed as well
[15:55] <balloons> nik90, right. I was going to say grabbing devel-proposed image with vivid should let you use adt easily enough. It should just work
[15:56] <balloons> alternatively you can grab devel-proposed, make it r/w and install autopilot packages again. Then copy the tests and run them just like you do on the desktop. The downside of that is you'll have to occassionally re-flash the phone to update it
[15:56] <nik90> balloons: For instance, when I tried adt-run on the music app AP tests, they all didnt get past the welcome wizard. I am not sure why.
[15:56] <nik90> hmm ok I will do that
[15:59] <balloons> nik90, if you are interested in cloning what happens on the dashboard, this is how CI does it. Essentially they do what I said as the latter option: http://ubuntu-test-cases-touch.readthedocs.org/en/latest/
[15:59] <balloons> so if you do that, you may as well simply use there script
[16:00] <balloons> nik90, if they didn't get past the welcome wizard that might just be an issue with the tests.
[16:05] <nik90> ok
[16:07] <nik90> balloons: wow that docs looks detailed and easy to follow, thnx. I will give that a go
[16:07]  * ahayzen hides and pretends the tests are working perfectly :)
[16:08] <nik90> ahayzen: lol
[16:08] <nik90> ahayzen: I just took another app to see if something was wrong with my testing environment
[16:08] <ahayzen> haha
[16:08] <balloons> nik90, good let me know.. CI is actively documenting that atm, I've been wanting to make sure it's actually usable by someone like yourself
[16:13] <nik90> will do