[01:07] robru, By chance are you still around? [01:31] tedg, hey, just got back. what's up? [01:33] robru, he wants a silo for a ubuntu-app-launch fix [01:34] tedg, ok you got silo 2 [01:34] i just hassled tedg on IM :) [01:35] Heh [01:35] kenvandine, hey hey. how was malta? such a shame we couldn't connect [01:35] good, yeah missed you guys [01:35] robru, Thanks! [01:36] tedg, you are welcome! [01:36] i did get to hang out with seb, larsu and dsert though [01:36] and of course tedg :) [01:36] kenvandine, i wish I could go to these things for both weeks [01:36] tedg, that was some damn good carbonara! [01:36] robru, You say that the first couple times ;-) [01:36] kenvandine, It was. [01:37] ha... i do not miss the 2 week trips, not at all :) [01:37] tedg, thanks for the fix! [01:37] kenvandine, The L'Artist restaurant was the best there though. [01:37] i didn't get to try that place [01:37] * kenvandine goes back to writing API docs for bacon2d :) [01:38] which is not nearly as much fun as game hacking :) [01:38] Oh, ogra uploaded a fix... [01:39] ah... distro patch? :) [01:40] Yeah... [01:41] when? [01:41] i don't see a change mail for it [01:42] kenvandine, https://launchpad.net/ubuntu/+source/ubuntu-app-launch [01:42] kenvandine, Not for this, for a packaging issue. [01:42] ah [01:44] tedg, oh right, you have to sync distro back to trunk there. [01:44] On it. [01:45] cool [01:46] Who can review this? https://code.launchpad.net/~ted/qa-regression-testing/ubuntu-app-launch/+merge/222115 [01:47] tedg, these people? ;-) http://bazaar.launchpad.net/~ubuntu-bugcontrol/qa-regression-testing/master/changes [01:47] Ewww, security people :-) [01:59] Hmm, clock isn't starting for me now. "(process:3727): GLib-GIO-ERROR **: No GSettings schemas are installed on the system" [02:10] === trainguard: IMAGE 66 building (started: 20140605 02:10) === [02:12] Uhg, missed 66 I guess. [02:14] yeap [02:28] camako, hey [02:29] robru, hey so is there anything I need to do at this point? [02:32] camako, haha we're talking in two channels, bah ;-) [02:33] tedg, http://ci.ubuntu.com/smokeng/utopic/touch/mako/65:20140604.1:20140530/8401/music_app/ is this related to UAL? [02:36] robru, I don't think so. Noticing that clock and terminal are also broken. [02:43] robru, Okay, nope, I think at least terminal is mine. [02:43] tedg, ah [02:46] robru, Rebuilding that silo with the fix. [02:46] tedg, cool [03:06] ugh [03:06] robru: something's wrong still [03:06] robru: I'm testing 65 at home with *just* music_app and it's working [03:06] unfortunately... I really hate that stupid song it plays [03:06] plars, what do you mean by "just music_app"? [03:07] plars, I think you can mute the phone while the test runs ;-) [03:07] robru: not running all the tests, just that one since it seems to fail everywhere [03:07] plars, oh, so you're suggesting that this is an infrastructure problem? [03:07] robru: that would involve getting out of the chair :) [03:07] robru: no [03:07] robru: but it could be like the other problems we've seen over the past couple of days where a package is messing things up [03:09] plars, right I see. [03:09] plars, anything I can do to help with that? [03:13] robru: going to try a few things, but I'm exhausted right now [03:13] I'll stay up as long as I can and try to sort it out [03:14] plars, alright, let me know if there's a specific test you want me to run on my mako or whatever, i've got a couple spare cycles. [03:14] robru: the changes list for 65 was enormous [03:15] plars, yeah, sorry abou that. are you bisecting it? [03:15] robru: no way [03:15] robru: I'd be up for the next few days [03:15] plars, I blame UAL for everything. revert that one first ;-) [03:15] :) [03:22] I think a couple of the apps issues were based on not having all the env vars set. [03:23] They were falling back to running as legacy apps, which doesn't set all the confinement variables. [03:33] robru, I didn't change the tracepoints yet, was letting the application startup guys get off the ground before throwing them a twist. [03:33] tedg, ah sorry, didn't realize those were *all* tracepoints, I was just concerned by the length of that list [03:35] tedg, thanks for clarifying [03:35] robru, almost all, most are inert, but going to fix them anyway. Stop the next person from getting confused. [03:35] tedg: does https://jenkins.qa.ubuntu.com/job/utopic-touch-flo-smoke-daily/144/artifact/clientlogs/calendar_app/_usr_lib_python3_dist-packages_autopilot_run.py.32011.crash/*view*/ mean anything to you? [03:35] tedg: specifically: DuplicateSignature: upstart-app-launch-invalid-appid [03:35] the apps that are crashing seem to all have this [03:37] plars, It's basically a report saying that it can't find the app. [03:39] tedg: and http://paste.ubuntu.com/7592099/ [03:40] tedg: is that the issue you were describing where not all the environment variables are set? [03:41] plars, Hmm, not sure on that one. [03:41] plars, That may just be from the app not starting though. [03:41] robru: hmm, I think I'm able to reproduce this now at home [03:41] plars, It seems like that error is in autopilot, so my guess would be that it can't find widgets because there isn't a window. [03:42] plars, oh really? [03:42] wait, maybe not, too early [03:42] tedg, plars: I overheard (incompletely) that there are some issues with upstart, autopilot and applications. I may be of service if it has something to do with autopilot [03:42] I thought it was farther along [03:43] veebers, Not sure it's an autopilot issue specifically, but here's the trace: http://paste.ubuntu.com/7592099/ [03:43] nope, it's still working here [03:43] To really break things you're going to have to wipe. [03:43] The problem is that the cache dir in ~/.cache/upstart-app-launch will stick around. [03:44] tedg: hmm, all I can tell from that is that the app failed to launch :-) Is this issue (issues?) happening outside of the autopilot tests? [03:44] i.e. is autopilot launching (or attempting to) the application correctly [03:44] veebers, Yes, it is. So I don't think it's an AP issue. [03:45] tedg: ah ok, I'll butt-out then :-) let me know if I can help out if there are AP issues [03:56] robotfuel: interesting, I've seen that off and on with a few devices lately [03:56] robotfuel: not on the one that was current when you said that (64 I think?) but with 65, and with some earlier ones too [04:01] plars: are there any workarounds that you know of? [04:01] robotfuel: holding the volume down button while turning it on [04:01] robotfuel: I was getting suspicious that we just had some devices starting to go bad [04:04] plars: interesting I had to do it 2 times, the phone went to recovery from the ubuntu-device-flash script after holding the volume button down, but it still wanted it in bootloader [04:06] robotfuel: oh, well if you specify --bootloader to ubuntu-device-flash it want's it in fastboot mode [04:06] robotfuel: but it won't try to reboot it to fastboot, you have to do that part [04:10] K, so silo 2 seems to fix the issue of the click packages falling back to legacy. [04:10] (and a related bug stemming from that) [04:10] Clock is still broken for me though. [04:12] Seems to be getting a GSettings error. [04:15] robru, plars, so I think that silo2 fixes a bunch of the errors, not sure about all though. [04:15] well, I guess we'll see how 66 looks and see if silo2 provides any relief [04:15] I'm going to run the full set of tests from home with some hope of reproducing whatever's going on [04:16] in isolation, I can't seem to reproduce, but it could just be something that doesn't happen every time [04:18] Makes sense. When would we have results for 67? [04:18] 1000 UTC? [04:21] I'm going to head to bed, if someone could publish 2 that'd be awesome. It definitely makes things better. [04:21] tedg: after it builds [04:21] tedg: 66 is the latest image right now [04:21] and it's looking bad for unity8 at the moment [04:22] I'm watching the carnage right now but I'm going to need sleep shortly... hopefully I won't have nightmares about this all night [04:23] Heh, I hope not! [04:23] 'night folks [04:23] robru, now status says "Migration, one pkg at least is not available at the dest.....". Do I need to intervene? [04:26] robru: well, I'm going to go try to get some sleep. expect unity8 failures in this image 66 at the very least. Not sure about the failures from 65 yet since I didn't manage to reproduce but I'll have a full run going tonight [04:26] robru: I'll be mostly off tomorrow, but will try to get back to my computer as soon as I can (probably mid-late afternoon) === plars is now known as plars-away [04:47] Can anyone from CI team clarify what this means : "Can't merge: One package at least is not available at the destination......" [05:57] camako: did you get that sorted out? it means some package hasn't migrated yet to release pocket. [07:47] * sil2100 sighs [07:53] So, the tests seem to be somewhat broken again - not sure if that's showing off a real bug or just some new problems [07:56] I wonder if the big landing of the UAL has something to do with it, as the apps fail on application start [07:56] sil2100, the two apps are UAL [07:56] missing the package rename in autopilot [07:56] no idea what uniy8 is though [07:56] ogra_: you think so? As I see other apps working fine without the rename [07:56] Attempting to launch application 'com.ubuntu.music_music_1.3.476' with URIs '' via upstart-app-launch [07:57] I see message "with URIs '' via upstart-app-launch" in others that pass [07:57] yes, i think so :) [07:57] oh ? [07:57] hmm [07:57] ogra_: if you open the console log and grep for 'via upstart' you'll see that it's used multiple times [07:58] ** (process:3263): WARNING **: Unable to find keyfile for application 'com.ubuntu.music_music_1.3.476' [07:58] So I thought that it's just a leftover name [07:58] could be indeed [07:58] _usr_lib_python3_dist-packages_autopilot_run.py.32011.crash [07:58] both crashed apps have that one [07:59] hmmm [07:59] Maybe screen unlock didn't work? [07:59] Oh, crash [07:59] yeah [08:00] First I thought about screen unlock failures, as it makes sense in the failure rate... i.e. if it fails for an application test suite, then all tests fail - for unity8 only certain tests fail as the unlock happens on each test [08:00] sil2100, hmm, could it be that your fix for the test setup yesterday used an old branch ? [08:01] hmm, what do you mean? [08:01] i see "ubuntu_filemanager_app" there ... that was changed to filemanager a while ago [08:01] looks like it rolled back a few versions or so [08:02] I was branching cleanly and pushing an MR, so hm [08:02] well, something is weird here [08:02] psivaa: hey, you around? :) [08:02] sil2100: yep, just coming in and looking at the results :/ [08:04] psivaa: so we're wondering, do you have any idea why ubuntu_filemanager_app is there as per ogra_'s comment ? ^ [08:04] psivaa: and do you think it could be the screen unlock failing? [08:05] (I remember Saviq or someone mentioning it as a possible problem) [08:05] sil2100: looking, but the filemanager is really weird [08:05] yeah [08:06] could the device pull from the wrong branch ? [08:07] there is no mention at all of ubuntu_filemanager_app anywhere in the current code [08:08] sil2100, I doubt there's any issue with unlocking, we'd see a *really* red result if that was the case [08:08] oh yay, crashes [08:08] * Saviq retraces [08:09] (process:10790): GLib-GIO-ERROR **: No GSettings schemas are installed on the system [08:09] huh? [08:09] ogra_: sil2100: filemanager was run as ubuntu_filemanager_app accidentally in one of the reruns as far as i see. i'm running it as filemanager now. [08:10] psivaa, ah, ok,, that helps with the confusion at least [08:10] Saviq: where's that from? [08:10] psivaa: ok, thanks [08:10] sil2100, unity8 logs [08:10] sil2100, https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/245/artifact/clientlogs/unity8/unity8.log/*view*/ [08:10] sil2100, that's what unity8 crashes with, at least [08:12] hmm [08:13] Maybe one of the devices has some broken state with packages missing and it causes unity8 and python-autopilot crashes? [08:14] The following NEW packages will be installed: [08:14] gir1.2-upstart-app-launch-2 libpython-stdlib libpython2.7-minimal [08:14] libpython2.7-stdlib libupstart-app-launch2 python python-autopilot [08:14] python-contextlib2 python-dbus python-dbus-dev python-decorator python-evdev [08:14] ogra_: in which test case is that? python2... [08:14] https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/245/consoleFull [08:15] looks like mediaplayer-app [08:16] On 66 only one test failure on mediaplayer-app, but still strange it's pulling in that [08:16] ogra_, sil2100 "mediaplayer_app unity8 dialer_app calendar_app sudoku_app ubuntu_filemanager_app ubuntu_weather_app online_accounts_ui" is the list of suites that were run in that job [08:16] * ogra_ checks if thats the same device the two broken apps were run on [08:16] doesn't include music_app [08:17] mako-11 [08:17] ogra_, music was on mako-02 [08:17] there goes that theory [08:17] calendar-app is mako-11 [08:18] why oh why don't we get the .crash files preprocessed!!! [08:18] Saviq, and unity8 was mako-02 too [08:18] ogra_, huh https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/245/consoleFull ? [08:18] oops, sorry [08:18] 11 too [08:19] Ok, the theory also has a problem since mako-11 also ran tests which passed fine [08:19] before mediaplayer ? [08:19] or after it installed all that cruft (which was never removed) [08:19] Well, unity8 was ran first from what I saw [08:20] And it failed, right? [08:20] right, not saying that we are not seeing two bugs [08:20] Ah, no [08:20] Actually... [08:20] psivaa, is there a way to find the order in which which tests were run on which device [08:20] (so many witches in that sentence :P ) [08:21] But yeah, so the first thing ran was mediaplayer_app, then unity8 and then the others... so still, weather should have failed right? [08:21] * ogra_ gets coffee [08:21] ogra_: yep, let me take a look [08:21] sil2100, unless it gets along with the old AP tests still [08:21] ogra_: that's actually true [08:21] But, why didn't we see it sooner then? [08:22] because UAL only landed in 65 ? [08:22] Ah, right! The gir1.2-upstart-app-launch-2 that's now installed [08:22] the same apps fail in 65 and 66 [08:23] Ok, this starts to make sense [08:23] (question is ... were they run in the same order there) [08:25] * sil2100 is checking the deps [08:27] so with 66, mako-02 ran gallery_app, notes, messaging, music, calc, shorts, uitoolkit in the order and music terribly failed [08:29] and with 66 mako-11 ran mediaplayer, unity8, dialer,calendar, sudoku, ubuntu_file_manager, weather, online_accounts_ui in the order [08:30] psivaa: could you give me a link to the logs from the mako-2 run? [08:30] sil2100: https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/244/consoleText [08:30] brt for the meeting [08:31] can someone reproduce bug 1326694 [08:31] bug 1326694 in unity-scope-click (Ubuntu) "Can't un-install clicks #65 mako - missing uninstall button" [Undecided,New] https://launchpad.net/bugs/1326694 [08:31] also, landing call [08:31] did you discuss https://code.launchpad.net/~ted/ubuntu-app-launch/confine-click-apps/+merge/222114 yet? ready for publishing from ted [08:31] Yeah, trying to log... === pstolowski is now known as pstolowski|bbl [08:59] popey, no memory leakage on my flo over night ... [09:00] (on #64 that was) [09:04] psivaa, bug 1326707 add any info you may have from smoke tests. [09:04] bug 1326707 in ubiquity (Ubuntu) "Ubiquity does't start, hangs in "/usr/lib/ubiquity/bin/ubiquity", line 426, in acquire_lock, test_debconf.stdout.readline()" [Undecided,New] https://launchpad.net/bugs/1326707 [09:04] jibel: ack, thanks [09:05] HAH! [09:05] ogra_, psivaa: I found something [09:05] tell us [09:07] How's the train doing? Can I ask for silos &c? [09:07] you can ask for silos but it is not clear if they can land [09:08] ogra_, psivaa: actually, it's less relevant than I thought, sadly, but it seems that different AP versions are used for different tests [09:08] there are still lots of issues with the upstart-app-launch rename that killl the tests [09:08] ogra_: did you kick a new image? [09:08] that's ok, landing is overrated :-p [09:09] Chipaca: give us some additional minutes and we'll get back to you :) [09:09] sil2100, yeah, the bot should pick it up any minute [09:10] === trainguard: IMAGE 67 building (started: 20140605 09:10) === [09:15] sil2100: I'll go preparing a row :) [09:16] or maybe I won't? has the spreadsheet changed? [09:17] I keep getting to the old one [09:17] Chipaca: http://wiki.ubuntu.com/citrain should take you to the current spreadsheet [09:18] Laney: thanks :) [09:20] ok, row #34 ready for a silo whenever a silo is ready for row #34 :) [09:25] wow! that's a lot of green :D [09:34] Chipaca: ok, tried to assign, but the MP is not a valid MP ;) [09:35] Chipaca: could you modify that? [09:35] d'oh! [09:36] sil2100: there. sorry. [09:37] sil2100: o/ hiya, i have line 27 ready if you have silos available [09:37] dbarth: hey! [09:38] sil2100, ogra_, are you any closer to knowing what happened? it looks like something that landed causes havoc in unity8 https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-mako/1112/? [09:38] we get 100% crash rate in ap tests on device [09:39] oh noes, my ssh! [09:39] uh [09:39] We didn't know it's so serious [09:40] * Saviq tries to retrace [09:41] http://paste.ubuntu.com/7593682/ [09:41] Saviq: I don't know if it is related, but I also got 100% failure in autolanding with a simple change: https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-mako/1106/?#showFailuresLink [09:41] -legacy UAL renaming [09:41] ^the MR is this https://code.launchpad.net/~elopio/ubuntu-ui-toolkit/fix1326072-create_fake_xauthority/+merge/221953 [09:41] t1mp, sounds related indeed [09:42] t1mp, so we got broken Qt it seems [09:43] unless it's the gsettings thing again [09:43] http://people.canonical.com/~ogra/touch-image-stats/65.changes [09:43] thats the changeset [09:43] sil2100, where on the wiki do you document procedures of the CI team ? I want to document the escalation process for unstable tests we discussed during the sprint. [09:43] doesnt look like there was much Qt in it [09:43] (process:3579): GLib-GIO-ERROR **: No GSettings schemas are installed on the system [09:43] right [09:43] ogra_, yeah, I take that back [09:43] it's this fucker [09:43] ++ [09:43] jibel: there is no documentation for that existing, the only procedures have been written in an annoucement e-mail on the phone ML [09:44] so gsettings-desktop-schemas? [09:44] sil2100, ok [09:44] Saviq, yeah, i wonder where that came from [09:44] hmmm [09:44] ah, greeter [09:44] sil2100, how did you plan to escalate AP failures to QA? [09:45] err [09:45] no, that was touch-schemas [09:45] ogra_, no we have that for long [09:45] https://launchpad.net/ubuntu/+source/gsettings-desktop-schemas/3.12.0-1ubuntu1 [09:45] well, it got updated [09:45] looks like a debian sync? [09:45] hrmpf [09:45] brendand: as per the e-mail, we proceed as discussed during the sprint - we assess the test if it's reproducible manually and then either forward it to QA or to the developers in the bug [09:46] * Saviq flashes 64 and upgrades one by one [09:46] seb128, do you know anything about https://launchpad.net/ubuntu/+source/gsettings-desktop-schemas/3.12.0-1ubuntu1 ? smells like we are missing somthing ... [09:46] (process:3579): GLib-GIO-ERROR **: No GSettings schemas are installed on the system [09:46] or Laney ^^ [09:47] It doesn't seem to be anything landed throught the citrain: [09:47] http://people.canonical.com/~lzemczak/landing-team/65.commitlog [09:47] erm [09:47] how do you do that? [09:47] ogra_, seems like the schemas compiler didn't run? [09:47] sil2100, yes but how? [09:47] sil2100, by email, bug tag? [09:48] brendand: it will be marked in the bug and in the landing e-mail, and generally inform QA people available so that it can be passed down further [09:49] brendand: if there are any propositions, I'm all ears [09:50] seb128, when should that run ? postinst ? [09:50] it's a trigger [09:50] ogra_, trigger [09:50] * ogra_ checks the image build logs [09:50] ogra_, ls /usr/share/glib-2.0/schemas [09:50] seb128, hard to do, thats in the lab :) [09:50] Saviq, do you have the error locally ? [09:50] do you have a gschemas.compiled [09:51] ogra_, just flashing [09:51] Saviq: Merge rather than sync (our terminology is that syncs are verbatim copies) [09:51] http://people.canonical.com/~ubuntu-archive/livefs-build-logs/utopic/ubuntu-touch/latest/livecd-armhf.out [09:51] cjwatson, ok, that [09:52] hmm, i dont see any specific errors [09:52] ogra_: I looked throught the diff you made and I think I see a problem [09:52] sil2100, tell me [09:53] ogra_: + def launch_ubuntu_application(self <- this shouldn't be renamed [09:53] ogra_: as per the merge for the python3 rename: [09:53] ogra_: https://code.launchpad.net/~ted/autopilot/ubuntu-app-launch/+merge/220909 [09:54] ogra_: you can see that it was left as launch_upstart_application, just that the underlying bones got modified [09:54] i wonder if that was an oversight though ... i thought tedg wanted to remove all mentioning of upstart ... but yeah [09:55] ogra_: as you can see, he basically did a s/Upstart/Ubuntu , case-sensitive [09:55] sigh, but yeah, seems like it is a lot more than just a search/replace [09:55] Since any other methods that were generally lowercase didn't get changed [09:55] right [09:56] let me redo that then [09:56] * sil2100 just sounded like a complete non-technical person [09:56] ;p === psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: psivaa | CI Train support - US: robru, rsalveti - EU: sil2100, Mirv | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Known issues: - [10:00] sil2100, brendand FTR https://wiki.ubuntu.com/CI/UnstableTests [10:01] what a week, btw... [10:03] jibel, i'm dubious about the idea that a failure that isn't reproducible should be reassigned to infrastructure [10:03] jibel, but ok for it to be owned by qa [10:04] ogra_, so no, of course the tests pass fine locally :| [10:04] brendand, it's now on the wiki, open for discussion and improvements :) [10:04] ogra_, oh wait actually [10:05] ogra_, yeah, I get it on 66 [10:05] nitctl: No such variable: XDG_DATA_DIRS [10:05] soudns related [10:06] not really ... unless you read from Pictures/Music/Video etc etc [10:06] XDG_RUNTIME_DIR would be worrying :) [10:06] hmm ok [10:06] jibel, how do you comment on the wiki? i never knew you could do that === pstolowski|bbl is now known as pstolowski [10:07] sil2100, http://paste.ubuntu.com/7593792/ a little shorter now :) [10:07] Saviq, any dbus errors ? [10:08] ogra_, not that I saw, no [10:08] k [10:08] thats good at least [10:08] * Saviq flashes 94 and will upgrade one by one [10:08] well, try to resinstall the schemas package ... see if it spills an error from the trigger [10:12] Saviq, hmm, i dont see a unity8-greeter landing, i thought you and mterry had changed the wrapper script again in your silo [10:12] ogra_, http://people.canonical.com/~ogra/touch-image-stats/65.changes [10:13] yay for descriptive changelogs ... sigh [10:13] * Bump version so ubuntu-touch-session can reference this one [10:13] ogra_, yeah, sorry about that... [10:13] thats the changelog entry ... i see the changes looking at the diff now [10:14] gawedasduibidfbdsgsgasdkaw ^W [10:14] +1 [10:16] * sil2100 checks the diff [10:17] psivaa, can you check if gsettings-desktop-schemas is installed on mako-11 [10:17] (hoping it is still in the state it was when the tests were run) [10:17] ogra_: ack, 1 sec [10:18] and also as seb128 said ls /usr/share/glib-2.0/schemas [10:18] see if they are there [10:19] the console log at least doesnt show a removal ... [10:20] ogra_: gsettings-desktop-schemas: Installed: 3.12.0-1ubuntu1 [10:20] thanks [10:20] hmm [10:21] and there are a lot of xmls listed under /usr/share/glib-2.0/schemas/ [10:21] psivaa, what about a gschemas.compiled [10:22] seb128: that's there. let me paste the whole list [10:22] where do you see this error? [10:22] Laney, smoke testing [10:22] direct link? [10:22] ogra_: seb128: http://paste.ubuntu.com/7593881/ [10:23] Laney, https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/245/artifact/clientlogs/unity8/unity8.log/*view*/ [10:24] psivaa: does gsettings list-recursively work? [10:24] (as phablet i suppose) [10:24] ogra_: ok, looks better I see... tedg doesn't rename FakeUpstartBase classess, but I guess those are used only internally with autopilot autopilot tests [10:24] k [10:25] So it seems ok [10:25] so upload ? [10:25] Give me another minute ;) [10:25] heh, k [10:27] * ogra_ meanwhile fixes the changelog accordingly [10:27] uh [10:27] Laney: http://paste.ubuntu.com/7593883/ is the output but as root [10:27] psivaa, try as phablet too ... the tests run as the user [10:28] ogra_: another thing... I think we cannot rename UpstartApplicationLauncher to UbuntuApplicationLauncher ;p [10:28] ogra_: since I think it's imported from the UAL [10:28] oh, why ? [10:28] As per the merge tedg made ;p [10:28] It's probably defined as such and hm [10:28] ogra_: it works too when as phablet [10:28] right, just making sure [10:28] Since I didn't see it defined locally in autopilot, so I guess it's imported somehow? [10:28] Still digging [10:29] this is very suspicious [10:29] sil2100, in testcases.py iirc [10:29] Laney, what? the gsettings no schemas thing? [10:29] yes [10:29] yeah, doesn't make sense to me [10:29]