[14:04] <pitti> fginther: hey Francis, how are you?
[14:05] <pitti> fginther: so on the phone I dpkg-deb -x'ed ubuntu-ui-toolkit-autopilot and set PYTHONPATH accordingly, to run autopilot tests
[14:05] <fginther> pitti, I think I'm well.
[14:05] <pitti> PYTHONPATH=ubuntu-calculator-app/tests/autopilot/:ap/usr/lib/python3/dist-packages/ autopilot3 run -v ubuntu_calculator_app
[14:06] <pitti> but I get tons of errors like "Introspect error on :1.269:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this sender from sending this message to this recipient, 0 matched rules; type="method_call", sender=":1.271" (uid=32011 pid=4685 comm="/usr/bin/python3 /usr/bin/autopilot3 run -v ubuntu")
[14:06] <pitti> interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply="0" destination=":1.269" (uid=32011 pid=4637 comm="/usr/lib/i386-linux-gnu/qt5/bin/qmlscene ubuntu-ca")"
[14:06] <pitti> fginther: i. e. some apparmor limitation; do you happen to know anything about that?
[14:06] <balloons> pitti, you need to add the click.rules for autopilot
[14:06] <pitti> hey balloons
[14:06] <balloons> hey pitti :-)
[14:06] <balloons> aa-clickhook -f --include=/usr/share/autopilot-touch/apparmor/click.rules
[14:06] <pitti> balloons: how do I do that?
[14:07] <balloons> there is a script that does the same thing; phablet-config autopilot --dbus-probe enable
[14:07] <balloons> should only need to include those once per device
[14:07] <fginther> balloons, thanks for that. I was trying to find where that 'dbug-probe' was done
[14:07] <pitti> balloons: aah, thanks
[14:07] <balloons> pitti, timing is excellent as I was wondering how things where going with autopkg
[14:08] <pitti> balloons: so today I learned about the intricacies of ubuntu-app-launch, how to run apps and tests on the phone from the command line, and how to use the emulator
[14:09] <pitti> balloons: so indeed nearly *everything* is highly ubuntu specific about that :)
[14:09] <balloons> mmm.. yes that's true
[14:10] <pitti> so generic .click support would require some work in adt-run, but I wondered if that would actually make sense
[14:10] <pitti> as we mostly (only?) have graphical apps with autopilot so far
[14:11] <pitti> but well, so far I still have rather lots of trouble actually running our AP tests on the device (or the emulator)
[14:11] <pitti> it's effing slow and buggy, I suppose I'm still missing some bits
[14:12] <pitti> balloons: so, I'm still in the "learning" phase, I'm afraid
[14:13] <pitti> _usr_share_android_emulator_out_host_linux-x86_bin_emulator-x86.1000.crash
[14:13] <pitti> and I suppose crashing the emulator doesn't help much either :)
[14:13] <balloons> pitti, still having trouble running tests eh?
[14:14] <balloons> I've not messed all that much with the emulator.. I've only played with it; not tried to do serious runs with it. I did that a little with the armhf one, but not the x86 one
[14:14] <pitti> the armhf one still didn't boot after 15 mins, so I retried with the x86 one
[14:15] <pitti> that boots, and got into running the tests (although they hang a lot), and then it crashed the emulator
[14:15] <balloons> pitti, yea.. it takes a while.. no reason to use it now that we have x86
[14:15]  * pitti tries again on mako with the above apparmor click thing
[14:16] <pitti> balloons: is that a per-boot thing, or will the effect stay around?
[14:17] <balloons> pitti, should just need to do it once. Unless you reflash, shouldn't need to re-apply it
[14:17] <balloons> or unless you change the rules ;-)
[14:17] <pitti> ah, thanks
[14:22] <balloons> might be useful to try and sync up again.. UOS has me multitasking today and tomorrow still
[14:23] <pitti> balloons: ok, better; 33 tests, 8 failures, 25 successes
[14:23] <pitti> testtools.matchers._impl.MismatchError: After 10.0 seconds test failed: '1.000000001' != '1,000000001'
[14:23] <pitti> locales, people, locales!
[14:23] <balloons> pitti, so you are running what tests and on your device right?
[14:23] <pitti> balloons: right, calculator's
[14:23] <balloons> ohh calculator tests :-)
[14:24] <balloons> nice.. yea, that's a locale bug.. file it against calc if you would.. we should fix that
[14:24] <pitti> balloons: right, so starting from a virgin device I copied the source tree, downloaded and unpacked the deb of ubuntu-ui-toolkit-autopilot, and ran the tests from the source tree against the installed click
[14:25] <pitti> balloons: I think that's pretty much the scenario that we want
[14:25] <balloons> pitti, sounds sane enough
[14:25] <balloons> you would push depends too, but we're staying simple for now
[14:26] <balloons> well the toolkit indeed is a depends :-)
[14:28] <pitti> right
[19:34] <alesage> balloons, in your experience are there test plans which require the tester to grep files, etc.?
[19:35] <balloons> alesage, mm.. the only example I can think of was verifying configs / status of things after installation
[19:36] <elfy> there are in manual tests
[19:36] <elfy> at least one that I can think of offhand
[19:36] <alesage> elfy, what's that example? also thx balloons
[19:37] <elfy> upgrade tests "grep Prompt= /etc/update-manager/release-upgrades"
[19:38] <alesage> elfy thanks for that
[19:38] <elfy> welcome :)
[19:38] <elfy> keeper of manual testcases apparently lol
[19:38] <alesage> elfy, now I know who to ask ;)
[19:39] <elfy> forestpiskie is the best one :D
[19:47] <balloons> elfy, ;p
[19:48] <elfy> bit unfair perhaps - not many will know who forestpiskie is :D
[19:48] <elfy> at least not without years old knowledge or a whois
[22:28] <phillw> balloons: is / are there any good sessions for QA from today?
[23:38] <elopio> ping balloons: are you still here? re: temporary home.