[00:27] cwayne-afk: No, I didn't do spanish. [00:58] trainguards can I have a silo for L64 [00:59] alex-abreu: silo 8. good timing, I gotta run out the door in a sec! [00:59] robru, hehe, thx Robert [00:59] alex-abreu: you're welcome Alex! ;-) [01:01] alright I'm out for dinner but will be back in a couple hours if anybody needs anything === _salem is now known as salem_ === salem_ is now known as _salem === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk [04:55] morning [07:01] archive admin would be still needed to preNEW review/accept indicator-network-tools at https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-006/+packages , and core-dev but still be needed to ack compiz multi-arch changes https://ci-train.ubuntu.com/job/ubuntu-landing-012-2-publish/lastSuccessfulBuild/artifact/packaging_changes_compiz_1%3A0.9.12.0+15.04.20141210.2-0ubuntu1.diff [08:28] trainguards good morning! is it still possible to add one important fix to one my existing rtm silo (that I tested yesterday?) [08:34] pstolowski: my latest info was that it needed to be end of yesterday in the silo, so no. sil2100 should be around soon so we can recheck. [08:34] o/ [08:34] What's up? [08:34] oh, there he is :) [08:35] sil2100: < pstolowski> trainguards good morning! is it still possible to add one important fix to one my existing rtm silo (that I tested yesterday?) [08:35] pstolowski: how important is this fix and to which silo you want to add it? === chihchun_afk is now known as chihchun [08:38] pstolowski, what is the fix? you had 3 weeks to land it, it is a bit late to do it this morning and we already have plenty of silos to test because people waited the last minute to upload fixes [08:41] Mirv, sil2100 jibel I understand your concern. currently discussing how important it is [08:42] pstolowski, okay, if it was critical there would be no discussion ;) let us know what the status is ASAP. If it has to be in the image, we'll have to test it this morning. [08:44] jibel, ok, we just discussed it. it's not critical enough. so skip it for now. thanks [08:44] Mirv, sil2100 ^ [08:44] pstolowski, thanks [08:56] jibel: did bfiller fix the gallery-app silo? [09:01] pstolowski: ok, thanks [09:12] sil2100, apparently yes. I verifying it. [09:12] +'m [09:16] trainguards: good morning, can I have a silo for line 65 ? [09:16] o/ [09:17] sil2100: hey [09:17] mzanetti: hey [09:17] sil2100: think it's still possible to get a silo for row 61? [09:18] mzanetti: for this milestone it's a little bit too late, but we might assign the silo for you to do the testing in a few moments [09:19] ah, ok, cool, thanks [09:19] But QA is already too busy for another silo to enter, that's why the deadline was tomorrow EOD :) [09:20] sil2100, gallery-app is ok [09:20] you mean yesterday, right? [09:20] Yeah... right ;) [09:20] mzanetti: still didn't get my coffee/tea today [09:20] jibel: \o/ [09:21] * mzanetti is currently on that [09:22] Mirv: publishing silo 006 - will you be able to build a click after it gets merged and cleaned? [09:23] sil2100: probably so, yes [09:25] Thanks :) [09:26] Do you know who can publish it for us to the store at this TZ? Since popey is on holidays [09:28] sil2100: what's that? [09:28] sil2100: I can upload, not sure who all can approve it [09:28] ...oh ;) [09:28] gallery app? dholbach can approve if Mirv uploads [09:28] popey: not at the moment, maybe in 1-2h, a new gallery-app :) [09:28] kk [09:28] ah, dholbach, great! [09:28] popey: thanks :) [09:28] np [09:28] Yaaay [09:28] popey: go back to where you came from! :) [09:28] * popey goes back to where he came from [09:29] heh, sound's like a new Hobbit sub-title [09:29] (probably sitting on computer, browsing Ubuntu stuff) [09:29] Hobbit: Back to where you came from [09:29] my engrish good [10:01] sil2100: this looks correct if a bit scary: http://s-jenkins.ubuntu-ci:8080/job/gallery-app-click-from-branch/138/console [10:02] sil2100: it first for unknown reason branches the real trunk. then it checks out the given rtm trunk to "trunk_dir", and later on it can be seen that it starts the compilation also in "trunk_dir" and apparently does not use the vivid trunk for anything [10:03] Mirv: indicator-network-tools looks fine to this ubuntu-archive member [10:03] thanks cjwatson! [10:10] sil2100: can you join #ubuntu-app-devel? [10:11] doh, jibel is not there either, I'll use #ubuntu-touch instead [10:12] sil2100, can I push a vivid device tarball now? [10:15] sil2100, silo 011 must land today? [10:15] bug 1399769 [10:15] Error: Launchpad bug 1399769 could not be found [10:24] jibel: not sure, as it's a barajas bug [10:32] sil2100, anyway it'll need 10 first and a rebuild [10:32] not enough time [10:32] Yeah... === chihchun is now known as chihchun_afk [10:51] trainguards: can silo 14 be published, please? [10:51] oSoMoN: sure [10:52] cheers [11:20] Mirv: the silo3 is finally OK. I have captured two regressions and both were addressed quickly. [11:21] bzoltan_: a good Christmas present to vivid users! [11:21] Mirv: that was the plan :D [11:24] sil2100, gentle re-request: is it ok for me to push a device tarball for vivid (ie are there no planned builds imminent)? [11:26] john-mcaleely: hey! Give me a quick moment to check [11:26] sil2100, thanks [11:27] john-mcaleely: ok, seems like you can push freely - go for it ;) [11:27] sil2100, great [11:28] sil2100, pushed. thank you! [11:45] Mirv: address-book-app is also a click package now, right? [11:45] Mirv: hmmmm [11:46] Mirv: I pressed publish on this silo, but maybe we need the framework changed there too? [11:46] ;/ [11:46] good morning [11:46] Morning [11:46] Phew [11:46] Ok, let me check this first then [11:47] huh, no, it's not a click it seems [11:58] sil2100: no, address-book-app is just .deb [11:58] ...like you then said === _salem is now known as salem_ [12:01] sil2100, silo 11 would need a rebuild right? [12:03] jibel: yes, but only if silo 10 lands [12:03] rvr, ^ what is the status of silo 10? [12:04] jibel: I am not able to reproduce the original issue, but it works [12:04] I wanted some feedback from bfiller [12:26] jibel: sil2100: A new "Manage Scopes" screen has landed in today's images, but it's not translated :P [12:26] geh ;p === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk [12:50] cihelp: would someone mind triggering jenkins on this community MR? https://code.launchpad.net/~danielholm/ubuntu-keyboard/ubuntu-keyboard/+merge/242580 [13:00] oSoMoN: oh right, thanks for über fast landing of the webbrowser-app 5.4.0 fix :) === chihchun_afk is now known as chihchun [13:04] jibel: will we try to get anything else in after silo 10? [13:04] (and the custom tarball) [13:04] sil2100, how long woultd it take to rebuild 11? [13:05] sil2100, it is the only critical left [13:05] It should be quick, considering that 10 would land soon ;) [13:06] rvr, what info do you need from bfiller ? [13:06] wrt to silo 10 [13:06] -to [13:07] jibel: I am not able to reproduce the original problem. Mute works ok in merged calls, both with and without the silo. [13:09] rvr: so are we good re: custom tar? [13:09] cwayne: Yes, fitbit, facebook and instagram rock [13:09] sil2100: so I got +1's now from rvr and ToyKeeper, am I goot to push the magic buttons? [13:10] rvr, sil2100 is it me or the changelog in silo 10 doesn't have anything to do with the bug? [13:10] bug 1398431 [13:10] + * Only set voicemail is the phone number is not empty. (LP: #1398431) [13:10] bug 1398431 in Canonical System Image "Can't mute a conference call " [Critical,Confirmed] https://launchpad.net/bugs/1398431 [13:10] how is it related to multiparty calls? [13:15] jibel: PulseAudio log changes with the silo, so apparently it does something. [13:16] rvr, sil2100 also how a silo can be marked ready for QA sign-off if the testing done by the lander failed? [13:16] jibel: o_O [13:17] rvr, last comment from Bill [13:18] there is something fishy here [13:18] Yes (#<180> ) [13:19] jibel: what the heck? [13:19] cwayne: yes, please press teh button ;) [13:20] rvr, here is the fix in this silo [13:20] 8 - if (mAccount) { [13:20] 9 + if (mAccount && !mAccount->voicemailNumber().isEmpty()) { [13:20] how does it fix conf calls? [13:20] sil2100: pressed :D [13:20] jibel: Yeah, I took a look. [13:21] It's a oneliner [13:21] * sil2100 doesn't know the code so cannot say [13:21] tail -f .cache/upstart/dbus.log | grep Pulse [13:21] No silo [13:21] Setting PulseAudio source 'source.primary' muted '0' [13:21] Setting PulseAudio source 'source.primary' muted '1' [13:21] Silo [13:21] Setting PulseAudio source 'source.primary' muted '1' [13:21] this fix has been push on the 12th, Bill comments on the 15th that it is not fixes, and on build 180 it is magically fixed and ready for QA [13:23] Maybe it was depending on some other silo to land first? [13:23] jibel: Was pushed to vivid [13:24] Would be best if we had Bill here [13:24] jibel: Still happening on rtm, that's what I understand [13:24] sil2100, yeah, it really needs an explanation. Can we land 11 instead? [13:25] sil2100, and it doesn't change that the fix has nothing to do with the bug [13:25] hmm, jibel I suppose Bill should be on in about 30 minutes [13:25] cwayne [13:26] k [13:26] cwayne: sil2100: What's the difference between custom.es and proposed? [13:26] Normally I would say let's land silo 11, but 10 has a critical in it [13:26] rvr: same rootfs, just different custom tarball [13:26] cwayne: sil2100: I just flashed 181 and I don't see the thumbnail problem [13:26] the difference between the custom tar's is *very* small [13:27] rvr: it sounds like an intermittent issue then, nothing on the custom tar should affect that [13:29] cwayne: On the custom image the issue is consistent. Flash -> Camera -> No thumbnail. [13:29] cwayne: I am not blaming anyone, just trying to know what's going on. [13:30] rvr: oh i know [13:30] i just really can't fathom anything in custom causing it, especially since the only thing that *could* (photos-local) hasn't changed [13:31] cwayne: It's not a problem with the scope, gallery and photo roll don't show up the thumbnail either [13:31] rvr: yeah, so that points even more to not custom, it just seems odd that it'd show up consistently there then [13:31] rvr: im flashing now to investigate [13:40] rvr: so, regarding silo 10, besides the questions we have it's all ok, right? [13:41] Mirv: do you know what the hack is that? autopkgtest for unity-scope-click 0.1.1+15.04.20141212.1-0ubuntu1: Regression (Jenkins: public, private) [13:45] bzoltan_: sadly yes I know. not your cause. [13:45] sil2100: would you have time for vivid? [13:45] Mirv: what's up? [13:45] sil2100: long story, but http://d-jenkins.ubuntu-ci:8080/view/Vivid/view/AutoPkgTest/job/vivid-adt-unity-scope-click/lastBuild/ARCH=amd64,label=adt/consoleText [13:45] sil2100: plus the history at https://bugs.launchpad.net/ubuntu/+source/oxide-qt/+bug/1400275 . so no, the latest try did not fix the problem. [13:45] Launchpad bug 1400275 in oxide-qt (Ubuntu Vivid) "Fix oxide-qt codecs dependencies (continued)" [Critical,Fix released] [13:46] sil2100: so we can choose from a) SDK broken (bzoltan not happy), b) autopkgtests broken (a lot of people not happy), c) oxide extra codecs package installed on desktop (chriscoulson not happy), but we still don't know of the option d) fix everything. which of a-c would be preferred? [13:46] we are currently again at b) [13:47] if we revert the last landing, we can go back to c [13:47] if we revert to the start situation, we get to a [13:49] Mirv: I would not break the SDK few days prior the Chinese classes :) [13:50] bzoltan_: yes I wouldn't break SDK. the only thing that speaks for it is that fixing SDK caused the original regression. [13:50] sadly for Oxide people I feel c) is still the smallest problem, at least during development series [13:51] hmmm [13:51] Mirv: strictly speaking it was not the SDK what needed the fix, but the Oxide packaging .. in order to make it multiarch installable [13:52] bzoltan_: I know, I know. so yes, fixing Oxide caused the regression. [13:52] and at the end the real problem might be apt... [13:53] Mirv: we were thinking hard with mvo and chrisccoulson together about the best possible fix. We had like three options and still this one was the most acceptable ... damn it [13:59] sil2100: Right, besides the questions, silo 10 looks ok [14:08] Elleo: you should be able to do so once you approve the MP no ? [14:11] vila: our current process requires jenkins to have run sucessfully before an MP is approved [14:12] Damn, where's Bill... [14:14] Elleo: you should still be able to trigger a -ci job manually [14:14] vila: how do I go about that? [14:14] Elleo: can you get to http://s-jenkins.ubuntu-ci:8080/job/ubuntu-keyboard-ci/build?delay=0sec [14:15] vila: nope, presumably I need some sort of VPN setup? [14:15] Elleo: yup, let me find the wiki page [14:15] thanks [14:21] rvr, jibel : what's up regarding silo 10? you have some questions? [14:21] bfiller: yeah, we're asking Tiago now [14:25] bfiller, it's okay, the changelog is confusing and the test case doesn't say that you can only reproduce when the sim card doesn't provide a voicemail number. [14:26] jibel: ack [14:27] Is it good to publish then? [14:27] sil2100, Mirv: looks like the gallery silo was released and rtm is up-to-date. I was going to build a click from the rtm trunk and push to store. Wasn't sure how to handle the version numbers [14:27] bfiller: ok, so another problem we had... we cannot get gallery uploaded ;/ [14:28] sil2100: ha [14:28] just asking about that [14:28] bfiller: there were 2 problems we saw with the upload: [14:28] 1) The framework was outdated and revisions wrong [14:28] 2) Even after Mirv fixed those up, it seems gallery-app regressed when using the correct framework ;/ [14:28] jibel has more details [14:29] sil2100: hmn, we didn't change the framework, should match what's existing in the store [14:29] bfiller, with the new framework, the gallery app crashes when the QML cache is empty [14:29] bfiller: Mirv built a click from here https://code.launchpad.net/~phablet-team/gallery-app/rtm-14.09-new and it seemed to have issues [14:29] bfiller: there was an announement that the -dev frameworks no longer work for new uploads [14:29] On the ML [14:29] jibel: why do we need to update the framework [14:30] should use whatever was in rtm [14:30] Mirv, ^ [14:30] sil2100: that is the wrong branch [14:30] bfiller, I think because -dev frameworks are deprecated [14:30] bfiller: it's a branch that Mirv prepared so that the versioning is ok [14:30] but Mirv would know the details [14:31] bfiller: it has the exact changes from your -rtm branch but the revisions are correct, as otherwise we wouldn't be able to release as the store has version 1101 and the rtm branch generated version 109something [14:31] jibel: let me check on the framework. I'd be in favor of not changing what was currently in rtm [14:31] that is a big change that these bug fixes don't address [14:31] can handle that one after [14:32] bfiller: I'm not knowledgable about clicks, but I know dholbach rejected it [14:32] Not sure if you can put new things in the store with the old framework at all now [14:32] hmn [14:32] ok [14:32] let me check it [14:32] Mirv would know the details as it was he who wanted to upload (I have no permissions there) [14:33] Anyway, we had to do 2 things to get it to a publishable state: [14:33] 1) Mirv rebased your rtm changes to get the click version generated to be higher than the one in the store (as it seems the RTM version was outdated in comparison to what was in the store version-wise) === salem_ is now known as _salem [14:34] 2) Changed the framework [14:35] sil2100: ok, Mirv are we sure your branch has the exact same stuf as lp:gallery-app/rtm-14.09 branch and just the framework change? [14:35] And since the diff between your rtm branch and the rtm-new branch from Mirv is *only* the framework change, it still seems it regressed and crashes [14:35] sil2100: got it, let me investigate the crash [14:36] bfiller: yes, I even tested it as per Mirv's recommendation - if you take both branches, remove the .bzr dir and do diff -urN between them, you only get this framework change [14:36] So it's the only diff [14:36] jibel has more info ;) [14:36] Too bad Mirv is not here right now [14:36] sil2100: how did Mirv build the click? I usually use http://s-jenkins.ubuntu-ci:8080/view/click/job/gallery-app-click/ [14:36] sil2100: and where is the click that I can test? [14:37] Let me try finding the link [14:37] http://s-jenkins.ubuntu-ci:8080/job/gallery-app-click-from-branch/lastSuccessfulBuild/artifact/out/com.ubuntu.gallery_2.9.1.1113_armhf.click [14:37] So this is what Timo gave us [14:38] sil2100: ok, I"m going to try rebuilding it using http://s-jenkins.ubuntu-ci:8080/view/click/job/gallery-app-click/ as that is what I was told is the proper link to build clicks for the store, maybe there will be some difference [14:38] sil2100: I will rebuild Mirv's branch and retest [14:38] bfiller: oh :) === jdstrand_ is now known as jdstrand === _salem is now known as salem_ === salem_ is now known as _salem [14:49] jibel: so I would say like this - let's see if we can still get gallery-app uploaded and approved [14:49] After that we kick a new image [14:50] sil2100, jibel: what's the status of silo 11 and 16? I know davmor2 tested silo 11 yesterday. I think they both need to be rebuilt after silo 10 lands [14:51] sergiusens, fginther: trying to build a click to upload to the store. Is there a difference between using http://s-jenkins.ubuntu-ci:8080/view/click/job/gallery-app-click/ and http://s-jenkins.ubuntu-ci:8080/job/gallery-app-click-from-branch/ in terms of build env and frameworks, etc? [14:52] bfiller: ok. it looked like the environemnt would be the same between the two, but probably the other one would be useful to remove if not needed [14:52] sil2100: did you have opinion on what to do about that oxide? the current b) option means ~nothing migrates to vivid-release [14:52] Mirv: yeah not sure, just asking. I always use the gallery-app-click link [14:53] Mirv: how much chrisccoulson would be sad if we choose c) ? [14:54] sil2100: judging from the bug filed he'd be Critically sad :) but I don't know the size of the problem of having the oxide extra codecs on the desktop for a while [14:54] bfiller, the only difference is that gallery-app-click-from-branch sets BZR_SOURCE=$target_branch [14:55] bfiller, in the other job it's undefined [14:55] sil2100: other than that the reason for making those two packages was to not have it on desktop [14:55] The worst thing is that we don't have a real fix for that - but that seems like the best workaround we can have [14:55] IMO [14:55] But I'm not a core-dev, we would probably need someone like infinity comment here [14:57] bfiller: how's the gallery check looking? Since we'd need the image kicked off soon, since it's evening is nearing [14:57] (UTC) [14:57] sil2100: it's building still and I just reflashed [14:58] sil2100: just finished [14:58] jibel, brendand: let's skip todays LT meeting as well not to waste time, we should have an image by that time [14:59] sil2100, sure === plars changed the topic of #ubuntu-ci-eng to: Need a silo? ping trainguards | Need help with something else? ping plars | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: lab move complete. RTM Archive open for ota-1 (and only ota-1 !!) landings. [15:00] sil2100, jibel: here a new click to try, I'm trying now http://s-jenkins.ubuntu-ci:8080/view/click/job/gallery-app-click/187/artifact/out/com.ubuntu.gallery_2.9.1.1113_armhf.click [15:01] bfiller: for store, use http://s-jenkins.ubuntu-ci:8080/view/click/job/gallery-app-click/ if possible, or make sure you choose the correct branch in from branch in order for ci not to fail later [15:01] jibel: will you have a moment to try this click above? Maybe it will work better because it's built from a different job? === _salem is now known as salem_ === salem_ is now known as _salem [15:04] sergiusens: thanks [15:04] sil2100, okay, i'll give it a try then we really need an image [15:05] I know, this is the last thing I want to try [15:05] jibel: I'm trying now, how to reproduce crash? seems fine to me even without a qml cache [15:05] no crashing [15:06] bfiller, remove the QML cache of the gallery app, take a photo, go to the photo scope, open the photo. [15:06] bfiller, it opens the gallery app which crashes [15:07] jibel: ok, will try [15:07] jibel: with the new click as well? [15:07] sil2100, no, I haven't try the new build yet [15:07] Ok, phew, so there's still hope [15:10] bfiller, when happens there is an apparmor denial on ~/.cache/QML/Apps/ [15:10] +it [15:10] jibel: that is working fine for me [15:10] jibel: it might have been due to the click package build env being different [15:10] bfiller, with the build above or Mirv's build? [15:10] jibel: with my build [15:10] Build above I suppose [15:10] jibel: on the latest image 182 [15:10] bfiller, good, I'm trying it now [15:11] let me keep trying [15:11] seems Photos scope is gone [15:11] only My Photos [15:11] nm found it [15:12] bfiller: dont scare me like that :) [15:12] cwayne: can't deal with Photos and My Phots [15:12] should just have one :) [15:13] well, ones an aggregator though [15:13] but yeah its unnecessarily confusing [15:14] bfiller, opening the gallery app from the scope works fine, but then it crashes when I switch between photos [15:14] sil2100, if you choose c), you need to talk to the legal team [15:14] jibel: switching between photos on the gallery app or in the scope? [15:14] I'm pretty sure that shipping H264 on the default desktop ISO would restrict how the image could be distributed and used [15:14] bfiller, in the gallery app [15:15] chrisccoulson: ok, that's bad then, nvm this solution ;) [15:15] bfiller, tap a photo, then move to next photo with a right swipe [15:15] bfiller, let me try 1101 again with this test [15:16] bfiller, there is this error in the log, not sure it's related: gallery-app: /build/buildd/thumbnailer-1.3+15.04.20141106~rtm/src/imagescaler.cpp:101: bool ImageScaler::scale(const string&, const string&, ThumbnailSize, const string&, const string&) const: Assertion `ifilename[0] == '/'' failed. [15:18] jibel: ok, just tried it a bunch of times and not crashing for me. That error is interesting. A new thumbnailer has just been released last night could be an issue with that or a mismatch. try again wiht build 182 and the click I sent. seems to be ok for me [15:18] bfiller, yeah, I retrying this case with 1101, the crashes when the apps opens and this one could be different [15:20] chrisccoulson: sil2100: ok, I adjusted the new silo 007 description as "Do not land", and explaining the options. so currently we're stuck at not much being able to land to vivid at all, as long as there is no solution to the installation of packages in autopkgtest:s. [15:20] Mirv: sorry to bug about this, but is there a way to push that UITK out? regardless of anything I do not think that this UITK release has anything to do with the real problem [15:20] grrr [15:20] bzoltan_: currently no-one has an offering that would make it possible :( [15:20] we've three options and all of them are bad [15:20] Mirv: I see [15:20] ;_; [15:21] but of course what we really need is that fourth option... [15:21] Mirv: break the SDK --- land stuff --- unbreak the sdk :) [15:22] that would be possible although as crazy as any of these. or override autopkgtests... [15:23] chrisccoulson: do you have any new ideas regarding solving the problem? [15:23] Mirv: That one I would particularly enjoy [15:24] jibel: so, how's the situation looking on 1101? [15:24] * sil2100 itches for a new image [15:24] Mirv: I am not an expert (read: I am an ignorant idiot) but did the autopkgtests actually captured any real problem in the last years? [15:24] a 4th option is: 1) Introduce a virtual codec package by having the existing packages Provide it, 2) Move the files in each existing package to non-conflicting locations, 3) Remove the Conflicts, 4) Register libffmpegsumo.so with the alternatives system [15:25] sil2100, no crash, but cannot reproduce the crash on 1113 anymore, give me 5 more minutes [15:26] jibel: ok, great news then [15:26] The desktop image would need to seed the desired (free) package then [15:26] sil2100, there is already a crash in /var/crash that might explain why the system doesn't hang [15:26] sil2100: this isnt' the final, final image right? we still need silo 11 landed which fixes a crit [15:26] bfiller: this fix won't make it in time sadly [15:26] I'm rebuilding it now as silo 10 just landed [15:27] bfiller: we're already late with getting the image built, sadly not all crits will be in ;/ [15:27] sil2100: it's only wednesday :) [15:27] sil2100: QA tested that one yesterday [15:27] not sure why it wasn't signed off [15:27] bfiller: yes, and next week are holidays, we need to have a safety net to make sure by Friday we have something promotable [15:28] bfiller: oh, it was? [15:28] sil2100: davmor2 tested it [15:28] jibel: ^? Do you know anything about it? Not sure what's the process, maybe after the rebuild we'd still make it in? Or not? [15:31] sil2100, davmor2 said at 22:10 "Developer added another fix which solved the issue for me however I didn't really have enough time to do a complete run on it." [15:31] I'm a bit worried about the time though... [15:31] sil2100, and for the product team "if a fix puts the promotion at risk then we'll continue w/o fix" [15:31] from [15:32] Right, olli's comment [15:32] Just thought it was fully tested yesterday [15:33] sil2100, can you retrigger the publish of silo 8, pls? [15:35] sil2100, bfiller I cannot reproduce the crash when switching between photos. the assertion is still displayed in the logs. So it might be something that already existed in previous build. [15:35] sil2100, bfiller the crash when the gallery is launched from the scope is gone. [15:37] sil2100, I think you can publish the gallery app and build an image [15:37] jibel, sil2100: I will upload to the store now [15:38] bfiller, thanks [15:38] bfiller: thanks! You have someone to approve it? :) [15:39] I think dholbach should be still around [15:41] cihelp: where can i see the commands run for the autopilot tests being run for the MPs on my branches? [15:42] sil2100, jibel : uploaded 2.9.1.1113 to the store, needs someone to approve === _salem is now known as salem_ [15:44] bfiller: approved! Thanks :) [15:44] sil2100: awesome [15:45] Mirv: what's the best way to make your branch the new lp:gallery-app/rtm-14 branch? [15:46] hmmm [15:46] dobey: in the jenkins job, you should be able to see most of that from the console log [15:46] bfiller: I'd guess push --overwrite [15:47] plars: i don't have any active MPs at the moment and trying to look at the link from the last MP that landed in trunk, i get a 404. [15:47] Mirv: hmm, you have a minute still? [15:47] Mirv: do you know what happened with silo 12 ubuntu-rtm? [15:47] Mirv: ok, we're going to need to do the same thing for camera-app and lp:camera-app/rtm-14.09 to get the versioning correct. Maybe you can send me an email about how you went about doing that for gallery so I can do the same for camera? [15:47] dobey: do you have the link? [15:47] sil2100: I don't feel very focused anymore othwerwise yes :) [15:47] Mirv: since I see qtubuntu-camera is in no known spacetime, and the rtm archive has a revert in it [15:48] Mirv: so, I'm wondering, is the archive in a coherent state now? [15:48] plars: https://jenkins.qa.ubuntu.com/job/autopilot-testrunner-otto-vivid/168/console [15:50] dobey: yeah, it looks like those jobs only go back to the beginning of the month, even on the jenkins behind the vpn that it mirrors [15:50] sil2100: wow, no. the train is waiting for 1202, and what was released was 1208 that was really 1204.. [15:50] I'm confused [15:50] ;) [15:51] sil2100: me too. robru would probably know. [15:51] Mirv: hm, but the silo PPA has actually 0.3.3+15.04.20141208.is.0.3.3+15.04.20141204~rtm-0ubuntu1 [15:51] dobey: I was hoping maybe it was still on that one, but it's not. It may be easiest for you to just run the new one and watch it, but if there's a specific question about how it runs, I may be able to help. Basically it's just calling phablet-click-test-setup after provisioning with the image, and using phablet-test-run for the tests - nothing magic [15:51] So it seems it's all as planned? [15:51] It seems to have been uploaded by rsalveti, so he would know what's up [15:51] * rsalveti looks [15:51] sil2100: oh, that is not a revert of what it was before [15:52] this is just a revert of the initial change I had on that ppa [15:52] Ah uh ok [15:52] as it had more than we should land [15:52] plars: it's running those tests on actual hardware, or in qemu? [15:52] because of the cherry-pick mess [15:52] and then probably build watch_only was missing so train was waiting for wrong package? [15:52] rsalveti: ok, so just a quick question: is what is in the PPA (and the archive now) what we want? [15:52] sil2100: yes :-) [15:52] dobey: oh wait, this is the otto one... no that's different, sorry [15:52] Phew, thanks ;) [15:52] I think this got published yesterday [15:53] * sil2100 leaves rsalveti alone now so he can finally rest [15:53] from the changes file it looks like to be included in 181 [15:53] flashing that now to check before going completely away :-) [15:53] jibel, Mirv, brendand: let's kick a new image now - everyone agreeing? [15:53] dobey: that one is happening in an lxc container [15:53] sil2100, +1 [15:53]