[03:35] === trainguard: IMAGE 60 DONE (finished: 20140602 03:35) === [03:36] === changelog: http://people.canonical.com/~ogra/touch-image-stats/60.changes === [05:05] cihelp jenkins full, can't even launch the clean jobs because also those fail from out of disk space.. :( [05:34] bug 1325467 for anyone on #60 who has an alarm any time soon. [05:34] bug 1325467 in unity8 (Ubuntu) "Alarms appear underneath greeter #60 mako" [Undecided,New] https://launchpad.net/bugs/1325467 [05:34] if you can confirm pls [07:08] Morning! [07:08] hey hey [07:08] Now what the heck happened with test results of the recent images! [07:08] * sil2100 looks at what has changed [07:09] seems there are timeouts in the tests with split greeter [07:09] sil2100, the landing wasnt complete, the unity8 bit only landed yesterday [07:09] hmm [07:10] ogra_: the split greeter one? How was it not complete? Not everything was present in the silo? [07:10] not sure why, but unity8 only made it into the archiove yesterday [07:10] Ah, hm [07:11] Interesting, as I thought the faux-package bumping was no longer required - maybe some autopkgtest failures? [07:12] https://launchpad.net/ubuntu/utopic/+source/unity8/7.87+14.10.20140530.1-0ubuntu1 [07:12] Uh, something broke the CITrain backend I just noticed\ [07:13] not sure what happened, but yeah, could be autopkgtests taking long [07:13] Holy sh... ci-train jenkins seems to be 'broken' [07:13] * ogra_ isnt sure if the "published" date in the proposed pocket entry is actually the date when it entered proposed [07:13] https://ci-train.ubuntu.com/ [07:14] cihelp: hi guys! Does anyone know why all the ci-train executors are dead? [07:14] cihelp: as per https://ci-train.ubuntu.com/ <- [07:15] anyway ... there are now timeouts in the tests ... Saviq was fearing we could have issues with unlocking with the new greeter ... not sure it is that [07:15] (i didnt inspect to deeply yesterday, just made sure we get an image with the landed unity8) [07:16] ogra_, if we affected it, it would be *all* of them, is that the case? [07:16] Saviq: there are like many many test failing now, around 120 failures [07:16] Saviq, nope ... but only -app tests [07:17] ogra_, that shouldn't be the split greeter then, means we're indeed unlocking the screen if we can pass any of them [07:17] Saviq, thats the changeset after which it started ... seems the ailo only half migrated on friday ... http://people.canonical.com/~ogra/touch-image-stats/59.changes [07:18] sil2100: bug 1325467 is interesting [07:18] bug 1325467 in Unity 8 "Alarms appear underneath greeter #60 mako" [High,Triaged] https://launchpad.net/bugs/1325467 [07:18] I don't see anything else that could have caused the failures [07:18] in that snap decisions appear underneath the greeter [07:18] In the changes [07:18] popey, commented on it already [07:18] popey: oh! [07:18] sil2100, well not sure if dbus-x11 is a dep of the greeter split [07:18] morning Saviq ☻ [07:18] ogra_, it is [07:18] popey, that's indeed fallout of split greeter [07:18] ok [07:19] nice one [07:19] Saviq, and the xlibs ? [07:19] * sil2100 is too tired today to feel any pressure regarding the test results [07:20] ogra_, I believe so, it did bring some weird things with it [07:20] hmm, probably deps of the dbus-x11 package [07:20] * Saviq looks [07:22] ogra_, my apt history.log entries from testing the silo: http://pastebin.ubuntu.com/7571253/ [07:22] ogra_, so yeah, the x things are pulled in by split greeter [07:23] yeah, looking at the dependency chain of dbus-x11 shows similar results [07:23] ogra_: yeah, and in the ubuntu-touch-session changelog I only see the greeter added, so no new explicit deps have been filed [07:24] ogra_, direct dep for dbus-x11, too http://bazaar.launchpad.net/~unity-team/unity8/trunk/revision/933/debian/control#debian/control [07:24] I was chatting a lot with Mike on Friday, but I can't remember if he'll be around today or not... [07:24] Since he might be traveling [07:24] sil2100: I reported the jenkins problem to cihelp in the morning [07:25] sil2100: it's out of disk space, and also trying to free up disk space with that one job fails with not enough disk space.. [07:25] i havent seen him at the bomb evacuation ... so he might not have hit one of the delays [07:25] (but he might just have been at another part of the airport) [07:26] so we have chances he traveled fine and is around later today [07:26] sil2100, my suspicion is more towards the infrastructure though [07:27] that we are either lacking something for these failed runs or that something is different from how mterry and Saviq tested [07:27] * ogra_ bets on the latter [07:27] t1mp / bzoltan do you have an ETA on when the fix for 1322527 will land in the image? [07:27] (morning btw) [07:27] popey, it is ready ... [07:27] bzoltan, pinged yesterday (assuming you talk about gallery) [07:27] Ready != on my phone ☻ [07:28] ogra_, now that I look through the diff, I'm not sure why dbus-x11 is a direct dep, we'll have to wait for mterry to comment :| [07:28] wheer is the bot ? [07:28] but then dbus-test-runner is used in a test, and isn't a build-dep... [07:28] Saviq, well, did you run all AP tests or just a selection ? [07:29] ubot5 is here. [07:29] then it doesnt like you :) [07:29] bug #123456 [07:29] bug 123456 in xine-lib (Ubuntu) "podcast crashes amarok" [Undecided,Fix released] https://launchpad.net/bugs/123456 [07:29] Mirv: morning! Now this is unexpected! Didn't he had the 'free disk space' job set up to be ran periodically? [07:29] common [07:29] hmm [07:29] Mirv: I suspect it was in plans and never happened, right? [07:29] bug 1322527 [07:29] bug 1322527 in Ubuntu Terminal App "Terminal app shows no text in #44 on mako" [Critical,Triaged] https://launchpad.net/bugs/1322527 [07:29] sil2100: I don't know, the apt-get clean job was at least disabled. that's probable. [07:30] Saviq, if you ran them all it must be something that is different in the infrastructure ... [07:31] Let's wait for CI to appear and resolve the problem [07:31] ogra_, indeed, we didn't run the whole suite with the latest builds, I got pressed for pushing the button... [07:31] Mirv: for now I disabled auto-refresh of the spreadsheet as it was failing because of the backend being broken [07:31] ogra_, in any case, http://q-jenkins.ubuntu-ci:8080/job/autopilot-release-gatekeeper/140/ was a run some time before, but nothing much changed that would warrant an all-over-the-place fail [07:31] (mostly because of jenkins dying in the middle of some configuration save operation) [07:33] Saviq: do you know of any differences in how tests are ran at the gatekeeper and in smoketesting? [07:33] sil2100, in theory there shouldn't be [07:33] sil2100, they all use phablet-test-run by now [07:34] Since psivaa is not around today, we also basically have no CI to support us [07:34] sil2100, did you have a chance to try and reproduce the issue locally? [07:34] Saviq: not yet, but will try in a moment once my image flashes [07:34] sil2100, doing the same [07:34] Saviq, it seems to hit largely the same tests/app that fail in both image that have the full landing (59 and 60) [07:35] sil2100, ^^^ [07:36] the only one i dont see in the first image is clock app ... all the others are roughly the same [07:38] hmm "via upstart-app-launch", are we monitoring tedg's rename? it didn't happen yet did it? [07:39] looks like launch_click_package got screwed somehow [07:39] the common denominator [07:40] dialer fails on phonesim, so another issue [07:41] gallery has a sh*tload of sqlite errors and then an SDK exception ?? [07:47] popey: t1mp: ogra_: the fix is in the silo3 [07:47] Saviq: yeah, so the name change didn't land yet if anything [07:48] hm, grrr, device problems [07:54] sil2100, ogra_, btw python2 is gone from the device, but phablet-test-run seems to be using it still [07:54] oh jeez [07:57] Saviq, for some deb tests thats ok ... it should pull it in [07:57] (if needed) [07:57] ogra_, well, sure, unity8-autopilot pulls it in... until it won't :P [07:57] Saviq, gallery is something else ... thats older, ignore it [07:59] aargh this whole click test setup is just crazy complex and delicate :| [08:01] Saviq: you mean, the downloading, looking up versions etc? [08:01] sil2100, yeah [08:01] Saviq, and thats fully in sergios hands ... who is on vac iirc [08:01] fun ... [08:02] huhm [08:02] and i think rolling back is also no option ... [08:02] my phablet-test-run is being prevented by apparmor ?! [08:02] oh ? [08:03] balloons mentioned that happened to him too last week iirc [08:03] although that would have ended up in the smoke logs if that was the case [08:03] yeah [08:03] Saviq: have you run "phablet-config autopilot --dbus-probe enable" ? [08:03] popey, ah [08:03] :) [08:03] this shit is CRAZY [08:03] may I remind https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1262879 [08:03] Ubuntu bug 1262879 in Ubuntu CI Services "There should only be one, documented, way to run tests on devices" [Undecided,Confirmed] [08:04] heh [08:04] and yeah, phablet-config just hangs... [08:04] https://wiki.ubuntu.com/Touch/Testing is the "canonical" page [08:04] * Saviq reboots [08:04] it takes a while [08:04] patience [08:05] ah probably rebuilds apparmor policies? [08:05] yes [08:05] so worse if you have lots of apps installed [08:05] Saviq: yeah, it can take even a minute sometimes [08:06] well, we usually only test preinstalled apps [08:06] takes more than a minute here [08:06] for these it should take 20-30sec only [08:06] alan@deep-thought:~$ time phablet-config autopilot --dbus-probe enable [08:06] real 1m36.286s [08:06] woah [08:07] but takes less time on subsequent runs [08:07] alan@deep-thought:~$ time phablet-config autopilot --dbus-probe enable [08:07] real 0m4.027s [08:07] yeah [08:07] it is the initial profile creation that takes ages [08:07] security has plans to ship some pre-created ones in the future [08:08] * ogra_ goes to make meeting coffee [08:09] well seeing ToyKeeper's mail it seems the issues are really AP centric ... doesnt look like she found many issues in dogfooding [08:09] (a unity crash though) [08:11] I wonder if the unlock script is used at all in the end... and if it works... [08:11] maybe it's unreliable [08:11] Saviq: you mean like during the app tests? [08:12] Since there it should unlock the screen once I guess, if it would fail then all tests should fail [08:12] sil2100, I know :| [08:12] Mirv: where are you seeing ENOSPC? https://prodstack-nagios.admin.canonical.com/cgi-bin/nagios3/extinfo.cgi?type=1&host=ue-prodstack-ci-train-jenkins-0 suggests we have plenty, so maybe this is in a tmpfs? [08:13] so yeah... of course it's fine locally :| [08:16] well, all tests do fail for the affected apps [08:16] the 4 that you see passed there are systemsettle, setup and teardown [08:17] they always work [08:18] its not "all apps" but if it fails its "all tests" of an app [08:19] sil2100, teds renaming didnt land yet, did it ? [08:19] ogra_: no [08:19] 04:27:02.746 INFO _launcher:116 - Attempting to launch application 'com.ubuntu.calendar_calendar_0.4.296' with URIs '' via upstart-app-launch [08:19] ok [08:19] ogra_: after Mike's landing it required a rebuild [08:19] ogra_: so no one published it afterwards yet - it's not marked as tested even [08:19] because i see this for all failing tests [08:20] RuntimeError: Timed out while waiting for application to launch [08:20] Yeah, I was suspecting this to be the problem as well, but it doesn't seem so [08:20] ... [08:20] right, but the apps dont seem to start properly [08:20] Saviq, another thing i noticed is that your ram usage is quite high with the new greeter [08:21] its stable ... but high [08:21] 200M for unity8 ... another 90 or so for the greeter [08:21] How did it look like before? [08:22] calendar is OK locally ;| [08:22] i think i remember far below 200 for unity8 ... [08:22] 170 or 180 or so [08:22] ogra_, if anything, it should go down in unity8 [08:22] and we didnt have a greeter [08:22] ogra_, can you file a bug please? we'll investigage [08:23] yeah [08:23] investigage... [08:23] nice word === Ursinha-afk is now known as Ursinha [08:23] :) [08:23] Ursinha, go away ! you are on vacation !!! [08:23] lol [08:23] :) [08:23] I'm not here :) [08:24] * ogra_ pretends he hasnt seen anything [08:24] *whistle* [08:24] :P [08:24] ;p === Ursinha is now known as Ursinha-afk [08:25] ev: https://ci-train.ubuntu.com/computer/%28master%29/executors/5/causeOfDeath [08:26] ev: and first it was in this job output before the jobs also started failing to even start: https://ci-train.ubuntu.com/job/landing-010-2-publish/8/console [08:28] clientlogs touch (run.py:2245): WARNING **: Unable to connect to Upstart bus: Cannot autolaunch D-Bus without X11 $DISPLAY [08:28] hmm [08:28] 04:27:01.320 DEBUG __init__:187 - Patched home to fake home directory /home/phablet/autopilot/fakeenv/tmpyt7h1kxo [08:28] error: XDG_RUNTIME_DIR not set in the environment. [08:28] oha ! [08:29] Uhh? [08:29] WTF [08:30] there seem to be more env issues [08:31] dialer = OK [08:31] initctl: Rejected send message, 1 matched rules; type="method_call", sender=":1.22" (uid=32011 pid=2242 comm="/sbin/initctl set-env HOME=/home/phablet/autopilot") interface="com.ubuntu.Upstart0_6" member="SetEnv" error name="(unset)" requested_reply="0" [08:31] rejected ... [08:32] ogra_: meeting [08:32] yeah [08:35] ogra_, sil2100, not sure what to say... I followed the standard testing process and everything's fine over here :| [08:35] Saviq, yeah, as i suspected ... most likely the infra [08:37] 04:27:01.079 WARNING emulators:26 - The ubuntuuitoolkit.emulators module is deprecated. Import the autopilot helpers from the top-level ubuntuuitoolkit module. [08:38] yeah, that's just a deprecation warning, though, should not affect anything [08:38] yeah, i was just mentioning it in the meeting :) === alan_g_ is now known as alan_g [08:38] (abusin IRC for copy/paste) [08:53] popey: I'm checking the bug and our landing.. [08:53] * ogra_ wonders if dbus gets started differently with the new greeter [08:53] not using the upstart job ... [08:57] bzoltan: what's the status of this landign? https://code.launchpad.net/~bzoltan/ubuntu-ui-toolkit/landing_28-05/+merge/221199 [08:57] popey: ^ the fix for terminal-app is included there^. We are currently trying to land it [08:57] kk [08:57] in silo3 bzoltan said earlier? [08:58] bzoltan: ^ the changelog of that landing is not complete, since we merged staging more stuff is in there [08:58] popey: yes, that's the one. trying to land it since last week. [09:00] popey: feel free to try a phablet-config writable-image --ppa ppa:ci-train-ppa-service/landing-003 [09:02] lots of ap test failures today [09:03] t1mp: will do! [09:08] sil2100, oh, are we in traincon until we get proper tests again ? [09:08] i think we shouldnt land anything til thats resolved [09:08] ogra_: for now we can't land anything anyway ;) [09:08] :D [09:08] (jenkins b0rken) [09:08] (well, probably the gallery fix, but i wouldnt go further) [09:08] yep, i know [09:09] but it might come back during the day [09:09] t1mp: what do you miss there? [09:10] brendand, yeah, some issue with the environment in the infrastructure ... and everyone who could help is either traveling, on vacation or otherwise not around [09:12] I wonder if Paul will be around today, or he also got stuck somewhere in transit [09:13] ev: do you know if Paul will be able to pop up today? [09:13] bzoltan: r1087, 1088 of staging [09:13] sil2100: I'm not sure which day he is taking as swap. What do you need him for? [09:14] ev, 150 failing AP tests :) [09:14] seems the environment is messed up and we need someone to help investigating ... tests pass fine locally [09:15] ah, well, i'm lying ... only 120 [09:15] bzoltan: I think only those two are missing [09:17] ev: right, we would need someone with smoketesting infra experience/access to help us figure out what's wrong with the environment in smoketesting [09:17] ev: which is causing many app failures (which are false positives) [09:18] the whole team is meant to have access and understanding. We're constantly fighting against the silo effect. Unfortunately though we are very short staffed today. [09:18] yeah, like almost everyone [09:18] Siva is on swap. Vincent is out sick. I suspect a fair amount of the US contingent will be taking swap, but it's hard to tell without the new HR system :) [09:19] 04:27:01.287 INFO logging:45 - str: Set the value of an initctl environment variable. Arguments ('/home/phablet/autopilot/fakeenv/tmpyt7h1kxo',). Keyword arguments: {}. [09:19] initctl: Rejected send message, 1 matched rules; type="method_call", sender=":1.22" (uid=32011 pid=2242 comm="/sbin/initctl set-env HOME=/home/phablet/autopilot") interface="com.ubuntu.Upstart0_6" member="SetEnv" error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init") [09:19] error: XDG_RUNTIME_DIR not set in the environment. [09:19] clientlogs touch (run.py:2236): WARNING **: Unable to connect to Upstart bus: Cannot autolaunch D-Bus without X11 $DISPLAY [09:19] thats a summary of th re-occuring errors we see ... usually its these three lines [09:20] it started with the split greeter ... we assume the infra needs something updated for the new setup [09:21] t1mp: I will fix it [09:21] (not sure what though ... and which versions of which tools are installed there) [09:23] ogra_: sil2100: Mirv: is there any news about the UITK landing from the Silo3? [09:23] bzoltan, well, jenkins is dead ... nothing can land [09:23] ogra_: what an excuse :) [09:24] bzoltan, and we have issues with the AP tests for the last two images [09:24] bzoltan: as per description on the spreadsheet, waiting on it to be resolved :) [09:24] so even if jenkins was working we would need to stop the line to get the infra back in shape [09:24] No worries, we'll land as soon as we can! We want to have the infra working and some test doubts solved first [09:25] sil2100: ogra_: ohh.. I missed the yellow cell ... and added a new landing line. Should I delete it? [09:25] no, but you wont get a silo atm [09:25] adding entries is fine, they just wont be processed [09:26] oh, wait [09:26] well, probably better remove it so you get auto-update if you add it the next time [09:27] sil2100, does the "please dont fill new landings" apply to the pending page too ? [09:27] (/me thought we just cant process silos) [09:30] bzoltan: no no, leave it :) We'll just assign it once possible [09:30] ogra_: how long this stop will last? Do I have time to rebuild the landing MRs in the silo? [09:31] sil2100, the text should be more clear ... it sounds like you shouldnt even add to the pending page [09:31] ogra_: you can fill in new landings, let me change the description as it's well... from the moment I didn't know what happened [09:31] yeah [09:31] sil2100: ok we should be more alive now..I'm restaring a few threads [09:32] t1mp: that fixes terminal for me, thanks. [09:32] bzoltan, up to sil2100 what and if he wants to land stuff even after jenkins is back up [09:32] bzoltan, we cant really get test results atm ... thats the second stopper imho, though sil2100 might still want to move ... he's the authority here :) [09:33] Mirv: so, what was the problem in the end? [09:33] ogra_: sil2100: a full rebuild would need an hour [09:34] sil2100: old backups cleaning not working correctly [09:34] bzoltan, well, i think you have time ... it will take a while til we can get someone from the infra team who knows the AP testing infra enough ... [09:36] bzoltan: you can rebuild, it'll give me some time to try and recover from our earlier problems [09:38] (just remember that the SS does not auto-update itself for now) [09:39] hmm, i see a dbus-launch process on my flo ... we never used dbus-launch before [09:40] seems we are running two dbus-daemon processes for the phablet user [09:40] one from the dbus upstart job, the other started via ssh-agent by the greeter [09:41] phablet 1350 0.0 0.0 2700 188 ? Ss Jun01 0:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session ubuntu-touch-session [09:41] phablet 1354 0.0 0.0 3360 604 ? Ss Jun01 0:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session [09:41] phablet 1450 0.0 0.0 4308 1540 ? Ss Jun01 0:08 dbus-daemon --fork --session --address=unix:abstract=/tmp/dbus-wwyt1Zs6rI [09:42] the first two are spawned by the greeter ... the last one is our normal dbus ... [09:46] popey: great, thanks for testing :) I hope it will land today === vrruiz_ is now known as rvr [09:49] heh, the boot animation is quite tiny on the flo screen [09:49] * ogra_ just enabled it [09:50] * sil2100 sighs [09:51] * sil2100 has to hack through jenkins to get the backend back to some usable state [09:55] sil2100: so the file that got corrupted is causing problems? [09:56] Mirv: yeah, I need to use the temporary jenkins job to at least recover some parts of the config so that I can reassign it once again :) Doing that [09:56] ogra_: could you say 'ack' on another "drop using the transitional package, instead use the real one that has been there since trusty": https://ci-train.ubuntu.com/job/landing-010-2-publish/lastSuccessfulBuild/artifact/packaging_changes_signon-ui_0.16+14.10.20140530-0ubuntu1.diff .. [09:57] Mirv, ackedy ack :) [09:57] ack! :) [09:57] Mirv, we still need to go over the seed one day ... i meant to do that at the sprint with you before i realized you wouldnt be there the same week [09:58] ogra_: indeed. so many renames. [09:59] yeah [09:59] ogra_: I was going to be there on the same week, but I got moved.. [09:59] which probably made sense ... [10:01] ev, hey, do you need guinea pigs for the airline maybe? [10:02] * sil2100 is grateful for the "cyphermox test" jenkins job [10:02] :) [10:03] sil2100, are we any closer to finding the issue in smoke? [10:03] Saviq: absolutely. Shall I get you on the list of people we need to engage with once we have the kinks knocked out of staging? [10:03] ev, please do! [10:03] Saviq, i see two sessuon dbus daemons ... [10:04] ogra_, oh [10:04] ogra_, well, wait [10:04] ogra_, the greeter has one, the session has one [10:04] Saviq: a little bit... but I guess it would be best if we had someone wit haccess here [10:04] ogra_, or are you seeing two on the usser? [10:04] Saviq, http://paste.ubuntu.com/7572007/ [10:05] there is also one running as lightdm ... that should be the greeter owned one [10:05] the ssh-agent one is new [10:05] i'm just re-flashing 60 to get a clean env ... [10:05] (another 15min to download over my slow line) [10:07] ogra_, I don't have ssh-agent here [10:07] does there happen to be a way, currently, that we can duplicate a test run from a jenkins job? [10:07] Saviq, on 59/60 ? [10:07] ogra_, 60, yes [10:07] hmm [10:07] that was 59 above [10:07] oh wait [10:07] FUX [10:07] ps aux|grep dbus|grep session|grep phablet [10:08] greyback, remember what I did in the room on Friday afternoon that we said it's gonna become interesting the next time I try to use it? [10:08] i think thats from lightdm ... i cant find any change in the landing that would make it use dbus-launch [10:08] ogra_, ignore everything I said since this morning... I had 55 flashed all the time :| [10:08] don't ask [10:08] oh my [10:09] Saviq: yep! [10:10] greyback, guess what :P [10:10] Saviq: noooo [10:10] OOoh [10:10] * sil2100 runs some tests on his 59 then [10:12] i think we could easily go with dbus-launch but would need to drop the upstart job in the session *and* make sure that the dbus socket address ends up in the file in ~/.cache/upstart/dbus-session ... thats what the tests rely on [10:13] sil2100, can you check on 009? prod it so it gets into proposed? [10:15] seb128, do you remember of the top of your head where dbus-launch is called from in a lightdm session startup ? ... we end up with http://paste.ubuntu.com/7572049/ after the new greeter landed on the phone ... and somehow the AP tests get confused not finding the right dbus [10:16] mhr3_: hi, the hud one? Let me try :) [10:16] i fail to find where dbus-launch is called [10:16] ogra_, I would say Xsession.d scripts [10:17] oh, i dont even have the dir on the old image ! [10:17] ? [10:18] do you have it on the new one? [10:18] ah, no ... i'm to sleepy still ... its there [10:18] root@ubuntu-phablet:~# grep dbus /etc/X11/Xsession.d/* [10:18] root@ubuntu-phablet:~# [10:18] dbus-x11 ships /etc/X11/Xsession.d/75dbus_dbus-launch [10:18] but no dbus stuff [10:18] but I guess that binary is not installed on touch [10:18] not sure how it's started there then [10:18] seb128, right, that landed together with the new greeter stuff [10:18] http://people.canonical.com/~ogra/touch-image-stats/59.changes [10:19] ok [10:19] so that explains why you get a new one [10:19] in the old world we use an upstart job [10:19] now there are both [10:19] right [10:19] though i wonder why the apps work fine ... they should get confused too [10:20] * ogra_ waits for the flash to finish to try some things [10:20] well, do the apps need to use the session bus? [10:20] AP tests do [10:20] and they get the address from a fil that is pointing to the secondly started dbus [10:20] *file [10:20] i guess the session ises theone dbus-launch started [10:21] *uses [10:21] and the secondly started one is just cruft [10:21] seb128, thanks ! that got me on the right track i think [10:21] yw! [10:22] good luck debugging it [10:22] heh [10:22] well, i'm fine with dropping the upstart job ... but we need to create that file somehow so AP can read it to find the bus [10:23] But hm... [10:24] I'm running clock-app tests here now on my device and so far they seem to look ok (we'll see once they're finished) [10:24] Shouldn't it also make them fail on my device? [10:24] Oh, wait [10:25] hm, I got 5 failures, it's still less than what I should expect [10:25] * ogra_ disables the dbus upstart job [10:25] lets see if the session still comes back [10:26] hmm [10:26] doesnt [10:26] so lets try the other way round [10:27] disabling the Xsession.d script [10:29] yeah [10:29] thats fine [10:30] fun, i still get two dbus-daemon processes ... but they use the same address [10:31] sil2100, mount -o remount,rw / && mv /etc/X11/Xsession.d/75dbus_dbus-launch /home/phablet/ && mount -o remount,ro / && reboot [10:31] sil2100, then run your tests again === pete-woods is now known as pete-woods-away [10:36] hah, ok, running [10:37] not sure what it uses dbus-x11 for ... i think we need mike to tell if it is important [10:38] sil2100: I'll probably mark line 9 as Landed manually, since it didn't pick that up [10:39] Ok :) [10:39] Mirv: thanks! [10:39] bzoltan: did you see the error in silo 003? [10:39] also, that means that the first Qt SRU to trusty finally is available to users <- bzoltan [10:41] sil2100, ogra_, in any case, tests work locally on 60, too [10:41] and whoa new calendar! [10:41] ☻ [10:41]