[07:36] <satoris> ping trainguards could I get line 75 assigned?
[08:43] <sil2100> davmor2, jibel: hey, so it seems the new custom tarball changed something besides translations
[08:43] <jibel> sil2100, hey, what did it change?
[08:44] <sil2100> jibel: there's one bugfix and an icon change - forwarding the e-mail (it wasn't sent to any ML again...)
[08:44] <jibel> sil2100, and what is new in 300?
[08:47] <jibel> sil2100, we're really wasting time on these i18n fixes. really doesn't look like ship stopper
[08:51] <tvoss> sil2100, ping
[08:51] <sil2100> tvoss: pong!
[08:52] <sil2100> jibel: I wonder how high-priority those are...
[08:52] <jibel> sil2100, I don't know, I don't speak spanish. I'd understand if the strings where on the wizard but it is not even the case.
[08:56] <sil2100> Damn, the spreadsheet barfed again...
[08:57] <sil2100> Phew, got it back...
[09:03] <cwayne_> sil2100, i stopped sending to the qa ML because my posts never made it through...
[09:04] <sil2100> cwayne_: hey! jibel said that he was actually seeing pings about those, so he was probably approving them ;)
[09:04] <sil2100> cwayne_: if not you can always use phablet@ instead as well!
[09:07] <sil2100> ogra_: really strange... we don't seem to have vivid smoketesting results, but all is fine with ubuntu-rtm ones
[09:07] <jibel> sil2100, actually I don't see the pings, only Julien does, but I'll can moderate incoming messages
[09:07] <sil2100> ogra_: maybe not 'all' is fine since I see some tests did not run
[09:08] <sil2100> cihelp: hey guys! On the rtm krillin dashboard we see that not all tests have been run for #219 - what happened? Those are still in progress?
[09:10] <vila> sil2100: looking
[09:12] <davmor2> cwayne_: that's sneaky :P
[09:13] <davmor2> sil2100: yeap typical developers
[09:13] <sil2100> ;)
[09:23] <cwayne_> hah well, we'd unfrozen our stuff to get more fixes in as we thought we were done for this milestone
[09:25] <vila> sil2100: running http://dev-jenkins.ubuntu-ci:8080/job/utopic-touch_stable-krillin-smoke-daily/805/console
[09:25] <oSoMoN> trainguards: can silo 20 be published, please?
[09:27] <sil2100> oSoMoN: sure :)
[09:28] <sil2100> vila: did a device die during testing before or something?
[09:28] <vila> sil2100: apparently one device failed to properly setup network access
[09:29] <vila> http://dev-jenkins.ubuntu-ci:8080/job/utopic-touch_stable-krillin-smoke-daily/801/console
[09:30] <sil2100> vila: thanks for re-running :)
[09:30] <vila> sil2100: /me crosses fingers it will be enough :-}
[09:36] <alf_> cihelp: Hi! We have been getting some strange failures in CI test runs, and there are some indications that cloud-worker-13 may be corrupted somehow and causing the problem. Can we reprovision this worker with clean image to see if it helps? Also, is the cloud-worker-13 tied to particular hardware?
[09:36] <vila> alf_: looking
[09:37] <alf_> vila: See https://bugs.launchpad.net/mir/+bug/1415027
[09:39] <vila> alf_: http://s-jenkins.ubuntu-ci:8080/computer/cloud-worker-13/builds
[09:41] <vila> alf_: crossing with http://s-jenkins.ubuntu-ci:8080/job/mir-vivid-amd64-autolanding/ and http://s-jenkins.ubuntu-ci:8080/job/mir-vivid-amd64-ci/
[10:08] <bzoltan> sil2100:  may I ask a quick vivid silo for the line 56?
[10:08] <bzoltan> that bot is fast
[10:11] <davmor2> where is chris now damn it
[10:11] <bzoltan> thanks a bunch
[10:12] <sil2100> bzoltan: yw!
[10:12] <sil2100> davmor2: I hope he didn't finish his day yet
[10:12] <sil2100> Anything wrong with the tarball so far?
[10:13] <vila> alf_: that cloud worker now use 4GB, all jobs are pbuilder based so they run inside a chroot so re-imaging shouldn't have an impact AFAICS, will talk to fginther in any case
[10:13] <davmor2> ah it's alright I just wanted to slap him for the hell of it
[10:14] <alf_> vila: thanks
[10:51] <oSoMoN> trainguards: can someone please perform a binary copy of oxide-qt from https://launchpad.net/~phablet-team/+archive/ubuntu/ppa/+packages to https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-001 ?
[10:51] <oSoMoN> (that’s oxide-qt 1.4.2 for vivid)
[11:07] <sil2100> oSoMoN: sure thing!
[11:07] <sil2100> Let me try that
[11:14] <sil2100> oSoMoN: should be in the PPA already
[11:15]  * sil2100 hopes cwayne will still go online today
[11:17] <davmor2> sil2100, jibel: last test just passed on custom
[11:18] <sil2100> davmor2: so we can publish it, right?
[11:18] <davmor2> sil2100: yeap
[11:18] <sil2100> We might need to message Chris somehow
[11:19] <sil2100> The directory doesn't have a mobile though...
[11:19] <davmor2> sil2100: which I guess needs cwayne who is now sciving off
[11:19] <davmor2> sil2100: I'll email him
[11:20] <sil2100> john-mcaleely: hey! In case davmor2's e-mail is not enough, could you somehow try contacting Chris to push the custom tarball to release?
[11:21] <john-mcaleely> sil2100, ack
[11:29] <davmor2> john-mcaleely, sil2100: just got a done reply from cwayne on the list of people in the last custom tarball message \o/
[11:30] <john-mcaleely> davmor2, sil2100 so we're good, yes?
[11:31] <davmor2> john-mcaleely: we just have to wait for the next image to arrive I guess
[11:31] <john-mcaleely> davmor2, nice
[11:31] <davmor2> ogra_, sil2100: can you guys see the wheels in motion for that?
[11:31] <sil2100> \o/
[12:06] <jibel> sil2100, 220 is the candidate? it looks like it contains the latest custom tarball
[12:07] <sil2100> jibel: yeah
[12:07] <sil2100> jibel: it's all good now
[12:22] <sil2100> jibel: should we send Alex a separate e-mail?
[12:47] <oSoMoN> trainguards: can silo 1 be published, please?
[12:48] <sil2100> oSoMoN: publishing!
[12:48] <oSoMoN> sil2100, thanks!
[12:54] <sil2100> grrr, the revert script is somehow broken
[12:58] <sil2100> Ah, yeah, of course, the changes for absolute path changing from Robert weren't made with regards to the reverter
[13:00] <sil2100> Will have to fix that today still
[13:06] <ogra_> sil2100, did anyone look at the smoke results for krillin ... we still have quite a few scoperunner crashes (not to mention 21 test failures) ... i thik this needs to be zero for final
[13:14] <vila> sil2100: #219 should be more complete now
[13:20] <jibel> cihelp, can someone look why krillin 220 failed on the dashboard?
[13:20] <jibel> ogra_, the number of failures is meaningless, the total number of tests changes every run.
[13:21] <ogra_> jibel, once we release the nubmer needs to be zero regardless, this image will be a reference
[13:21] <ogra_> s/will/should/
[13:21] <jibel> ogra_, I don't disagree with that though.
[13:22] <jibel> ogra_, we just don't know if it's better or not than previous builds
[13:22] <ogra_> right, i mean we need it green for release so people can match against the officially released test results
[13:25] <brendand> ogra_, how's that going to happen?
[13:25] <psivaa_> jibel: it was because one of the devices is having some wifi setup failures all the time,
[13:25] <ogra_> brendand, by fixing everyhting ... that should have had time planned for it
[13:25] <ogra_> by the product team ...
[13:25] <psivaa_> i've offlined that device and kicked off another run on that. the tests on the rest are running
[13:25] <jibel> psivaa_, thanks
[13:27] <brendand> ogra_, well if that's really required...
[13:27] <ogra_> brendand, for a release ? well
[13:27] <ogra_> i would expect it, yes
[13:27] <ogra_> and i would expect to take it into account in time planning
[13:28] <ogra_> if that didnt hapopen this time it at least needs to be done in the next planning round
[13:28] <ogra_> the smoke results should be the reference for developers
[13:33] <sil2100> There was no requirement and there is no way we can make that happen
[13:34] <ogra_> :(((
[13:34] <ogra_> this looks reaslly unprofessional imho
[13:34] <ogra_> butu well
[13:34] <sil2100> There is simply no way - we already made it barely for this release, if we put the autopilot work additionally to that we would still be in the middle
[13:34] <sil2100> Not much we can do now sadly
[13:35] <sil2100> And the deadlines don't care about our problems ;p
[13:37] <brendand> ogra_, to put it bluntly, having a clean dashboard requires *everyone* to care about it
[13:40] <ogra_> brendand, rifght, which is why you usually plan to have time (2 weeks or so) to have *everyone* work on fixing this ... in a professional setup at least :P
[13:45] <sil2100> ;p
[13:45] <sil2100> True true
[13:46] <sil2100> satoris: ^ triple confirmed that the mediascanner2 upload fixes music-app and not introducing any regressions?
[13:46] <satoris> sil2100: in the middle of doing that.
[14:02] <satoris> sil2100: it seems that due to a sqlite limitation we can either have fully reliable dash scope updates or a music-app that works. Wanting both would require apparmor changes and possibly daemonification.
[14:06] <sil2100> satoris: how did the situation look before?
[14:08] <satoris> sil2100: when we started updates in scope did not work at all during scans, then they worked perfectly but music-app did not start, the current silo has working music-app and scope updates that work most of the time (but are reliable once the scan stops).
[14:14] <sil2100> satoris: ok, to double confirm - is it better in scopes now than it was before the last upload?
[14:15] <satoris> Most definitely yes. The simple delta is that then the updates did not work at all, now they work but not perfectly.
[14:23] <satoris> sil2100: is the current silo acceptable then? I have tested everything else and they work. Can I mark it as tested (and put explanatory text about the scope unreliability to the status column)?
[14:24] <sil2100> satoris: if the situation is better than it was before (when using the version before the one causing music-app issues), then it's fine
[14:25] <satoris> sil2100: ack, that is exactly the case. Marking appropriately in the spreadsheet then.
[14:26] <sil2100> \o/ Publishing then
[15:15] <zbenjamin> ogra_: ping, could you quick-approve this MR? https://code.launchpad.net/~bzoltan/ubuntu-seeds/target-qmake-extras/+merge/247852
[15:15] <zbenjamin> ogra_: i made a mistake with the package architecture :/
[15:16] <ogra_> zbenjamin, you are sure you want this package installed on every phone ?
[15:16] <ogra_> sdk-libs is our framework
[15:16] <bzoltan> zbenjamin:  apply a bit more selfcriticsm ... atache pictures that you bash yourself :)
[15:16] <bzoltan> ogra_:  no, we want it on every click chroot
[15:17] <ogra_> zbenjamin, bzoltan, then this is a NACK
[15:17] <ogra_> sdk-libs is what we install on the phones
[15:17] <ogra_> to ship the framework
[15:17] <zbenjamin> ogra_: its part of the Qt mkspecs , and by this part of the framework
[15:18] <bzoltan> zbenjamin: ogra_: in that case we want it on ubuntu-sdk-libs-dev
[15:18] <zbenjamin> ok
[15:18] <bzoltan> let me fix the MR
[15:18] <ogra_> zbenjamin, sure, but seedint it there means you install it (and all its dependencies) on every phone
[15:18] <ogra_> bzoltan, that sounds about right, yeah
[15:19] <zbenjamin> ogra_: bzoltan: ok as long as we have a solution
[15:20] <bzoltan> ogra_: zbenjamin: sorry for the hustle .. now the MR is OK
[15:54] <om26er> boiko, can you comment on bug 1413604 please ?
[16:00] <ogra_> FYI: i'm trigering a vivid build ...
[16:01] <sil2100> ogra_: o/
[16:02] <sil2100> The mediascanner2 packages most probably migrated, so it's a good idea
[16:03] <ogra_> ah, cool
[16:03] <ogra_> well, i did it for something else (effectively need a bumped version number for another s-i server)
[16:05] <imgbot> [16:06] <sil2100> Fine with me ;)
[16:30] <plars> sil2100: I know a lot of the focus is on rtm right now, but I was just noticing that phablet-click-test-setup fails on vivid images for a long time now. I suppose that is known and just can't be addressed at the moment for some reason?
[16:31] <sil2100> plars: hey, I saw that yesterday but didn't have time to look into that, but it seems there's still some problem with fetching bzr sources of a click package
[16:31] <plars> sil2100: from the errors, it would appear that lp:ubuntu-terminal-app just doesn't have a latest tag to reference in the branch
[16:31] <plars> bzr: ERROR: Requested revision: 'latest' does not exist in branch: bzr+ssh://bazaar.launchpad.net/+branch/ubuntu-terminal-app/
[16:32] <plars> sil2100: which is probably just the manifest data in ubuntu-terminal-app telling it to pull "latest" rather than a revno
[16:33] <ogra_> why does that work on rtm ?
[16:33] <ogra_> i thought they both pull the same thing currently
[16:34] <ogra_> oh ... probably becvause there is no terminal app in rtm
[16:34] <ogra_> :P
[16:35] <sil2100> ogra_: ;)
[16:35] <sil2100> plars: ugh
[16:44] <sil2100> plars: you're right
[16:44] <sil2100> plars: I actually see in lp:ubuntu-terminal-app something like this:
[16:44] <sil2100>     if(NOT BZR_REVNO)
[16:44] <sil2100>         set(BZR_REVNO "latest")
[16:44] <sil2100>     endif(NOT BZR_REVNO)
[16:44] <sil2100> Where BZR_REVNO is used int the manifest
[16:44] <sil2100> popey: ^
[16:44] <plars> yeah
[16:45] <sil2100> popey: do you know why it's like that?
[16:45] <sil2100> popey: I suppose BZR_REVNO should be set somewhere to be the actual bzr rev instead, but grep returns no other results than thi
[16:45] <sil2100> *this
[16:46] <dbarth_> hi trainguards, can i have a vivid silo for line 61 please ? thank you
[16:48] <sil2100> dbarth_: on it!
[17:00] <dbarth_> ok
[17:01] <pmcgowan> bfiller, silo 20 failed to build, was about to try it
[17:02] <bfiller> pmcgowan: it's actually built correctly just reporeted as failed incorrectly
[17:02] <pmcgowan> bfiller, ah ok
[17:03] <popey> sil2100: meeting overrunning, will be there in a bit
[17:03] <bfiller> pmcgowan: you'll need to stop sync-monitor and rm ~/.config/syncevolution after you install from here
[17:03] <sil2100> popey: sure
[17:04] <pmcgowan> bfiller, oh I thought this had the fix for that
[17:04] <bfiller> pmcgowan: not yet, we're testing that now but not in a silo yet
[17:05] <pmcgowan> bfiller, ok may wait to test that one if its coming soon
[17:18] <popey> plars: which terminal branch are you building there which is failing?
[17:18] <popey> plars: got a link to whatever failure log ?
[17:18] <plars> popey: I'm not building anything that's what's in vivid images
[17:18] <popey> plars: where does the click come from?
[17:19] <popey> i just built it here and it builds fine, with the revno in the click file
[17:19] <plars> popey: from the image
[17:19] <popey> no, i mean, the click in the image, where did that come from.
[17:19] <bzoltan> ogra_: If you are OK with this and merge it to the seeds then I will find somebody who could push  release -> https://code.launchpad.net/~bzoltan/ubuntu-seeds/target-qmake-extras/+merge/247852
[17:20] <plars> popey: through the normal process.  iirc they get built by some job in jenkins before image creation
[17:21] <popey> ok, i dont know what that process is.
[17:21] <popey> i suspect it may be using the old terminal app
[17:21] <popey> not the new one.
[17:21] <plars> popey: I think it would probably be https://jenkins.qa.ubuntu.com/job/terminal-app-click/
[17:22] <popey> yes, thats the wrong one.
[17:22] <plars> popey: that's only a guess
[17:22] <popey> it should be 0.7.41 which comes from lp:ubuntu-terminal-app/reboot
[17:22] <popey> plars: who can fix that?
[17:22] <popey> I imagine someone on the ci help ping list?
[17:23] <plars> popey: I think we can add a job to build the reboot one, if there's not one already. I'm not sure if something needs to change to pull the new one into the image though. That wouldn't be us if so
[17:24] <popey> sil2100: do you know who can do that? ^
[17:26] <plars> fginther: is this just a matter of changing the landing_candidate in the cu2d stack config? to the branch he points at above? or are these separate jobs
[17:34] <fginther> plars, I've been adding a separate job for building clicks from the 'reboot' branch and keep the 'lp:ubuntu-terminal-app' job as is
[17:34] <sil2100> popey: I think all the clicks are pulled in from the custom tarball now, no?
[17:34] <sil2100> ogra_: ^ ? Since I might mix things up
[17:35] <plars> fginther: popey: but the reboot branch *is* the official one now? Is there any reason to preserve the one that builds lp:ubuntu-terminal-app?
[17:35] <imgbot> [17:35] <imgbot> [17:36] <fginther> plars, oh, I thought we needed to keep both branches alive. In that case it only makes since to have the one job and update the branch config there
[17:36] <plars> fginther: I'll confirm with popey, but if so I need to modify the click job separate from the landing job right?
[17:42] <popey> plars: we would like both terminal and reboot to build, but reboot should be the one in the image
[17:43] <plars> popey: ok, I'll duplicate it then
[17:44] <popey> thanks plars
[17:45] <bzoltan> sil2100:  As the UITK from the silo1 will not land on RTM as now ... I think it is OK to free that silo and cancel the landing request
[19:35] <john-mcaleely> http://people.canonical.com/~jhm/barajas/master/device_krillin-20150128-5379bdb.tar.xz
[19:35] <john-mcaleely> http://people.canonical.com/~jhm/barajas/master/device_krillin-20150128-5379bdb.changes
[19:35] <john-mcaleely> http://people.canonical.com/~jhm/barajas/master/device_krillin-testresults-20150128-5379bdb.ods
[19:36] <john-mcaleely> new vivid tarball. with nice test results. is there a good time to push this sil2100 ? (vivid!)
[19:38] <sil2100> john-mcaleely: I think now might be good - ogra_ you have everything you need in the image that built recently?
[19:40] <john-mcaleely> sil2100, sounds good
[19:40]  * john-mcaleely gives ogra some time to respond...
[19:41] <sil2100> john-mcaleely: I'm pretty sure all is ok ;) Push it!
[19:41] <john-mcaleely> sil2100, ack :-)
[19:41] <john-mcaleely> sil2100, pushed!
[19:41] <john-mcaleely> thank you
[19:41] <sil2100> \o/ thanks ;)
[20:05] <cyphermox> sil2100: robru: freed silo 6, all of it has landed so don't mind the messages about stuff not out of proposed.
[20:06] <robru> cyphermox: cool, thanks
[20:48] <tedg> trainguards, could I get a vivid silo for line 63 please?
[20:48] <tedg> No blurry silos, just vivid ones.
[21:11] <robru> tedg: vivid 3
[21:12] <tedg> robru, gracias señor
[21:13] <robru> tedg: you're welcome
[21:34] <jibel> sil2100, it seems the package migrated: unity-plugin-scopes | 0.5.4+15.04.20150126~rtm.is.0.5.4+15.04.20150120~rtm-0ubuntu1 | ubuntu-rtm/14.09/universe
[21:40] <imgbot> [22:50] <imgbot> [22:50] <imgbot>