[00:06] So, after configuring a facebook account in UT in the online accounts app... should the facebook app still be asking for username and password? [00:07] ToyKeeper: i think so. facebook app is a webapp. online account / facebook would only work with something like friends app, no? [00:07] ... but IIRC the Friends app was removed. [00:08] ToyKeeper: correct. [00:09] Seems like we should probably either remove the facebook account setting or attach something useful to it. [00:14] ... like make it sync contacts. [00:16] stgraber, bdmurray: ok, so since there are multiple channels per release, that implies that in fact we need channel+version+device_name for a unique identifier? [00:20] ToyKeeper: other things use fb online account, not the fb webapp though [00:20] popey: What other things? [00:21] share photos from gallery [00:21] (I mean, what actually uses it today?) [00:21] trainguards: Looking for help, silo-10 failed to publish I've since sorted out the MP issue, is there a button I can push myself to proceed? [00:23] veebers: you want reconfigure or build? [00:24] xnox: I'm hoping to publish. THe testing has been done but due to traincon-0 the other day the publishing was delayed [00:25] veebers: triggered re-publishing, sponsored on your behalf [00:25] ok, can't you just press publish again? [00:26] mkay [00:26] xnox: awesome cheers. [00:26] cjwatson: that's what I was unsure of :-) [00:26] In the past I've just set testing to done [00:26] * xnox re-acks, republishes again [00:27] veebers: all good. [00:27] veebers: note my comment on https://code.launchpad.net/~thomir/autopilot-qt/trunk-add-build-flags/+merge/228218 BTW [00:27] for future cleanup [00:28] cjwatson: ack, sorry missed that comment earlier [00:28] xnox: thanks [00:31] alecu,dobey: ^- [00:31] * alecu looks [00:35] thanks for spotting that; I'm asking for another review and will ask again. [00:35] you can't top-approve it yourself if it's already adequately reviewed? [00:35] that's all it needs [00:35] xnox, cjwatson : is the bots comment about 'not available at the destination' an error or a status update? [00:36] veebers: status update [00:36] cjwatson: ack, thanks :-) [00:36] ah, there we go [00:36] dobey: thanks [00:36] cjwatson: ah, I thought it needed a review after my latest commit of translation updates. [00:36] alecu: no, all MPs must be top-approved before publishing [00:36] that's all [00:37] great, thanks. [00:43] alecu: yeah, it's the same thing tarmac complains about if you top-approve something, and then push a new revision to it [00:44] I don't think so, this one wasn't top-approved to start with was it? [00:44] it's not my experience that LP magically reverts things away from top-approved [02:04] === trainguard: IMAGE 162 building (started: 20140731 02:05) === [03:29] === trainguard: IMAGE 162 DONE (finished: 20140731 03:30) === [03:29] === changelog: http://people.canonical.com/~ogra/touch-image-stats/162.changes === [04:28] Goodmorning, is anybody active from the landing team? [06:17] hi all [06:17] any idea why webbrowser-app 0.23+14.10.20140730.2-0ubuntu1 has been stuck in the proposed pocket for 4 hours now? it usually migrates to the release pocket much faster than that === tvoss is now known as tvoss|test === tvoss|test is now known as tvoss [07:30] oSoMoN: did you check the reports? [07:32] oSoMoN: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#webbrowser-app "Not touching package due to block request by freeze (contact #ubuntu-release if update is needed)" - all packages that are on images participating in 14.10 alpha 2 are frozen until later today [07:32] cjwatson, I thought the freeze would start being in effect later today? [07:33] ah, got it, it’s 14.10 alpha 2 freeze, not the rtm beta freeze [07:33] sorry for the confusion [07:33] I have no idea about any RTM beta freeze [07:34] cjwatson, well the rtm beta milestone is today, and I assumed there would be some sort of freeze, but obviously that’s an unfounded assumption [07:35] I think that's just a feature delivery milestone, yeah [07:35] I’m a bit dense today and mixing up things, sorry… [07:35] davmor2, you around, yet? [07:35] Freezing seems counterproductive really - we'll be branching off the most recent promoted image, when we branch [07:35] cjwatson, yeah, it makes sense [07:36] Better off trying to get as many of the feature branches as possible done before then [07:44] tvoss: davmor2 should be around in about 40 minutes ;) [07:44] sil2100, thanks === sil2100 changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard (general help): cihelp | CI Train support: sil2100, trainguards | CI Train Status: #157 promoted | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does. [07:55] sil2100, ping [07:56] tvoss: pong! [07:56] sil2100, can I get a silo for line 33? [07:56] sil2100: if you're wondering of the missing tests with 162.. i've kicked them off. should be in soon. === psivaa is now known as psivaa-brb [07:56] tvoss: sure, let me just finish the publishing of other silos and assign one for you [07:57] sil2100, thank you [08:00] sil2100: May I ask for a silo? [08:00] bzoltan: hello! We're a bit lowish on silos, but let me assign one once we get some free (which should be soonish) [08:08] bzoltan: uh! it seems someone locked the UITK already [08:08] sil2100: what is that? [08:08] bzoltan: silo 15 (row 15) from bfiller, something related to the address book or such? [08:09] I can assign if you guys coordinate [08:09] sil2100: OMG... that is wrong. Let me go kick t1mp's butt [08:10] uh oh! ;) [08:10] No violence please! [08:11] sil2100: ahh... that was not t1mp, that was renato again [08:11] sil2100: I am not a violent person :) I am a radical and fundamental pacifist :) [08:11] ;) [08:12] sil2100: That MR is not right.. Renato should not just pick up a UITK development branch and propose to the trunk. We have a staging branch for that [08:13] sil2100: that is exactly what we want to avoid...people landing on our trunk stuff what is not tested. [08:14] sil2100: but hey ... that line15 silo is for testing. It is not meant to land. [08:14] sil2100: should not people stop using the Silos for development? They can set up PPAs in their projects and can push their source packages and test the PPA the way they want. [08:17] bzoltan: amen! [08:17] bzoltan: yeah, so we don't mind giving people silos for development, but it becomes a really big problem when they're hogging them for weeks [08:17] sil2100: So I think we are fine with proceeding with the real UITK landing. [08:17] bzoltan: and there are other dedicated PPAs that can be used for testing [08:17] bzoltan: right! Let me assign [08:18] sil2100: Oh yes... only the UITK and SDK has like 6 PPAs [08:19] bzoltan: you got the border silo! Silo 20 for your disposal ;) [08:19] sil2100: sweet. I hope to release it today === psivaa-brb is now known as psivaa [08:23] sil2100, hmm, i still see a ton of DENIED for calendar in https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/613/artifact/clientlogs/calendar_app/syslog/*view*/ [08:23] (and there seem to be some for media-hub as well) [08:24] in https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/615/artifact/clientlogs/music_app/syslog/*view*/ (other device) there are quite a few for notes-app [08:25] hm [08:25] At least it doesn't seem to break anything [08:26] calendar has 4 failures ... notes has one [08:26] (music has 8 if the media-hub is related here) [08:29] tvoss: hey, so playing with silo 008 last night only issue I've hit so far is that reminders isn't seeing any notes. I'm just going to look in to that a little incase it isn't related and then I'll do a mini dogfood for calls sms mms etc [08:29] davmor2, thanks [08:30] sil2100, can you hold back on silo8 a little until davmor2 gives his final ack? [08:30] tvoss: too late [08:30] tvoss: it has already been published in the morning... [08:30] sil2100, ack. Will hotfix if issues arise [08:30] davmor2, would be great if you could finish your mini-dogfooding, though [08:32] tvoss, sil2100: sms is okay so that's a start [08:32] davmor2, cool [08:35] popey: in reminders do you see your notes and notebooks? [09:05] bzoltan, sil2100 silo 15 was only for testing at the sprint last week, for UITK I was collecting all the visual changes that we made and were not ready to be merged into UITK staging in an rtm-fit-finish branch so that renato could work with them in the apps [09:07] that silo was never intended to land [09:08] t1mp: if not intended to land then it should not be in a silo [09:08] renato: we were just discussing silo15 === renato is now known as Guest78593 [09:09] bzoltan, time, we need sdk on silo 15 to build the apps otherwise the apps will fail, since we are using the stuff from your branch === Guest78593 is now known as renatouy === renatouy is now known as renatou [09:10] renatou: that is fine, but why do not you use a regular PPA for that? Why to block a silo and why to lock all projects you porpose to? [09:11] renatou: we like to land a 'real' UITK now so we need to get rid of silo 15 [09:12] renatou: t1mp: just branch all the branches you want to play with and issue the `dch -i;debuild -i -I -S -sa` and dput the source packages to the PPA. Ask the IS to turn on the armhf builds and that is it. You will have a resident testing Silo. [09:13] t1mp, what is the problem I do not understand [09:13] t1mp: it is fine now.. but the landing team has to look up the reason for the lock and that takes time. [09:14] renatou: we could not land a new UITK because there was already a silo (15) that has UITK changes [09:14] turn on armhf and probably make it devirtualised [09:14] renatou: I wrote what the problem is... whenever you add a UITK branch to the CI landing sheet all UITK landings will be blocked [09:14] unless ubuntu-ui-toolkit works in a virtualised PPA now, which isn't impossible [09:14] renatou: ^ [09:15] what is a virtualised ppa? [09:16] a PPA building in a VM (vs a PPA building on real hardware) [09:16] bzoltan, I think you can remove it until you release and put back after it [09:17] renatou: I do not want to and will not touch other people's landing request. [09:17] ogra_: ahh :) [09:17] bzoltan, ok, when bill arrive I will ask him [09:17] renatou: and I never add other project's branch to my landing without asking the lander of that project. [09:17] eventually everything will be in VMs but it'll take a while yet [09:18] then we can just scale out the builder infrastructure smoothly and there will be unicorns [09:18] bzoltan: they asked me for the branch to collect stuff which they can add to the silo [09:19] bzoltan: I didn't tell you.. I guess nobody foresaw problems with it [09:19] since it was only for quick testing [09:20] it makes sense now to put stuff in ppas, but a silo seems like a quicker solution to set up [09:20] t1mp: well.. we do not land stuff directly to the trunk.. so that should have been clear :) But in general... I do not touch yours, you do not touch mine :) I think that is the safe way.. unless we agree that we have fun by touching each other's things [09:21] t1mp: and I do mean branches and MRs here! [09:21] haha nice way of putting it ;) [09:21] bzoltan: I know that we don't land to trunk, the branch in the silo was only for testing, not for landing (there is not even an MR) [09:21] t1mp: with the good old PPAs it is two commands more... create the source and dput the source [09:21] is silo 15 deleted now? [09:22] t1mp: actually there was an MR [09:23] oh, I see [09:23] rsalveti: ping [09:26] I created the MR and marked it as "work in progress", everybody can do that [09:26] I did not see that as a problem [09:26] rsalveti: I am not sure what to do with the ubuntu-ui-toolkit/gles branch [09:26] renatou: Do you see it now? [09:26] what? [09:28] renatou: 1) using teh limited number of silosfor development when they are meant for landing stuff 2)whenever you add a UITK branch to any Silo, all upcoming UITK landing requests will be blocked, regardless of the comments in your request or the status of the MRs in your request. [09:29] renatou: that is why I suggest you to use the PPAs under your project for development. You can create as many you need and you can asdk the #is to set it up they way you need (armhf builds, real hw) [09:29] bzoltan, 2) is not true, you just need to ask for the landing team to ignore conflicts and let everyone that has a silo with your project in that's the situation [09:30] we still landing our apps even with the branches on silo15 [09:30] Saviq: but that is just waste of time.. [09:30] bzoltan, no it's not, not when the silo is under active work [09:30] bzoltan, and PPAs are not that easy, armhf builders are virtualized by default, and the builds fail for whatever wants to use threads [09:30] Saviq: It is OK for me. It is not that important. [09:31] Saviq: the Silos are PPAs too... [09:31] Saviq: note my "devirtualised" comment above [09:31] also it's worth rechecking your assumptions about virtualised builds given the complete replacement of the virtual builder infrastructure on Monday [09:32] cjwatson, do they not use QEMU any more? [09:32] may well still fail - we think we probably want to import SUSE's grotty qemu-user patch to limit it to a single thread - but the failure modes may be different as now it's based on trusty kernel+qemu rather than a frankenstein bodge on hardy [09:32] still using qemu, just much newer [09:33] not saying it will definitely work now, just that it's worth rechecking assumptions that date from before this week [09:33] this will all be solved by CI airline anyway :P [09:33] sure, but the devirtualised builder infrastructure doesn't scale, by definition [09:33] so we still need to fix this [09:33] sure [09:34] hm, in fact the qemu version was possibly the same by the end, looks like 2.0.0+dfsg-2ubuntu1 was backported. We've seen the newer kernel make a difference for some projects though [09:35] the only thing that CI airline will solve here is not having a fixed pool of silos [09:35] and maybe being better about clashes [09:41] trainguards, can we please remove unity-scope-{mediascanner,click} from silo 005? [09:41] I'm reconfiguring the silo without them [09:44] cihelp, could I get a silo for row 40 (mir 0.6.0)? [09:44] camako: you want the "CI Train support" person in the topic (also there are no free silos right now) [09:45] cjwatson, Ah ok.. Sorry about that.. [09:46] sil2100, waiting for a silo assignment for row 40 (understand all silos full)... [09:53] sil2100, oh it seems we want one more MP to get in.. Updating the sheet. [09:53] hmm, i thought the new webbrowser landed [09:54] doesnt look new in 162 [09:54] oh, it didnt make it into any image yet [10:01] ogra_: alpha 2 freeze [10:03] tvoss, sil2100 so silo 008 is looking okay. The issue with reminders is showing on devices that don't have silo 008 enabled too so that isn't related [10:03] davmor2, \o/ thank you [10:05] sil2100, can you add qtmir to the list of packages requiring -gles twin? [10:05] Saviq: ok! [10:06] sil2100, and drop scope-{click,mediascanner} from silo 005 in the mean time :) [10:07] cjwatson, ah, thanks ... [10:07] Saviq: there no longer is any click or mediascanner scope in 005 :) [10:07] sil2100, ah, someone cleared it up, thanks [10:07] Saviq: ok, and I'll add the qtmir package to the twin list in a moment [10:08] sil2100, awesome, thanks [10:08] camako: right, not silos free, but some packages should finish migrating in a moment [10:09] sil2100, what's going on with silo 8? [10:10] tvoss: ugh, did someone try to rebuild? It was published :| [10:13] sil2100, seems so ... [10:13] sil2100, what do we do? [10:13] mterry, losking works, but the UI is to slow to properly use it when unlocking [10:13] *locking [10:14] ogra_, sil2100: so the reminders thing is down to apparmor="DENIED" by the look of syslog [10:14] but I'll confirm that once I'm on a fresh 162 [10:14] ogra_, how do you mean? [10:15] davmor2, yeah, i think jdstrand should grab all syslogs from the last three devices that rean the smoketests and actually check them [10:15] mterry, the unlock UI with the number pad ... it takes about 3-4sec to recognize a tap from me [10:16] so punching in the numbers is more a matter of luck [10:16] ogra_, whoa... I don't see that. I'm on N4 though... [10:17] tvoss: hmm [10:17] tvoss: ok, I see what happened [10:18] tvoss: someone pressed the wrong button and tried rebuilding on the wrong silo, as robru's dashboard can be confusing sometimes [10:19] tvoss: so what we do now is we wait for it to migrate and manually track it [10:19] sil2100, okay [10:20] I'm shutting down xchat for 5 while I back it up I'll get any pings when I get back [10:36] sil2100: may I get a silo for the QtCreator plugin in the line 41? I will release it an hour after the build is ready. [10:37] sil2100: regression in the guide the last slide slide left doesn't seem to be exiting the slides [10:37] davmor2: oh, that seems to be new [10:38] bzoltan: sure [10:39] sil2100: the number 1? wow,that is nice :) thanks [10:39] that moment when you realize that location service is a trusted helper and your acceptance tests are failing [11:03] sil2100, hope you got some silos left :-) [11:06] sil2100: davmor2 good news, I get to keep my 2nd phone ☻ [11:06] popey: yay I'd miss you cursing the alarms on hangouts if you were only down to one ;) [11:06] hah [11:07] oh, btw I did a fresh flash and when i got the new welcome wizard I turned the phone off (to ship it) [11:07] when I turned the phone back on, there was no wizard [11:07] this seems sub-optimal [11:07] popey: indeed [11:07] * popey will file a bug [11:08] popey: when you go through the slides for the guide see if it exits for me please it didn't for me just [11:08] I need to file a bug for then, I need my reminders app back damn it === MacSlow is now known as MacSlow|lunch === tvoss is now known as tvoss|lunch [11:27] thostr_: looks like something in ms2 has broken music app - https://bugs.launchpad.net/music-app/+bug/1350529 this broke all the tests as it's loading some odd "untitled" artwork (watch the videos linked at http://91.189.93.70:8080/job/generic-mediumtests-utopic/1210/#showFailuresLink ) [11:27] Launchpad bug 1350529 in Ubuntu Music App "[music-app] Trunk fails autopilot tests on jenkins" [High,Triaged] [11:28] sil2100: ^^ this should be a promotion blocker. [11:28] ugh [11:34] popey: thanks for the info :) [11:34] np === greyback is now known as greyback|away === alan_g is now known as alan_g|lunch [12:11] popey: investigating... we did actually a test run of music apps but apparently something went wrong [12:13] sil2100, ping === tvoss|lunch is now known as tvoss [12:22] sil2100, is there a chance of getting a silo soon? Any landings near completion? [12:22] sil2100, silo 8 still seems weird [12:25] tvoss: let me fix that [12:26] sil2100, should give us a silo back [12:26] camako: oh, I see your silo is set to ready now, sorry before me going to lunch it was still as 'No' [12:27] sil2100, np.. had to update some MPs [12:29] camako: so, qtmir and unity-mir are already allocated by silo 14 [12:29] * camako looks [12:30] camako: I can assign a silo if you rebuild once that lands, but not sure when that happens [12:31] sil2100, since it's kgunn's silo we can easily coordinate (kgunn might prefer mir 0.6.0 to get ahead) [12:31] Sure, let me assign then [12:33] sil2100, thanks [12:50] sil2100, I had a mistake in the order of MPs (and got a merge conflict). I corrected the order now. Do you have to reconfig the silo or can I just build? [12:50] silo2100, landing-009 [12:50] camako: you will have to reconfigure before you rebuild, you can do that by pressing the reconfigure button [12:51] sil2100, ah I see. That's pretty cool. [12:51] camako: if you didn't add or remove any 'projects', but just changed the order of merges or added some new ones to existing projects in the silo, then you can reconfigure the silo yourself :) [12:51] camako: if you added something completely new, then we need to do it for you [12:52] sil2100, can I get a silo for line 42? [12:52] sil2100, gotcha [12:52] tvoss: it's not set to ready :) ! [12:53] sil2100, it is in my spread sheet [12:53] :) [12:53] sil2100: The silo1 is good to be published [12:53] tvoss: I see it now :) [12:53] bzoltan: I know! Just pressed publish [12:53] sil2100: thanks :) [12:53] bzoltan: approve teh merges please ;) [12:54] sil2100: sure === alan_g|lunch is now known as alan_g === josepht changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard (general help): josepht | CI Train support: sil2100, trainguards | CI Train Status: #157 promoted | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does. [13:07] sil2100, line 42, line 42, line 42 [13:08] tvoss: oh, the assignment failed, it seems you have location-service already in silo 10 :) [13:08] sil2100, just overwrite it, I'll take care [13:20] jdstrand: hello! [13:23] camako: i think that unity-mir just needs some testing, let me try to get that outta the way (landed or rejected) [13:25] kgunn, ok.. we don't even need to land the MP for unity-mir for 0.6.0 but I was just doing it for thoroughness/cleanliness === tvoss is now known as tvoss|test === tvoss|test is now known as tvoss [13:26] sil2100: hey [13:29] jdstrand: when looking at the syslogs for the test results of the recent image we noticed many different apparmor denials [13:30] sil2100: has anyone filed bugs or listed them anywhere? [13:30] * jdstrand didn't see bugs this morning, but maybe missed them [13:30] jdstrand: we're not sure if they're causing any problems, but still we saw many during for instance calendar or music [13:31] jdstrand: not sure if we have any bugs for those [13:31] sil2100: can you give me a list of links to look at? [13:32] Sure, one moment [13:32] jdstrand: https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/613/artifact/clientlogs/calendar_app/syslog/*view*/ <- calendar app denials here [13:34] jdstrand: https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/615/artifact/clientlogs/notes_app/syslog/*view*/ <- here notes app and some gallery app ones I see [13:34] sil2100: what timestamp? this has all the apparmor-easyprof-ubuntu denials in it [13:35] sil2100: oh, this is the fakeenv stuff [13:35] This is from the latest image smoketesting, i.e. #162 http://ci.ubuntu.com/smokeng/utopic/touch/mako/162:20140731:20140728.1/9386/ [13:36] sil2100: if it says 'fakeenv' in the denial, balloons is aware of the issues there [13:36] the /var/cache/fontconfig/ denial is probably related to the fakeenv not being complete [13:37] sil2100: the calendar is ok [13:37] Ah, ok [13:38] Yeah, I see fakeenv in calendar indeed [13:38] The notes ones are worring us though [13:39] sil2100: the gallery-app is doing something wrong ti try to read /home/phablet/.local/share/applications/. apps aren't allowed to do that [13:40] sil2100: the notes-app denial tofor /home/phablet/.local/share/notes-app/ is a bug in notes-app not using the right path (ie, one that matches its click name) [13:41] sil2100: so, calendar is ballons fakeenv work, notes-app is a bug in notes-app and gallery is it is trying to do something it isn't supposed to [13:41] ACK [13:42] ogra_, brendand, popey: ^ [13:42] sil2100: I imagine the notes-app isn't behaving properly [13:42] jdstrand: I heard it was really behaving strangely recently, but not sure if related [13:43] jdstrand, there were media-hub ones too [13:43] it isn't able to write to its application directory, so, depending on what it is trying to do, I imagine it wouldn't work well [13:43] ogra_: where? [13:43] in both of the sysllogs i looked at this morning [13:44] ogra_: can you give a url? [13:44] the two above [13:44] it isn't in https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/615/artifact/clientlogs/notes_app/syslog/*view*/ [13:44] sil2100, i'm pretty sure notes-app has absolutely nothing to do with apparmor [13:45] sil2100, it's either uitk or the app itself [13:45] brendand: are you the developer of notes-app? [13:45] jdstrand, thats weird ... i promise you there were three denials per syslog [13:45] jdstrand, no [13:45] even identical ones for both devices [13:45] maybe I am blind [13:45] hm, wait [13:45] psivaa, did anything get re-run so that syslog was re-created ? [13:46] as for notes-app-- it likely just needs to set applicationName correctly in its QML [13:46] jdstrand, no, you arent, they are gone [13:46] ogra_: you mena this: kernel: [ 361.379185] type=1400 audit(1406785498.576:119): apparmor="DENIED" operation="file_mmap" profile="/usr/bin/media-hub-server" name="/tmp/orcexec.mF4JRO" pid=3501 comm="multiqueue0:src" requested_mask="m" denied_mask="m" fsuid=32011 ouid=32011 [13:46] https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/615/artifact/clientlogs/music_app/syslog/*view*/ <0 this had media-hub denials for sure [13:46] ogra_: sorry missing the context. reading the backlog [13:46] jdstrand, yeah [13:47] psivaa, the syslog's seem to be different from the ones i looked at this morning [13:47] for 162 [13:47] I may have filed a bug for that [13:48] fyi, that media-hub denial is just noisy [13:49] the way gstreamer works is it tries several deifferent locations until it finds one it can use [13:49] ok [13:49] we had these 8 test failures in music-app so i was thinking they could be related [13:49] well, actually, it is 'm', so maybe not [13:49] it might be now that I think about it more [13:50] if it was 'w', then it would be what I said [13:50] but 'm' indicates it wrote it but couldn't mmap it [13:51] i wonder if recent kernel changes bite us [13:51] with all these apparmor issues coming out of the blue [13:51] no [13:52] openssl was a curl change. pat's was a bug in the upstart job, this is something else, notes-app is just a bug, fakeenv was always there and gallery-app is it just doing something it shouldn't [13:52] ogra_: there were a number of tests that had to be manually started but they should not have changed the syslogs that were already synced [13:52] psivaa, ok. thanks [13:52] jdstrand, well, i find it significant that everything seems to happen at the same time :) [13:53] but thats probably just a murphy-ism [13:53] I don't think it is-- I bet all of this except the curl change were there but no one noticed them [13:54] but people were freaked out about the openssl.cnf so people started looking harder [13:54] * jdstrand has asked for CI to report apparmor denials for a long time [13:54] that didn't come out right [13:55] well, indeeed we only look deeper in the landing meeting if something fails [13:55] I identified that a good report would be apparmor denials on all the test runs, and mentioned it to CI a long time ago [13:56] I think people are just busy and it is an improvement, not a pressing issue [13:56] right, i know paul said he has that on his TODO but other higher prio stuff to solve first [13:56] what I advised paul to do was different> I wanted to =have an infrastructure test to verify the autopilot rules were applied. both would be great [13:59] sil2100, ogra_, jhodapp: fyi, bug #1350870 [13:59] bug 1350870 in media-hub (Ubuntu) "apparmor mmap denial for /tmp/orcexec files" [Undecided,New] https://launchpad.net/bugs/1350870 [13:59] Oh, so it's known, thanks [13:59] I added the rule to the bug to add to the policy [13:59] sil2100: no, I just filed it [13:59] I was thinking of something else [13:59] since 37 seconds :) [14:00] * jdstrand added the rtm14 tag [14:01] that may fix whatever media playback bugs you saw [14:02] \o/ [14:02] I did say *may* :P [14:03] .o. [14:03] hehe [14:03] jdstrand, you need me to add the rule change to media-hub? [14:04] it would be easy for someone seeing the playback issue to verify [14:04] jhodapp: yes please [14:04] jdstrand, and yes, access to the orc memory is very important for software rendering of video [14:04] and other things [14:04] jhodapp: I would imagine in front of any silo landing if possible based on what I've heard here. but may want to talk to sil2100, et al on the priority [14:06] ok [14:07] sil2100: I forget to say that the silo1 is OK now [14:08] bzoltan: thanks! Published :) [14:08] davmor2: what's that "notification" thing in online accounts for google accounts? [14:09] popey: your guess is as good as mine [14:09] heh [14:09] popey: who deals with online account they might know === Ursinha changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Need a silo? Having landing problems? CI Train support: sil2100, trainguards | Vanguard (general help): Ursinha | CI Train Status: #157 promoted | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does. === alan_g is now known as alan_g|tea === greyback|away is now known as greyback === boiko__ is now known as boiko === alan_g|tea is now known as alan_g [14:40] sil2100, could we get a priority on assigning a silo for line 34, it contains critical FTBFS fixes [14:41] bregma: ACK, I remember it not being set to ready in the morning [14:41] Assigning [14:41] thank you very much [14:42] popey, davmor2 you can get gmail notifications [14:42] pmcgowan: oh nice [14:43] I don't use gmail though :D [14:43] we just need dekko notifications too !!! [14:47] pmcgowan: ooh [14:51] davmor2: did you file a bug for the power button sensitivity? [14:51] sil2100, got a high priority bug fix for the media-hub-server apparmor denial bug in spreadsheet line #45 [14:51] sil2100, know if any silos will be freeing up soon? [14:52] popey: you mean the power dialog popup? [14:52] jhodapp: hmmm, let me take a look [14:52] davmor2: yeah, when you wake the phone the power down dialog pops up [14:53] popey: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1349362 [14:53] Launchpad bug 1349362 in unity8 (Ubuntu) "Powerdown Dialog appear on waking the phone" [Critical,Confirmed] [14:54] oh ta === gatox is now known as gatox_lunch [15:11] ogra_: hey, is there a step i missed to get an update of twitter in the image? [15:11] ogra_: i have twitter 1.0.13 approved, but image 165 still contains 1.0.10 it seems [15:11] 165 ? [15:12] uh, yes; or was that 156 that lucio told me about [15:13] but if it was approved but doesnt show up i think you should talk to the store guys === pete-woods1 is now known as pete-woods|lunch [15:21] sil2100: I have added the gles package to the Silo20. Could you help me with thatplease [15:22] bzoltan: hi! How did you add this package? [15:22] bzoltan: how are the tests for the landing going? [15:24] sil2100: do you know how long alpha freeze will take? meaning would it be worth to reassign silos blocked by that? [15:26] ogra_: ok [15:26] bzoltan1: saw your gles uitk pings here now, but guess you should be good now :-) [15:46]