=== Ursinha-afk is now known as Ursinha === jpds is now known as Guest78130 === jose- is now known as JoseeAntonioR === pleia2_ is now known as pleia2 === jackson__ is now known as Noskcaj === Guest72344 is now known as forestpiskie === forestpiskie is now known as Guest26089 === ara is now known as Guest80428 [10:00] Morning all === davmor2_ is now known as davmor2 [10:03] morning davmor2 === ubot5` is now known as ubot5 === vrruiz_ is now known as rvr === zequence_ is now known as zequence === 14WAB1TNZ is now known as shadeslayer === Ursinha-afk is now known as Ursinha === Ursinha-afk is now known as Ursinha === Ursinha is now known as Guest40244 === Ursinha_ is now known as Guest51202 === Guest51202 is now known as Ursula === TheLordOfTime is now known as teward === Ursula is now known as Ursinha === fginther` is now known as fginther === Ursinha_ is now known as Ursinha === salem_ is now known as _salem === xnox_ is now known as xnox === _salem is now known as salem_ === balloons is now known as Guest54791 === mapreri is now known as Guest54867 === Guest54867 is now known as mapreri____ === balloons is now known as Guest51231 === mapreri____ is now known as mapreri === PaulW2U is now known as Guest17472 === Ursinha is now known as Guest4888 === Guest4888 is now known as Ursula === Guest17472 is now known as PaulW2U === PaulW2U is now known as Guest62881 === Ursula is now known as Ursinha === salem_ is now known as _salem === Guest62881 is now known as PaulW2U === Guest51231 is now known as balloons === PaulW2U is now known as Guest54842 === _salem is now known as salem_ === TheLordOfTime is now known as teward === salem_ is now known as _salem [19:27] ping elopio. what was the mp you sent my way on friday? I didn't have enough time then to do a full review and now I'm no longer on my main box :-) === pcwhite is now known as PaulW2U [20:04] afternoon Letozaf_ [20:04] balloons, hello === _salem is now known as salem_ [20:08] Letozaf_: how's reminders app tests going? [20:10] balloons, well without autopilot launch it's hard to understand why the tests are not working, the code looks ok but the tests fail [20:10] balloons, with StateNotFoundError [20:10] balloons, so I'm a bit stuck [20:11] Letozaf_: can you paste the full error? And even with updating autopilot launch still isn't working? [20:12] balloons, I have just run a apt-get update and apt-get dist-upgrade to see if there was some change, but I have the same problems [20:12] balloons, let me paste the error [20:12] we can ping the autopilot guys to ask [20:13] balloons: hello :-) [20:13] veebers: :-) Good morning to you [20:13] so, autopilot launch for qt/qml things are working for Letozaf_ or myself.. well at least my main box. I'm on the laptop atm [20:14] *are not working [20:14] Letozaf_: can you paste the error for veebers as well? [20:14] balloons, http://paste.ubuntu.com/6869097/ this is the autopilot tests failing [20:14] balloons, do you also need the autopilot launch error ? [20:15] balloons: interesting. I suspect it hasn't worked on the device for a while, I"m thinking the lack of a desktopfile_hint or something similar to be an issue. [20:15] Letozaf_: yes, explain what's up to veebers as well with autopilot launch [20:15] Letozaf_: yes please [20:16] balloons, veebers if I launch autopilot launch -i Qt qmlscene ../../src/app/qml/reminders.qml [20:16] balloons, veebers I am in the tests/autopilot directory [20:16] balloons, veebers I get: Error: cannot find application '../../src/app/qml/reminders.qml' [20:17] balloons, veebers this also with other apps not only with reminders app [20:17] Letozaf_: right, I'm thinking that the autopilot launch code might need updating for the device [20:17] veebers, this is happening on my desktop [20:17] Letozaf_: can you file a bug with the details, commands you're running and the error please [20:17] veebers, ok [20:18] veebers, do I have to report a bug only for autopilot launch or also for the autopilot run problem ? [20:20] Letozaf_: the autopilot run problem being the StateNotFoundError errors? [20:20] Just the autopilot launch please, the other sounds like an issue with the app or test (at this stage, until proven otherwise :-) ) [20:20] veebers, yes, these tests used to work and it's quite weired they fail now [20:21] veebers, ok fine so I will report only the autopilot launch problem [20:21] Letozaf_: that is odd. When did they start failing? [20:22] veebers, I found out on friday but it was a bit that I wasn't using autopilot waiting for balloons to find a solution to the Evernote autentication issue [20:23] veebers, so it could have been before friday [20:23] sorry, I'm moving through rooms :-) [20:24] * balloons reads backscroll [20:26] so Letozaf_ with the statenotfound errors, did you rebase to trunk? [20:27] for instance, if you run your original branch (that requires authentication) does it run properly? [20:27] balloons, I merged trunk into mine so now it should have all the changes and my tests in [20:28] right.. I would recommend trying your old branch. I *think* something in trunk broke the tests [20:28] trying the old branch would confirm it [20:28] balloons, and if I launch autopilot with everything in, also the cmake stuff is in it fails [20:28] balloons, ok let me try... [20:28] Letozaf_: there was a release a couple of weeks ago, I doubt that may have introduced anything [20:29] veebers, ok, so I will have to find out what the problem is then, thanks [20:29] balloons: fyi, the libautopilot-qt fix we spoke about a week or so back, had to be reverted as it introduced issues . I'll try get an ETA on that for you [20:30] Letozaf_: let us know how you get along, it still possible could be an autopilot issues. If anything there could be improvements on how it reports the error to make it easy to debug === salem_ is now known as _salem [20:32] veebers: ahh.. the fix for andrews issue broke thing eh? I saw the release and revert. And just like Carla, AP launch hasn't worked since.. it's odd === _salem is now known as salem_ [20:33] balloons, my tests run fine before merging trunk into mine [20:33] balloons, no failures [20:34] 21:33:17.925 INFO testresult:43 - OK: reminders_app.tests.test_reminders.TestMainWindow.test_logon_to_Evernote(with mouse) [20:34] Ran 2 tests in 10.889s [20:34] OK [20:35] ok, so that more or less rules out AP for the statenotfound piece. I believe the issue is the qml changed [20:35] have a look at the qml changes you made and see if something is up [20:35] you can look at the diff between your old branch and what you have now as well [20:36] hopefully veebers can figure out the autopilot launch issue [20:36] balloons, Letozaf_: when was the last time autopilot launch worked for you guys? [20:36] balloons, I seem to remember just merging trunk into mine and not changing my tests, but I will double check [20:37] Letozaf_: yes it didn't change the tests during the merge, but instead it changed the underlying qml [20:37] veebers, I think it must have been since friday as I can recall [20:37] so look at the objects in the qml, and the objectnames.. Yes, autopilot launch would likely help here :-( [20:37] balloons, ok let me see if I can find out what the problem is [20:38] balloons, let me first report that bug on autopilot launch [20:40] balloons, veebers bug 1275913 do not have much to write in it though [20:40] bug 1275913 in Autopilot "autopilot launch for qt/qml things is failing to start the apps" [Undecided,New] https://launchpad.net/bugs/1275913 [20:44] balloons: it's this: https://code.launchpad.net/~elopio/ubuntu-clock-app/refactor_timer_tests/+merge/204335 [20:46] Letozaf_, balloons: I suspect the launch issue is something to do with a lack of a desktop_file_hint, you should be able to manually launch your app with testability like so: [20:46] /usr/bin/qmlscene -testability --desktop_file_hint=/usr/share/applications/ [20:48] elopio: ty [20:48] veebers: ohh, that's a good point.. give it a whirl Letozaf_ [20:49] veebers, balloons it works !!! yay [20:49] * balloons facepalms [20:49] * Letozaf_ facepalms too [20:53] balloons, now with autopilot vis I could verify that the objectNames I put are there but I get statenotfound error... I will look into the qml as you said [20:54] Letozaf_: great.. good luck! [20:57] Letozaf_: oh wait, aer you using autopilot launch on desktop or device? [20:57] veebers, on desktop [20:58] Letozaf_: oh, sorry I didn't realise, yeah there seems to be an issue there. I had assumed that it was on device. I'll look into that today [20:58] veebers, ok thanks I feel a bit relieved now :P [20:59] Letozaf_: heh, and I can't even blame it on being Monday morning :-) [20:59] veebers, lol [21:13] balloons, by the way, now that reminder app is on the device with the other apps, is the way of launching autopilot tests changed, or do I still have to use the run_on_ubuntu_touch.sh script ? I mean can I use click packages or not ? [21:15] Letozaf_, balloons: The suggested method (for click tests) as far as I'm aware is, on the host computer run: `phablet-click-test-setup` then `phablet-test-run -v ` [21:15] Letozaf_: but if you're running tests that you're actively developing it may be different [21:16] as I've never heard of run_on_ubuntu_touch.sh :-) [21:16] veebers, yes I think reminders-app is still been actively developed and not sure they have implemented the click tests yet [21:17] veebers, I was asking balloons if he knew this [21:17] Letozaf_: oops sorry [21:19] veebers, no, thanks for the info and for your help [21:19] Letozaf_: nw [21:20] Letozaf_: I haven't landed cmake support for reminders app atm [21:20] so yea, use the script for the device [21:20] I promise this will be nicer soon :-) [21:21] veebers: so I might need to add some things to: http://unity.ubuntu.com/autopilot/tutorial/good_tests.html [21:21] balloons, no problems it's just that maybe I was doing it the "old" way and you had made some changes,never know [21:21] if you can have a look and add any other tips.. or potential pitfalls to that documentation that are not there, it would be helpful [21:22] Letozaf_: no worries. Hopefully very soon doing it that way will be behind us, and it will be easy [22:06] balloons: do you know how can I schedule our next QA lightning talk as part of ubuntu on-air? [22:07] elopio: with me [22:07] and he's on a sprint, so I don't think he'll answer [22:08] JoseeAntonioR: awesome, what information should I give you? [22:08] elopio: https://wiki.ubuntu.com/OnAir/Submissions should have it [22:08] thank you! [22:08] I have some time now, so if you send it in a while I'll make sure it's in the calendar asap :) [22:08] no worries! [22:20] JoseeAntonioR: sent. [22:20] elopio: I just checked, looks good [22:21] I'm scheduling it, I'll be the hangout host that day [22:21] give me a sec so I can give you more detail on it [22:22] JoseeAntonioR: wow, we'll have a real host, that's nice :) [22:23] elopio: is it 30m or 60m? [22:23] JoseeAntonioR: it's 30 minutes. [22:25] elopio: it should be at ubuntuonair.com/calendar now [22:26] now, who will be the people going into the hangout? only you three or more QA members? [22:26] JoseeAntonioR: it should be 2 hours later. [22:26] (public can comment at #ubuntu-on-air) [22:27] then that's 22:30 UTC [22:27] probably, I suck at clocks. Sorry about that. [22:27] no worries :) [22:28] elopio: now, who will be joining the video call itself? [22:28] JoseeAntonioR: I'll give you the emails of the canonical team in private. Half of them will probably be sleeping at that time, so it's likely we'll have some free seats for the community. [22:29] oh, community is at #ubuntu-on-air on this network [22:29] or well, people in general [22:29] if any of them want to join to speak during the session, like, something that will be recorded on video, they can join for sure [22:30] we basically just want people who will be doing actual speaking on the video [22:37] JoseeAntonioR: well, probably not everybody from the list I gave you will talk, because there's no time. === salem_ is now known as _salem [22:38] but we do this as part of our working from home adequation, we try to see each other faces as much as we can :) [22:38] elopio: erm, well, see PM [22:38] so if it's ok to have them on the call, that would be great. They will behave, I promise. === knome_ is now known as knome