=== slickyma1ter is now known as slickymaster === _salem is now known as salem_ === salem_ is now known as _salem [05:28] Good morning === plars_ is now known as plars [07:00] good morning [07:04] morning DanChapman [07:04] morning elfy :-) how are you? [07:04] awake - just :p [07:18] elfy, yeah same here. got ill children in this house :-( now just got to look forward to catching it! [07:19] nice [07:19] just hope you had chickenpox when they get that ... [08:12] jibel: I have the "wait 20 s after boot and check runlevel" patch locally applied on wazn, first two tests succeeded now; I restarted the other ones [08:12] * pitti commits [08:17] pitti, I think we need the same hack in UpgradeTestBackendSSH in upgrade() [08:17] jibel: why? that just calls .start(), doesn't it? [08:18] pitti, because it calls start() then immediately calls upgrade() and capture the list of services before the upgrade [08:18] so we may miss some or have too much [08:18] jibel: oh, you mean we need to move super().upgrade() after .start() in Qemu.py, too? [08:19] jibel: you already did that for LXC (thanks) [08:19] pitti, that too [08:19] jibel: ok, then I don't understand what you mean [08:19] pitti, but I meant that the initial list of services is captured too quickly after start() [08:21] jibel: what I meant was http://bazaar.launchpad.net/~auto-upgrade-testing-dev/auto-upgrade-testing/trunk/revision/116 [08:21] pitti, in LXC.py we call upgrade() which calls start() and super().upgrade() [08:21] jibel: which does to Qemu what you did to LXC in r111 [08:21] but in super().upgrade() we don't wait for the system to settle [08:21] jibel: no, but start() already does? [08:22] jibel: but what couldn't hurt is to do the same sleep/runlevel check in Qemu's start() as well; AFAIK that just tries whether /bin/true works [08:22] pitti, ah right, sorry [08:26] next run should be green again [08:33] meh! [08:33] jibel: seems I need to blacklist kdm, precise -> trusty kubuntu switched from kdm to lightdm as it seems [08:33] jibel: I blacklisted plymouth this morning, as that's really just transient [08:33] jibel: anyway, I'll get it to green today, promised :) [09:59] jibel: ok, much better already: http://d-jenkins.ubuntu-ci:8080/view/Upgrade/ [10:00] now, why isn't whoopsie starting for quantal -> saucy.. [10:01] that starts to smell like an actual bug now === Ursinha is now known as Ursinha-afk [11:04] Morning all === _salem is now known as salem_ === Ursinha-afk is now known as Ursinha === bfiller_afk is now known as bfiller [14:36] ty DanChapman for merging those autopilot requests :-) [14:40] balloons: np :-) how's it going? ready for a busy few days? [14:41] DanChapman, never completely ready, but always excited and happy to talk [14:41] :-D === salem_ is now known as _salem === bfiller is now known as bfiller_afk === _salem is now known as salem_ === bfiller_afk is now known as bfiller [18:32] veebers, thomi: have some time to talk about the folder hierarchy after I deprecate the word emulators? [18:33] elopio: gimme 2 minutes? [18:33] Then I will [18:33] ok [18:37] elopio: have time now [18:44] thomi: so, this is the current structure: [18:44] tests.autopilot.ubuntuuitoolkit.tests [18:44] tests.autopilot.ubuntuuitoolkit.emulators [18:44] no, scratch that. [18:44] it's not namespaces, it's directories. [18:45] tests/autopilot/ubuntuuitoolkit/tests [18:45] tests/autopilot/ubuntuuitoolkit/emulators [18:45] right [18:45] so... can we drop the 'tests/autopilot/' prefix? [18:45] I mean, it's not important to the conversaion here, they could be *anywhere* in the source tree right? [18:46] I can't just put what's currently in tests/autopilot/ubuntuuitoolkit/emulators [18:46] in tests/autopilot/ubuntuuitoolkit/__init__.py, because at some point we might want to provide actual python toolkit APIs on ubuntuitoolkit. [18:46] thomi: yes, we could drop the prefix. [18:47] what I propose is to move ubuntuuitoolkit.emulators to ubuntuuitoolkit.autopilot [18:47] and ubuntuuitoolit.tests to ubuntuuitoolkit.autopilot.tests [18:47] yeah - that sounds sensible to me [18:48] now, we need to fix the prefix because it would be horrible tests/autopilot/ubuntuuitoolkit/autopilot/tests [18:48] :) [18:48] I don't really know how to make it better. [18:48] if we just drop the first tests/autopilot [18:49] we separate them from tests/qml [18:49] it was somewhat nice to have them together. [18:49] elopio: so.. I'm not convinced that you're ever going to ship an actual toolkit in the python package [18:49] but, maybe we should also drop tests/qml, and put them next to the components. [18:50] thomi: well, even if we don't release the toolkit in python, I think it's not right to assume that the ubuntuuitoolkit namespace is all ours. [18:51] elopio: not forever, but it is today. Ideally you'd rename that python package, but that's a lot more work then we want to do right now [18:51] thomi: it would be the same amount of effor to move the helpers to ubuntuuitoolkit.__init__ than to move them to ubuntuuitoolkit.autopilot [18:52] elopio: yes, but your package and paths wouldn't be so ugly [18:52] thomi: droping the tests/autopilot prefix to the path is a bzr move + a cmake change. [18:53] no big deal there either. [18:53] right [18:53] something fancier than that could be a problem. [18:53] In general, I think it's a python anti-pattern to have deeply nested namespaces [18:53] so I prefer the flatter solution [18:53] and yes, I realise that autopilot does this, but we're fixing that :) [18:54] thomi: flat would be something like calling the package ubuntuuitoolkit_autopilot ? [18:54] elopio: no, like [18:54] custom proxy classes and helpers are in 'ubuntuuitoolkit'. tests are in 'ubuntuuitoolkit.tests' [18:55] if you ever release the python SDK, release it under 'ubuntusdk' [18:55] or some other name [18:55] it really won't belong in the same package I don't think [18:55] ok, I agree that a namespace hierarchy is not pythonic. [18:56] however, putting the autopilot helpers in ubuntuuitoolkit is not clear. [18:56] we need to mention somewhere that they are autopilot helpers. [18:56] elopio: right - ideally you'd rename that top-level package [18:56] 'ubuntu_sdk_helpers' or somesuch [18:56] thomi: what name would you propose? [18:56] but anny name change is going to be painful [18:57] although... maybe not so bad [18:57] with the ci-train [18:57] ubuntu_sdk_testing, I like something like that. [18:57] yeah [18:57] 'ubuntu_sdk_testing.tests' :P [18:57] I suppose that's not too bad [18:58] ubuntusdk_testing.user_accpentance_tests [18:58] ubuntusdk_testing.helper_tests [18:58] I actually would like something like that. [18:58] then we can run first the helper tests, and if they pass, we run the uat. [19:54] good evening [20:38] balloons, hi [20:38] letozaf, hello [20:39] balloons, I was trying to figure out why reminders app does not start, do you know how to fix this: No token set. Cannot execute job. ( FetchUsernameJob ) [20:39] balloons, I think that reminders app does not start due to a token problem [20:39] balloons, but do not know how to fix this [20:40] balloons, well if you got time obviously as I think you're quite busy with vUDS [20:47] letozaf, I agree with all those things.. but I would think the app would still start [20:48] it starts when run from the command line [20:48] so clearly it should work; the __init__.py launch is not correct, that's my guess as we discussed [20:49] balloons, yes I think you're right [20:49] balloons, I will have to see if I find out what's wrong in the __init__.py [20:50] balloons, but how do I know if something has change in the way reminders app get's launched ? [20:51] balloons, I mean the tests used to work a long time ago and I do not know about the changes, if changes have been made obviously [20:51] letozaf, yes the depcrecated qmlscene which broke things for us [20:53] letozaf, well let's look together [20:53] give me a moment :-) [20:53] balloons, ok [20:58] letozaf, so launch_test_local won't work anymore [20:59] balloons, no and it tries to launch /usr/lib/x86_64-linux-gnu/qt5/bin/qmlscene', '-testability', '-I', '/home/letozaf/autopilot-tests/new-reminders-app-tests/builddir/src/plugin', '../../src/app/qml/reminders.qml', '--desktop_file_hint=/home/phablet/reminders/reminders-app.desktop'] [21:00] balloons, :O [21:00] so for the moment, let's try launch_test_installed [21:00] mmm [21:00] also not gonna work [21:02] balloons, I get http://paste.ubuntu.com/7075741/ [21:02] letozaf, ok let me send you the hackery to launch [21:03] but it needs to be fixed to have it work without installation [21:04] balloons, you mean without reminders.app being installed on my desktop ? [21:05] letozaf, merge lp:~nskaggs/reminders-app/fix-ap-launch [21:07] letozaf, so that forces launching via the installed version. It will get you running for now [21:27] letozaf, did it work? :-) === dkessel_ is now known as dkessel === dkessel_ is now known as dkessel