[01:08] asac, you're welcome! [01:31] i'm heading out, but will bring laptop with me. brb [02:04] === trainguard: IMAGE 188 building (started: 20140814 02:05) === [03:08] Mirv: almost all tests fail for the gallery app on a stock 187 image [03:39] === trainguard: IMAGE 188 DONE (finished: 20140814 03:40) === [03:39] === changelog: http://people.canonical.com/~ogra/touch-image-stats/188.changes === [03:48] bzoltan: gallery was "fixed" in #187.. [03:49] Mirv: "fixed" like "fixed"? === cprov__ is now known as cprov [03:55] Mirv: on the stock image 28-31 of 41 tests fail consistently [03:55] bzoltan: fixed for certain tsrget, but seems a lot of failures on mako in dashboard [03:56] Mirv: All right, it means I can not test the UITK release candidate against the gallery autopilot tests... all other tests are OK [03:57] Mirv: I am still struggling with the -gles package to disable the component tests ... after it is done the SIlo7 will be good to go [03:58] ok. we can assume another attempt to make gallery APs work everywhere correctly is being made [04:34] cool, can't launch any app with latest [04:34] rsalveti, pf, apps are for chumps [04:35] and I'm now forced to add a passcode [04:36] rsalveti, indeed libubuntu-app-launch2 is in the new image, can you try downgrading that (or flashing a lower image and then upgrading it if that's easier for you...) [04:36] yeah [04:36] got a few denieds [04:36] http://paste.ubuntu.com/8042111/ [04:37] nah, will just go to bed, that's fun for the european folks [04:37] ogra_: ^^ [04:37] Mirv, ^^ ;-) [04:55] doh :) [06:57] sil2100: I didn't publish UITK yet, as zoltan thought a QA signoff might be required (I'm not sure if that's normal for UITK, or was it just because of the traincon earlier) [07:08] sil2100: Mirv: I am confident that the UITK will not cause regression, but I am happy with an extra QA signoff if you want. === infinity_ is now known as infinity [07:28] bzoltan: I appreciate additional safety anytime! [07:28] bzoltan: let's wait for davmor2 to appear for a quick dogfooding run [07:28] sil2100: OK [07:46] rsalveti, ogra_, davmor2: I got a note from robru that applications don't start on #188 [07:46] Is that true? [07:46] * sil2100 reflashes [07:48] sil2100, any in particular or all the applications? on mako it works fine [07:48] sil2100: they do start for me, everything seems normal [07:48] The e-mail mentioned 'any apps', so I would guess all are broken... probably rsalveti knows more details about those === Guest75668 is now known as wgrant [07:49] I've been using browser, gallery, terminal... [07:49] Mirv: ACK === wgrant is now known as Guest89446 === Guest89446 is now known as wgrant [08:08] sil2100, the smoke tests disagree somehow [08:10] doesnt look liks anything changed for the camera app [08:10] :/ [08:14] ogra_, haven't got that fix in yet. was hoping for tvoss 's branch to land first [08:14] brendand, testing the silo right now [08:14] ogra_, but i'll submit it today either way [08:16] hmm [08:16] mesa pulled in llvm3.4 [08:16] that forced a downgrade of llvm [08:16] hmpf ... and llvm3.5 was a dep of mir it seems [08:18] brendand, ah, i thought the upstart change was the only thing needed (apart from setting the property) [08:19] uh [08:20] and i cant find where the original 3.5 dep comes from, it came in with the mir landing [08:21] ogra_, camera-app has to be modified to set the property and restart the service (and then reset it when done) [08:21] well not the app, the tests [08:21] i thought we'd do that in the infrastructure scripts when setting up the test [08:22] ogra_, hmm. if we want to disable the location prompts for all suites, yes we could [08:22] ogra_, is that what you were thinking? i was just focused on fixing camera_app [08:23] yeah, i guess trust store will get its own functional test anyway ... [08:23] so we could skip it for apps [08:24] * sil2100 thinks 'fudge location prompts' [08:24] * sil2100 thinks a bit too loudly [08:24] * ogra_ grumbles ... [08:24] 'the fudge is under your bed' [08:24] i cant find out why libllvm3.5 came in with image 186 [08:24] mesa [08:25] Laney, oh, was it deliberately downgraded to 3.4 tonight ? [08:25] yes [08:25] 3.5 broke stuff [08:25] phe, ok [08:25] thanks ! [08:26] * ogra_ gets meeting coffee [08:31] popey, davmor2: meeting happy times [08:32] yeah one mo [08:32] hangout says 'wait' [08:33] same [08:33] * popey restarts chrome [08:34] ff worked here [08:37] Chipaca: No notification on a new image again [08:37] davmor2: which new image is that? [08:38] my phone just rebooted from the updated image [08:38] 188 here [08:38] Chipaca: this mornings image [08:38] ogra_, llvm 3.5 caused issues with llvmpipe in mesa, which impacts our ci as some build time tests of apps run under xvfb [08:38] davmor2: number? [08:38] 188, let me double check though [08:38] ogra_, popey is it known that apps don't start with latest image? [08:38] no [08:38] they start here [08:39] if by latest you mean proposed? [08:39] tvoss, yes, we know it is your fault :) [08:39] popey, other arch [08:39] ogra_, ? [08:39] oh [08:39] davmor2: i got: 2014/08/14 04:05:06.049686 DEBUG broadcast chan:0 app: topLevel:1949 payloads:[{"ubuntu-touch/devel-proposed/flo":[188,"ubuntu-touch/utopic-proposed"],"ubuntu-touch/devel-proposed/generic":[18 [08:39] davmor2: in the logs [08:39] tvoss, adding cgroups support to u-a-l [08:39] davmor2: could you zgrep broadcast ~/.cache/upstart/ubuntu-push-client* [08:40] tvoss, that kind of only works if the kernel actually supports cgroups [08:40] ogra_, that wasn't me :) and davmor tested it [08:40] oh, someone mentioned it was you and tde [08:40] *ted [08:40] tvoss: tested on mako though [08:40] (in the landing meeting) [08:40] davmor2, okay [08:43] tvoss: fyi i dont have that device, only nexus 4 [08:44] popey, ack [08:55] tvoss, do you have a silo with the modification of the upstart job for ubuntu-location-service? [08:56] brendand, not yet, let me get to it after having tested my trust-store silo [08:56] psivaa, first we need this branch to land: https://code.launchpad.net/~thomas-voss/location-service/make-sure-trust-store-restarts-on-location-service-restart/+merge/230599 [08:57] Mirv: I see you're working in public today! [08:58] brendand: ok, could you let me know when it's landed and then may be we could test your workaround [08:58] ? [08:58] psivaa, the command you will then need to run is 'sudo setprop custom.location.testing "true"' [08:58] psivaa, followed by 'sudo restart ubuntu-location-service' [08:59] psivaa, and then in the clean up step do the same again but unset the property (or set it to false) [08:59] brendand, just added the mp to silo 15 [08:59] brendand: ok, but that's after the above branch lands, right? [09:00] psivaa, there's a way to make it work without that branch, but we may as well wait to test the actual solution, just to make sure [09:00] sil2100: yeah :) and pretty nerdy looking in that with mako attached to one usb port, charger in use, wired headphones, and a USB extra battery charging from the other USB port [09:01] brendand: ack, do you have vpn setup to the ci lab btw? [09:01] davmor2: Chipaca notifications work for me. [09:01] Mirv, you're in Finland though so i think it's not that unusual to be fully wired up :) [09:02] brendand: hehe :) [09:02] sil2100, well at least the gallery-app issue is reproducible [09:03] sil2100, that's not really good news i know, but... [09:03] Mirv: hah [09:03] brendand: yeah, not sure if I should be happy or not! [09:03] (I guess I should!) [09:04] can i get a silo for line 28 please? [09:04] Chipaca: my battery ran out of go go juice in the night but it is on 187 and I got not ping for 188, however I did on my tablets so I'm assuming that it was just the battery but then is it not meant to check once it is powered back on? [09:04] s/not/no [09:04] sil2100: FYI post-188 I published Unity8 in the morning. it seems Saviq did a late-nighter and was able to even test it during the night. [09:05] or robert tried to publish it but I got the packaging ack and really published it [09:05] davmor2: it is, yes. Did you do that grep? [09:06] brendand: like I mentioned, the latest fix in gallery removed some blockingness from loading the main screen, so I'm wondering whether the tests now think that the gallery-app as loaded too early, and executes tests too early too [09:06] Chipaca: no sorry I'll do that now [09:08] weird though that some tests pass. but for me everything I try in gallery just seems to work. [09:08] Chipaca: http://paste.ubuntu.com/8043645/ [09:09] davmor2: ok. Could you add -A10 to that last zgrep and repeat? [09:09] davmor2: the first of those notifications was posted, at least; we'll see if it was presented (and if not, why not) [09:10] also, dude, adb shell sucks; phablet-shell ftw [09:10] Chipaca: http://paste.ubuntu.com/8043656/ [09:10] Chipaca: :P [09:11] davmor2: it says there that it presented the notification for 188 [09:11] davmor2: at 4am [09:11] Chipaca: too used to adb shell I should use phablet-shell I just forget about it :) [09:12] Chipaca: right and then the battery died so when I powered on no notification [09:12] davmor2: surely every time you've got to tset for it to get the geometry right is enough to remind you? [09:12] Mirv, if it was something that we worked around before then maybe [09:12] davmor2: ah! well, no, notifications don't survive reboots. [09:14] Chipaca: which kinda sucks hard as you don't get the 1 on the system-settings app or the notification area so unless you open system settings ever day to check for updates you'd never know there was one :( [09:15] Chipaca: is there a bug for that do you know? [09:15] davmor2: I'm not following [09:16] davmor2: it's not a bug imho (but then, i didn't understand your issue yet) [09:17] Chipaca: there should be a way to either store the notifications so that when your device reboots you still know what is going on or a recheck after a reboot I think, other wise you can miss the fact that there are updates on your system, most people don't check the setting app daily to see if there are updates [09:17] Mirv, looks like there is something racy there [09:18] davmor2: well... most people don't reboot their device daily either [09:18] davmor2: however, for the special case of system updates, the current situation will change and i believe what you want to happen will still happen [09:18] system and package updates, realy [09:18] -lly* [09:18] Chipaca: no but they will turn them off for plane, battery dying, important meetings etc [09:19] woohoo! [09:20] davmor2: the designed behaviour is that the update message triggers the download (if you have that enabled), and you only get presented the notification when the download completes [09:20] you'd only get the notification directly if you have disabled automatic downloading [09:21] davmor2: if we really want notifications to survive reboots, we probably need to fix it in too many places to start now [09:21] indeed :( [09:22] davmor2: and I don't think we do, anyway; at most, we want to provide a hook for apps to check for notifications on boot or somesuch [09:23] but there are so many races in that that it needs to be done very carefully by all parts [09:23] hands up if you think "done very carefully" is something you can trust appdevs with [09:28] cihelp hey, seems the slave here http://s-jenkins.ubuntu-ci:8080/computer/ps-utopic-server-amd64-2/? broke again :| [09:29] Saviq: let me take a look [09:29] psivaa, thanks === vrruiz_ is now known as rvr [09:46] sil2100: Mirv: is there any news about the UITK landing from the SIlo7? [09:47] bzoltan: I asked davmor2 to perform QA sign-off on silo 007 during the morning meeting [09:47] davmor2: how's it going? [09:47] Saviq: that node is now online [09:48] bzoltan: not yet [09:49] sil2100: hi, think I could get a silo for line 32 ? [09:51] bzoltan: installing now give me about an hour [09:52] ricmm: sure o/ [09:53] thanks [09:58] Mirv, i found an issue [09:58] Mirv, it's not *really* a functional issue, but the user can notice it [09:58] Mirv, launch the app and wait how long it takes for the tab names to appear [09:59] i guess it can be worked around in the test, but i think that's worth a bug [10:00] Mirv: oh, so that would explain the 'tab object not found' errors during smoketesting indeed [10:00] I mean, brendand === psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | CI Train support: trainguards | Vanguard (general help): psivaa | CI Train Status: #179 promoted | CI Train Dashboard: http://bit.ly/1mDv1FS | Known issues: http://bit.ly/1l1Bsoh [10:01] brendand: is that the cause of all the failures? [10:01] sil2100, not sure [10:09] sil2100, probably all the ones with that error. i'll scan them and see which ones might have a different reason [10:10] sil2100, no there are some with a different reason [10:14] davmor2: sweet, thanks [10:26] brendand: right.. good stuff [10:26] sil2100: yep [10:35] popey: can you confirm this one please asked you about it ages ago and just filed it https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1356811 unless I filed it before and just couldn't find it :) [10:35] Ubuntu bug 1356811 in messaging-app (Ubuntu) "Selecting a name from contacts moves the name under the side of the name field" [Medium,New] [10:35] all the bugs merge into one [10:36] sil2100: I have flashed the image 188 and set a password... now I see the password input, but the OSK does not come up. [10:36] Mirv: ^ [10:36] davmor2: you filed that before [10:36] popey: I was pretty sure I had I just couldn't find it [10:37] nvm, confirmed [10:37] popey: it can get merged if I have [10:39] davmor2: sil2100: I see people are changing stuff what effects the application development story. Would you guys pay attention that the SDK features do not suffer? [10:41] bzoltan: hm, it works fine here [10:41] bzoltan: I just set a passphrase and my keyboard appeared during unlocking [10:42] sil2100: good for you :) I am flashing again ... does this feature has test coverage? [10:43] bzoltan: I remember seeing it in unity8 tests, but I'm not entirely sure... but I know it's not using the OSK for keyboard input anyway [10:43] As we have no coverage for the keyboard AT ALL [10:43] sil2100: is there any other easter egg I need to be worried about? [10:43] sil2100: uhh... [10:43] bzoltan: hah! No idea! ;) Better ask Saviq ;p [10:44] http://www.bettercallsaul.com/ [10:44] sil2100: Saviq: for us it is super important, like for _REAL_ that we do not land anything what breaks the app development features. [10:44] bzoltan, and what did I do? [10:45] Saviq: nothing yet :D [10:46] bzoltan, *if* it was that you can't type your password in, I'd say that's more than a development feature that's broken :P [10:46] Saviq: I am reflashing the 188 and see if I got lucky this time and I can type in my password [10:48] bzoltan, is there a manual test plan that covers all app-development specific features? [10:48] bzoltan, obviously, an automatic one would surely be appreciated, too :) [10:50] bzoltan, sil2100: Silo 007 looks good here on mako [10:50] sil2100: the testing on 188, is now complete with uitk rerun having 12 failures( it had 16 in the first run) [10:50] psivaa: ouch :o [10:51] davmor2: thank you [10:51] davmor2: thanks! [10:51] bzoltan: ok, so I'll publish UITK in a minute then ;) [10:51] tvoss: we have [10:51] bzoltan: btw. we might later poke you about some UITK test failures, probably caused by some other landing... ;/ [10:52] (or we just got very unlucky) [10:52] sil2100: whut! tell me now:) [10:53] tvoss: this is the manual tests I run before releases -> https://docs.google.com/a/canonical.com/document/d/1D7J8TgxqDBpuilE8z1EGtUF4OK_kGQm39DodzVbbOKY/edit#heading=h.p8k2gcui1js8 [10:54] bzoltan: do you mean the PIN code screen lock? it works for me. [10:54] there's the own keypad for it [10:54] tvoss: and we have autopilot tests to cover the most critical (chroot and emulator creation) parts.. I will make app deployment tests too soon. [10:55] Mirv: it was a one time problem... i had password lock and the keyboard did not show up [10:55] right === MacSlow is now known as MacSlow|lunch [10:58] tvoss: but just simple open the Ubunu SDK, plug in the device, create a simple app, select the device as target and hit the Run... if the app shows up then it is fine. Should not take longer than a minute... given that you have set up armhf chroot (the SDK does it for you on the first run) [11:00] Saviq: why the lock security setting is hidden in "About this phone" -> "Developer mode" -> Lock security? [11:00] bzoltan, it's not, it's in Security and Privacy, too [11:00] bzoltan: sooo! We noticed some tests failing on 188 - this is a re-run already but we still had 12 failures [11:00] Saviq: ohh redundancy :) what a great invention ...: D [11:00] bzoltan: http://ci.ubuntu.com/smokeng/utopic/touch/mako/188:20140814:20140811.1/9648/ubuntuuitoolkit/ [11:00] bzoltan, it's there in Developer mode because we only allow enabling dev mode *if* you have a pass set [11:01] bzoltan: it had 16 failures on the first run ;) [11:02] sil2100: so who broke the SDK in the meantime? I have tested on 187 and it was all OK [11:03] bzoltan, http://people.canonical.com/~ogra/touch-image-stats/188.changes [11:03] bzoltan: no idea yet! In the past we saw such big number of failures already, but it was happening once per like 20-30 runs [11:03] bzoltan: this time it happened again after a re-run, so we're like hmm, not sure what it's about [11:04] bzoltan: might be the same here, as I said we might just have been very unlucky and hit it twice [11:04] sil2100: RuntimeError: Application Launch Failed: Application failed to start. [11:13] hmm, in #188 the OSK keeps coming up sideways for me [11:18] psivaa, it looks like we have a publishing problem https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-utopic/900/console [11:18] psivaa, or something... [11:18] right, not a publishing one of course, because that's published... [11:19] sil2100: I am running and rerunning the failing tests and they are OK sometimes...all failures are "RuntimeError: Application Launch Failed: Application failed to start" [11:24] Saviq: that issue is i think because of the addition of archiving results, that we did yesterday.. not sure why but that's where jenkins is throwing the exception [11:24] bzoltan: thanks! We'll also try looking into the reasons for those ourselves [11:24] psivaa, ;( seems to have worked a few times http://s-jenkins.ubuntu-ci:8080/job/unity-phablet-qmluitests-utopic/895/ :| [11:25] until this morning [11:26] Saviq: yea, this time it could be transient. i'm rebuilding one without archiving and if it succeeds will rebuild with it again [11:27] psivaa, ok there's one about to complete here too http://s-jenkins.ubuntu-ci:8080/job/unity-phablet-qmluitests-utopic/901/console [11:28] ogra_: who is responsible for the security lock pages? [11:28] Saviq: yep, watching that too [11:28] davmor2, mterry [11:28] ogra_: thanks [11:29] ogra_: there is a small bug, the set button is clickable before the the confirmation code/password is input. [11:36] davmor2: app store is showing me [install] button for apps i already have installed, you getting that? [11:36] popey: I had that ages ago and you couldn't reproduce it ;) let me check [11:40] davmor2: bug 1356837 for you if you reproduce [11:40] bug 1356837 in unity-scope-click (Ubuntu) "Click store shows apps to install but they're already installed" [Undecided,New] https://launchpad.net/bugs/1356837 [11:40] popey: right I think this is a refresh issue. If I search for 2048Native, install it hit the back button to the search results and then click on it again I see the install button. If I keep hitting back till I get to the store and it shows as installed then click on it I then get unistall open as options [11:40] popey: I think it is that the original search is cached so is still showing the app as uninstalled [11:41] right [11:41] which is wrong. [11:41] As aq says, the two hardest things in computing. 1) Naming things. 2) caching. [11:44] Ok, anything else? [11:44] popey: anything I have installed prior to opening the scope shows as unistall/open though [11:44] ^ wrong channel [11:45] Saviq: 901 did not see that exception [11:45] psivaa, ok, maybe I was too fast, thanks [11:46] Saviq: np [11:51] trainguards, could someone hit publish for 14? === alan_g is now known as alan_g|lunch === psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | CI Train support: trainguards | Vanguard (general help): cihelp | CI Train Status: #179 promoted | CI Train Dashboard: http://bit.ly/1mDv1FS | Known issues: http://bit.ly/1l1Bsoh [12:06] tvoss: sure [12:06] Mirv, thanks [12:07] tvoss: not approved... [12:08] this process should maybe warn about it at least verbally at build time already :) [12:08] Mirv, hmmm, weird .. let me see [12:09] tvoss: https://code.launchpad.net/~thomas-voss/trust-store/add-reporting-for-cached-agent/+merge/230470 + https://code.launchpad.net/~thomas-voss/trust-store/add-preseed-support-executable/+merge/230496 [12:10] Mirv, yup === MacSlow|lunch is now known as MacSlow [12:19] sil2100, bzoltan: It seems silo-007 has been given QA-sign off. Are we waiting on something else before publishing it? [12:19] nik90: we're waiting for "davmor2 sign-off" [12:19] Mirv: he already did sign off [12:19] unless of course that's already there, I just thought I'd see it on IRC too [12:19] nik90: right.. [12:20] oh, now I see, it was just in the middle of these other discussions [12:20] Mirv: see spreadsheet it is signed off about an hour ago :P [12:20] np, might check with bzoltan to be sure. It is his landing in case he is holding it for a reason [12:20] I think sil2100 just forgot about it, since he said he'll publish it "in a minute" :) [12:20] it's not anymore in zoltan's hands as such [12:20] ah ok [12:21] then go go go :D [12:21] * Mirv goes goes goes [12:38] psivaa, is it expected that the two nodes are launching for a few minutes now http://s-jenkins.ubuntu-ci:8080/label/utopic&&amd64/? ? [12:47] Saviq: I don't think so. Last week same thing happened, I believe one vm had to be restored and the other one tweaked [12:47] I can have a look [12:50] thanks === alan_g|lunch is now known as alan_g [12:57] So! [12:58] I went to lunch before publishing, since we want to build an image after landing UITK [12:58] And we want one more fix in === josepht changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | CI Train support: trainguards | Vanguard (general help): josepht | CI Train Status: #179 promoted | CI Train Dashboard: http://bit.ly/1mDv1FS | Known issues: http://bit.ly/1l1Bsoh [13:06] Saviq: sorry went afk for lunch [13:07] Ursinha: thanks for looking :) [13:07] psivaa, nw, you're not on vanguard :) [13:07] psivaa, I just hold on to you once I caught you ;)( [13:07] :), that's alright [13:18] sil2100, did you plan an image during the day ? [13:18] ogra_: yes [13:18] can you wait til dbus-property-service is in ? [13:19] ogra_: waiting for UITK to migrate first [13:19] cool [13:19] ogra_: sure, UITK will take a while anyway :) [13:19] * ogra_ bets he is faster :) [13:19] yeah [13:32] ogra_: when's next image being built? do we have one planned? [13:33] popey, see above :) [13:33] soon, but waiting fo UITK [13:33] haha [13:33] ok [13:33] * popey quickly approves 10 clicks into the store [13:33] :) [13:34] Noooo [13:34] [13:34] Mwuhahahaha [13:35] can I get a silo for line 33? [13:36] thostr_: o/ [13:36] sil2100: thanks [13:36] hmmm, actually... [13:36] Where's queuebot?! [13:36] :O [13:37] * sil2100 ressurrects CI Train bot then [13:37] No wonder I didn't see any pings today [13:37] Two bots and both down [13:54] must be a bank holiday in botland then :) [13:59] sil2100: can you add this to the known issues list please https://bugs.launchpad.net/webapps-core/+bug/1356417 [13:59] Ubuntu bug 1356417 in The Webapps-core project "[Facebook] Following a link, then returning to the app causes the app to be blank" [Undecided,Confirmed] [14:00] sil2100: it's made more serious by not being able to recover facebook, which of itself is possibly a good thing see what people post on it, but from an end user point of view not so good ;) [14:01] ;p [14:01] davmor2: hm, is that enough serious to be a blocker? [14:01] Or just a visible issue? === gatox is now known as gatox_lunch [14:02] sil2100: visible for now we can always uprate it latter. [14:03] sil2100: I blame oSoMoN for doing such a good job on the browser memory :) [14:04] ogra_: sil2100: sorry, I should have said which device I tested latest image with :-) [14:04] heh, well, all solved now [14:04] that was a mystery for you guys to solve :P [14:05] but I got a bunch of denied when testing kr yesterday [14:05] yeah === charles_ is now known as charles [14:13] Saviq, problem with the utopic VMs has been resolved, they are all working again [14:19] \o/ [14:19] ogra_: building a new image, UITK in the archive [14:19] +1 [14:19] ogra_: are you ready with your things as well? [14:20] yep [14:23] fginther, thanks, great === alan_g is now known as alan_g|tea [14:27] ogra_: can I get a publish in silo 2? Did-rocks needs to push the button after it gets to the NEW queue and he's in a hurry :-) [14:28] ralsina: I guess ogra_ has no power over CI Train ;) [14:28] ralsina: let me do that [14:28] :) [14:28] right, I got the wrong nicj [14:28] Sorry for that, without the bots around we're a bit blind, as we got used to being poked on IRC [14:28] I keep confusing ogra and rob-ru in my memory :-) [14:29] sil2100: no problem at all, thanks! [14:29] === trainguard: IMAGE 189 building (started: 20140814 14:30) === [14:30] woop woop [14:30] and popey turns into zoidberg again [14:31] sil2100: is the uitk in image 189? [14:31] sil2100: nvr mind..just read backlog [14:31] :) [14:31] nik90: yes ;) [14:31] (\/) (°,,,°) (\/) [14:31] woop woop woop woop [14:31] popey: hahahaahahaha [14:31] Crab people?! [14:33] lol === alan_g|tea is now known as alan_g [14:37] is jenkins ok? seems exceptionally slower than normal lately [14:41] sil2100, https://bugs.launchpad.net/gallery-app/+bug/1356841. get this on your radar [14:41] Ubuntu bug 1356841 in gallery-app "Tabs take a long time to appear" [Undecided,New] [14:41] Uh oh! [14:41] brendand: thanks! [14:42] sil2100, i'm still looking at the other failures - they seem less straightforward [14:43] sil2100: could you reconfig silo 10 [14:43] thostr_: sure [14:45] yay, the bot is back [14:46] Yeah, poked stgraber about that [14:46] It seems it died for unknown reasons [14:47] it had a meeting with the other bots === Ursinha changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | CI Train support: trainguards | Vanguard (general help): Ursinha | CI Train Status: #179 promoted | CI Train Dashboard: http://bit.ly/1mDv1FS | Known issues: http://bit.ly/1l1Bsoh [15:04] tvoss, do you want me to help land silo15? [15:08] cihelp: tried to abort http://s-jenkins.ubuntu-ci:8080/job/ubuntu-system-settings-ci/1231/ and it seems to be hanging [15:08] thanks [15:09] jgdx: looking [15:11] Ursinha, thank yuo [15:16] psivaa, did you try that location-service code? [15:16] brendand: has that MP landed? [15:17] psivaa, no - but there's a way to do it before the mp lands [15:17] psivaa, you just have to 'restart ubuntu-location-trust-stored' as well [15:17] brendand: ohh, i thought you were suggesting to wait till it lands [15:18] psivaa, is it a long process to change things in jenkins? [15:18] psivaa, or just a simple mp? [15:23] brendand, in a few, checking something right now === gatox_lunch is now known as gatox [15:37] ping Ursinha: I'm waiting on ubuntu-experience-tests to go into the archive. But it has been synching for a long time now: https://launchpad.net/ubuntu/utopic/+queue [15:37] Do you know if that's normal? [15:37] psivaa, here's the code you need: http://paste.ubuntu.com/8046270/ [15:37] elopio: I'll have a look, trying to fix another stuck job and will get to it [15:38]