[02:05] <imgbot> [03:25] <imgbot> [03:25] <imgbot> [06:30] <michi> cihelp: I have a job on Jenkins that’s abnormally slow
[06:31] <michi> http://s-jenkins.ubuntu-ci:8080/job/unity-scopes-api-devel-vivid-amd64-ci/41/console
[06:31] <michi> That one takes several minutes to compile files that normally are done in a second or two.
[06:31] <michi> It’s been compiling for over an hour on code that, normally, compiles in five minutes or less.
[06:31] <michi> Any help with that?
[06:48] <Mirv> (usually not at this hour :( )
[06:52] <michi> OK.
[06:52] <michi> Mirv: thanks
[06:53] <michi> cloud-worker-08 reports 4001 ms response time. Looks like that’s way too long.
[08:51] <ogra_> AlbertA, your mir packages sit still in vivid-proposed
[08:53] <ogra_> (i assume you need to ask an archive admin for NEW queue processing)
[08:53] <sil2100> mir-graphics-drivers-android/arm64 unsatisfiable Depends: libmirplatform4driver-android
[08:53] <sil2100> mir-graphics-drivers-android/arm64 unsatisfiable Depends: libmirclient8driver-android
[08:53] <ogra_> right, i bet they are stuck in NEW
[08:53]  * ogra_ didnt check
[08:54] <ogra_> oh
[08:54] <ogra_> arm64 ... fun
[08:58] <robru> sil2100: ogra_ I looked at that already, there's an all package depending on another package that only lists certain arches, so it should be simple enough to change the 'all' to have the same matching arch list
[08:58] <ogra_> well
[08:59] <ogra_> we will actually want that package on arm64 sooner or later
[08:59]  * ogra_ expects us to actually have to support 64bit HW before end of 2015 ...
[09:00] <ogra_> (on the phone i mean indeed)
[09:00] <ogra_> though i'm not sure we have the right hybris headers yet
[09:00] <robru> ogra_: depends if we're in a hurry or not then ;-)
[09:01] <ogra_> no,, it depends if we want this package on a "potentially forgotten" package list (that we dont maintain) until its bites our butts when trying to build arm64 images ;)
[09:02] <ogra_> i guess it is the right thin atm due to hybris
[09:03] <sil2100> In any way, the lander needs to know about this
[09:03] <ogra_> yeah
[09:03] <sil2100> AlbertA2: hey, give us a sign when you're around ;)
[09:25] <davmor2> Morning all
[09:25] <sil2100> davmor2: o/
[10:23] <sil2100> ogra_: poked victorp about the cgmanager issue, but I guess he's not around currently
[10:28] <ogra_> sil2100, thanks
[10:57] <brendand> sil2100, did the reminders update ever land in the archive?
[10:57] <sil2100> brendand: no, no one was around to test it properly so I never dared to release ;) But there is a vivid and rtm silo for that
[10:58] <brendand> sil2100, ah ok. i'm around now and will test it
[10:58] <sil2100> brendand: thanks!
[10:58] <brendand> sil2100, as we checked those packages aren't seeded so it can't possibly do any harm
[11:01] <ogra_> what do you mean by "no seeded" ??
[11:05] <ogra_> *not
[11:25] <sil2100> ogra_: we need to have a fix pushed to account-plugin-evernote, which is not seeded or pulled in by anything on our ubuntu-rtm images
[11:25] <ogra_> ah
[11:25] <ogra_> the silo only has the app
[11:47] <davmor2> ogra_: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1395682
[11:50] <ogra_> thanks
[11:53] <popey> davmor2: all the files on the sd card are owned by phablet?
[11:53] <popey> you don't have any root owned stuff there?
[13:05] <brendand> sil2100, so can that silo land?
[13:46] <Saviq> sil2100, Wellark, did we get anywhere with the libconnectivity-qt1-dev depends?
[13:46] <bzoltan> Mirv:  thanks ^
[13:51] <Mirv> bzoltan: np, it's building now.
[13:57] <om26er_> seb128,  who maintains ubuntu-system-settings-online-accounts ?
[13:57] <seb128> om26er_, mardy
[13:58] <om26er_> seb128, thanks
[13:58] <seb128> yw!
[13:59] <sil2100> Saviq: I think it didn't move too much ;/ I think I need to prioritize it today
[13:59] <Saviq> sil2100, Wellark was considering making indicator-network a Recommends instead of Depedns
[13:59] <sil2100> Saviq: what about the idea of 2 new metapackages?
[14:00]  * sil2100 vaguely remembers hearing about that
[14:00] <Saviq> sil2100, you mean virtual ones?
[14:00] <sil2100> ogra_: ping... on the meeting I asked about how the revert of the u-a-l landing helps in the cgmanager issue - did anyone try that?
[14:00] <Saviq> sil2100, that wouldn't help when we don't have an alternative atm, we'd still need to Depends: indicator-network | the-virtual-one
[14:01] <ogra_> sil2100, it will just bring back the hard lock
[14:01] <ogra_> sil2100, you can try but it takes hours til the issue even shows up
[14:02] <sil2100> ogra_: since I'm considering testing a quick alternative - since it had to start somewhere, as we didn't have this issue a few images ago
[14:02] <ogra_> sil2100, we have had this issue since forever
[14:02] <ogra_> well
[14:02] <ogra_> since we enabled cgroups supposrt
[14:03] <ogra_> sil2100, and you will ave a hard time to repro it if you dont actually use the phone heavily for some hours
[14:05] <ogra_> sil2100,  the onyl thing we could roll back if the whole of cgroups support ... remember that we had to roll it back due to this issue ... then tedg enabled it believing it was working ... since then we catch up with the symptoms
[14:08] <ogra_> s/if/is/
[14:09]  * sil2100 shrugs
[14:10] <ogra_> sil2100, that means we lose lifecycle management
[14:10] <ogra_> or at least big parts of it
[14:10] <sil2100> We can't release without it as it was a hard requirement
[14:11] <ogra_> sil2100, oh, and if you chack bug 1377332, the cgmanager task was never closed or fixed
[14:11] <ogra_> sits in incomplete/critical
[14:11] <ogra_> and unassigned
[14:23] <brendand_> sil2100, i might have missed your response about the reminders-app landing?
[14:23] <ogra_> sil2100, i commented on bug 1394919 ...
[14:23] <sil2100> brendand_: hey! So, is it tested? Does it help?
[14:23] <brendand_> sil2100, no - which silo is it?
[14:23] <sil2100> brendand_: rtm silo 12
[14:24] <brendand_> sil2100, obviously :)
[14:24] <brendand_> sil2100, i was just looking at clock app failures, now i'll check that
[14:25] <sil2100> brendand_: thanks!
[14:26] <sil2100> ogra_: so let's gather more information this way, but I'm exploring all possible workarounds for the worst case scenario
[14:27] <ogra_> sil2100, i dont see any but dropping all of cgroups support again
[14:27] <ogra_> it never worked
[14:27] <sil2100> Yeah, but now it got more visible it seems
[14:27] <ogra_> not really much more though
[14:28] <ogra_> i always had to reboot my phone on the weekend since we enabled it
[14:28] <ogra_> https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1377332/comments/40
[14:28] <ogra_> heh
[14:28] <ogra_> hallyn even says it is dying
[14:28] <sil2100> Since even after enabling cgroup support (which was really some time ago), I remember people mentioning that the system was good - at least I don't remember you mentioning it to be as bad ;)
[14:29] <ogra_> sil2100, that bug is from image 79
[14:29] <ogra_> thats nearly 100 images ago
[14:32] <ogra_> sil2100, seriously, the only non crashy option will be to disable cgroups again and live with it ... or to fix cgmanager now ... its a shame that bug didnt get finished but i blame bug management via spreadsheets here, that made it fall off the radar
[14:33] <Elleo> cihelp: Would someone mind triggering jenkins on this community MR? https://code.launchpad.net/~danielholm/ubuntu-keyboard/ubuntu-keyboard/+merge/242580 thanks :)
[14:33] <ogra_> the bug was reported during the sprint ... ted had attempted to land cgroups before the sprint and had to roll it back due to this bug ... then after the sprint added the recoverable error bit to UAL
[14:33] <sil2100> ogra_: yeah, it introduced a lot of unneeded confusion, as this just means that one of our topblockers simply hasn't been fixed
[14:33] <ogra_> right
[14:37] <olli> so...
[14:37] <olli> sil2100, what about applying ted's "fix" from https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1394919
[14:38] <sil2100> olli: it will just fix the apport bit, but we'll still have cgmanager crashing
[14:38] <ogra_> olli, again ... this wont fix cgmanager ... who is responsible for the fix
[14:38] <olli> sil2100, does cgmanager recover after a crash
[14:38] <ogra_> no+
[14:38] <olli> ogra_, I understand that
[14:39] <ogra_> and because it doesnt we have the hang
[14:39] <olli> ogra_, so what made it worse
[14:39] <ogra_> and the ball on the original bu was dropped a month ago
[14:39] <olli> it seemed to have been fine around the RC image
[14:39] <ogra_> olli, for me it was never better or worse
[14:39] <olli> "fine" as in not noted that frequently
[14:39] <sil2100> From what ogra_ says, it was never better
[14:39] <sil2100> Which is a bit strange
[14:39] <pmcgowan> ogra_, is there something in particular that triggers it?
[14:39] <ogra_> tedg made it more visible in /var/crash, thats all
[14:39] <sil2100> QA mentions they noticed it getting worse since last week
[14:40] <ogra_> sil2100, yes, because the look at it more closely now
[14:40] <sil2100> Maybe
[14:40] <ogra_> sil2100, it only shows up after 4-6h of constant use of the phone
[14:40] <ogra_> nobody in QA does that except when dogfooding
[14:40] <sil2100> davmor2: did you see that constantly? ^
[14:41] <ogra_> pmcgowan, we dont know ... the data we need for this was never collected in the original bug
[14:41] <olli> ogra_, sil2100 as you might have noticed, I added an appointment in 50min to fix the plan, if we haven't done so by then
[14:41] <ogra_> pmcgowan, i enabled what hally asked for and run my phone like this now ...
[14:41] <sil2100> In any case, I see a lot of people are now trying to gather as much info as they can
[14:41] <olli> any ping from hallyn yet this AM?
[14:42] <jibel> ogra_, I did too this morning, but I cannot reproduce the problem since I enabled it
[14:42] <ogra_> olli, i pinged in #ubuntu-devel but didnt get any reply
[14:42] <olli> so, to get it right...
[14:42] <ogra_> jibel, well, perhaps thats our workaround ;)
[14:42] <olli> ogra_, you are saying the fix for https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1377332 never fixed the actual issue
[14:43] <ogra_> it will massively produce log spam though
[14:43] <ogra_> olli, there was never a fix
[14:43] <davmor2> pmcgowan: I only saw it once or twice, jibel has seen more I think and popey
[14:43] <jibel> I hit the problem twice yestarday but cannot find how
[14:43] <ogra_> olli, only quietening of the symptom ... see the cgmanager task
[14:44] <ogra_> jibel, i hit it since a month and cant ... usually only on weekends though
[14:44] <ogra_> this weekend i packaged a lot of new webapp games and tested them ... probably playing a lot is the right way to repro :)
[14:45] <olli> sil2100, ogra_, so while I agree that the cgmanager crash is bad
[14:45] <olli> we really have 2 issues to deal with again
[14:46] <olli> the apport one which was revealed by the fix for ^ bug
[14:46] <olli> and then the actual crash
[14:46] <ogra_> the apport bit is ignorable atm
[14:46] <brendand_> sil2100, it makes things better but still not perfect
[14:47] <jibel> the apport crash is minor
[14:47] <ogra_> olli, if cgmanager is fixed (which must happen) there wont be an apport issue
[14:47] <jibel> it's just a stacktrace that says it cannot collect information about the process
[14:47] <olli> ogra_, I agree that we need to fix it
[14:47] <olli> .oO(not sure for GM though)
[14:48] <olli> jibel, so the user impact on 1394919 is none
[14:48] <olli> just traces in /var?
[14:48] <ogra_> olli, well, you have apport trying to collect info and it makes the device slow
[14:49] <ogra_> close to unresponsible
[14:49] <jibel> olli, yes it's none
[14:49] <olli> so we should consider taking ted's latest patch which will disable the apport invocation
[14:49] <olli> ogra_, ^
[14:49] <ogra_> the point is still, we cant release with cgmanager in the state it is currently
[14:49] <jibel> ogra_, not even because apport stops immediatly since it crashes
[14:49] <pmcgowan> jibel, any idea how frequent this is?
[14:49] <ogra_> we either roll back cgroup support completely (which rips out cgmanager)
[14:50] <ogra_> or we find a fix *now*
[14:50] <olli> ogra_, it was good enough for RC, wasn't it
[14:50] <sil2100> I think we cannot get that... and getting a fix might also prove to be a bit troublesome
[14:50] <ogra_> olli, with that original bug open as topblocker
[14:50] <jibel> pmcgowan, no, that's the problem. We cannot find a way to reproduce and the symptoms are so vague that it's difficult to know if it is the same bug when it happens
[14:50] <ogra_> yes, it was
[14:50] <pmcgowan> jibel, ack
[14:50] <olli> thx jibel
[14:50] <pmcgowan> if I see recoverable problem in /var/crash did I exprience hte issue?
[14:51] <sil2100> olli: so, the biggest problem is as I mentioned: it basically means that one of our topblocker is still open and not fixed ;/
[14:51] <ogra_> pmcgowan, yes
[14:51] <pmcgowan> so I got it yesterday first time then
[14:51] <olli> sil2100, that's OK
[14:51] <ogra_> pmcgowan, at least UAL thinks you did and tols apport to collect info
[14:51] <ogra_> *told
[14:51] <jibel> pmcgowan, if the pid in the stacktrace corresponds to cgmanager, then you are experiencing the same problem
[14:51] <olli> if we can't easily reproduce then we might want to rethink whether this bug classifies as topblocker
[14:51] <ogra_> olli, imho we should roll back cgroup support
[14:52] <olli> ogra_, what was the bug for that?
[14:52] <sil2100> I'm not sure if that's an option...
[14:52] <olli> that might be another option
[14:52] <ogra_> olli, bug 1377332
[14:52] <olli> but I think that's quite invasive to do until tomorrow
[14:52] <sil2100> In the time we were getting cgroup support in, I remember this being labelled as 'required for RTM'
[14:52] <ogra_> right
[14:52] <olli> ogra_, that's not cgroup support is it
[14:52] <ogra_> it is an essential part of the lifecycle mgmt
[14:53] <olli> I thought cgroup support came in to lifecycle manage webapps
[14:53] <olli> which iirc was a different bug
[14:53] <ogra_> olli, that was the bug that caused cgroup support to be rolled back
[14:53] <ogra_> was it ?
[14:53] <pmcgowan> ogra_, are we waiting to repro with debug enabled right now?
[14:53] <ogra_> oh, right, there was one before ... this one bubbled up right after croup support finally landed then
[14:53] <ogra_> i cant find it though
[14:54] <ogra_> pmcgowan, well, thats my only idea beyond ... well... findin hallyn to give us better ideas
[14:55] <brendand_> sil2100, can we land it and then deal with the other issues seperately?
[14:56] <sil2100> brendand_: I suppose, if you give it a QA sign-off then I'm +1 on that ;)
[14:58] <sil2100> brendand_: thanks! Let me close my eyes now and publish ;D
[14:59] <ogra_> *boom*
[14:59] <ogra_> :)
[15:02] <sil2100> popey: hey! If you're still around: would you mind if I release a new .deb version of reminders-app now? This will basically commit one additional commit to trunk with the debian/changelog etc.
[15:03] <sil2100> dpm_: hello, maybe you're around and could answer the above question? ^
[15:13] <popey> sil2100: speak to dpm
[15:13] <popey> <- on airport wifi
[15:13] <sil2100> popey: did that, thanks :)
[15:13] <popey> coolio
[15:14]  * ogra_ recommends "cartoon flight" for airports 
[15:14] <popey> is it in the store?
[15:15] <ogra_> sure
[15:15] <popey> ooh thats fun
[15:15] <ogra_> :)
[15:15] <ogra_> i love the graphics
[15:17] <dpm_> sil2100, if we release a .deb version of reminders now, will it affect in any way the app that's in the store? Or the authentication plugin?
[15:17] <dpm_> sil2100, I guess not, as none of the packages are installed from the seeds, but I'd like to be extra sure
[15:18] <sil2100> dpm_: I think it won't affect anything besides tests, as I checked that none are installed anywhere - but I was poking you guys to make sure about that :)
[15:18] <sil2100> As I only see how it looks like from the rootfs's POV
[15:21] <dpm_> sil2100, essentially, we don't need any packages from reminders-app for the app to work. The .deb packages are only there to make Jenkins happy
[15:21] <sil2100> dpm_: ok, so I guess it's fine to release this then I suppose
[15:22] <sil2100> Thanks!
[15:22]  * sil2100 presses publish
[15:22] <dpm_> sil2100, given the caveat above I'd think it's safe, yes
[15:26] <AlbertA> sil2100: hi I'm here...so mir is stuck?
[15:28] <popey> ogra_: ever have a situation where lock screen, apps and indicators respond to touch events but the shell doesn't?
[15:28] <sil2100> AlbertA: hey, yeah... there's an issue with mir-graphics-drivers-android as it seems to be an 'any' package, while its dependencies are built only for selected architectures
[15:28] <ogra_> popey, i had that too before, yes
[15:28] <ogra_> popey, any crash files ?
[15:28] <popey> had it today
[15:29] <sil2100> AlbertA: e.g. libmirplatform4driver-android and libmirclient8driver-android  only build for certain archs, and are missing arm64 binaries in this case
[15:29] <AlbertA> sil2100: right....
[15:29] <popey> only one for location service
[15:30] <pmcgowan> popey, I had the dash disappear the other day while launcher and indicators were there, maybe similar
[15:30] <AlbertA> sil2100: ok we'll fix it...
[15:30] <popey> and not at the right time
[15:30] <sil2100> AlbertA: we can re-release it from the same silo, so just push your changes to the same place and rebuild
[15:30] <popey> also, had osk not coming up in g+ when writing a comment
[15:30] <popey> had to switch to terminal to bring it up and switch back again
[15:31] <popey> no amount of stabbing G+ would bring it up
[15:31] <AlbertA> sil2100: ack
[15:32] <popey> bfiller: ever get green picture when taking photos on krillin?
[15:32] <popey> known issue?
[15:33] <popey> i took two pictures, first was fine, next was solid green with some jpeg style corruption in top left
[15:33] <bfiller> popey: weird, no. Kaleo ^^^?
[15:34] <popey> sergiusens: can we please get that wording changed in the indicator notifications "You have an approximate of 15 unread messages" makes my teeth itch every time I see it ☻
[15:48] <sil2100> AlbertA: thanks!
[15:59] <Kaleo> bfiller, popey, never seen that nor heard of it
[16:07] <sergiusens> popey: oh, if you get all the paperwork done, sure ;-)
[16:07] <sergiusens> popey: or for vivid?
[16:08] <sergiusens> popey: I do risk breaking all the translations for rtm though; not sure that's desirable
[16:11] <bzoltan> Mirv: sil2100: The oneliner fix for qtbase in silo2 is good. I have checked the binary strings. It is good to land.
[16:12] <bzoltan> Mirv: sil2100: ...and may I ask for a silo for line 47?
[16:24] <sil2100> brendand_: do you have a vivid device as well?
[16:25] <sil2100> Oh, you tested it on vivid too
[16:25] <sil2100> Sorry, missed that part, let me publish
[16:26] <dbarth> hi trainguards: we have silos 25 & 29 ready to publish now
[16:26] <sil2100> dbarth: o/
[16:26] <sil2100> bzoltan: o/
[16:29] <sil2100> dbarth: can you top-approve the merges in 29?
[16:31] <sil2100> ogra_: can I ask you for a packaging ACK for webbrowser? It's only a dependency bump: https://ci-train.ubuntu.com/job/ubuntu-landing-025-2-publish/10/artifact/packaging_changes_webbrowser-app_0.23+15.04.20141121-0ubuntu1.diff
[16:32] <dbarth> sil2100: yes
[16:32] <sil2100> dbarth: thanks, give a sign when I can re-run
[16:32] <dbarth> sil2100: done
[16:32] <ogra_> sil2100, ACK (if it was made sure it doesnt break apps in the store to bump this indeed)
[16:33] <brendand_> tvoss, where's the trust db again?
[16:34]  * ogra_ has it here in a bag ... but wont tell you :P
[16:35] <tvoss> brendand_, ~/.local/share/UbuntuLocationService/trust.db
[16:44] <sil2100> brendand_: btw. did you have a moment to take a look at dialer AP tests?
[16:44] <brendand_> sil2100, yeah they are not reproducible really
[16:45] <brendand_> sil2100, i ran 20 times and got 1 (different) failure
[16:45] <sil2100> wow
[17:53] <zsombi> timp: I've added action press highlight and fixed the listitem highlight, I have two unit tests failing, I have to address those. Pls review the changes and I will add the tests tomorrow
[17:53]  * zsombi goes off now, C U tomorrow
[18:16] <sil2100> ogra_: re: the adbd change you announced - any luck with the #1387214 adbd part? :)
[18:16] <ogra_> sil2100, i'll hopefully get to that tomorrow when i'm not in meetings til the middle of the night :P
[18:16] <sil2100> ;p
[18:16] <ogra_> sil2100, but thats a corner case and can also wait til ota-1
[18:17] <sil2100> Sure, we won't risk it for GM, but asking out of curiosity
[18:17] <ogra_> the current setup will shield us from the brakage it could cause ... it is juts a "potential breakage"
[18:17] <ogra_> sil2100, though ... i could sneak it in while distracting olli with something else :)
[18:18] <sil2100> Let's wave some topblockers in front of him and land it from the shadows!
[18:18] <ogra_> yeah :)
[18:37] <olli> yeah, I'll be busy reading the patches
[18:37] <olli> I mean writing...
[18:37] <olli> :P
[18:38] <ogra_> hah
[18:41] <sil2100> alex-abreu: ping
[18:42] <alex-abreu> sil2100, pong
[18:43] <sil2100> alex-abreu: hey! I have been looking at the packaging changes for silo 29
[18:43] <sil2100> alex-abreu: and I have a question
[18:43] <alex-abreu> sil2100, yes
[18:44] <sil2100> alex-abreu: unity-webapps-qml has this: "+Depends: liboxideqt-qmlplugin (>= 1.2.0) | qml-module-qtwebkit," <- does this mean that this package is backward compatible and will still work with qml-module-qtwebkit?
[18:44] <alex-abreu> sil2100, yes
[18:44] <sil2100> ACK
[18:44] <sil2100> ogra_: hey, have a minute for a packaging ACK? ;)
[18:45] <ogra_> sure
[18:46] <sil2100> ogra_: https://ci-train.ubuntu.com/job/ubuntu-landing-029-2-publish/lastSuccessfulBuild/artifact/packaging_changes_unity-webapps-qml_0.1+15.04.20141122-0ubuntu1.diff <- qml bindings changed to support oxide, but is backward compatible still
[18:49] <bzoltan> sil2100: is everything OK with the silo2?
[18:52] <bzoltan> thanks sil2100
[18:52] <sil2100> bzoltan: sorry it took so long, I thought Mirv had that on his radar :)
[18:52] <sil2100> (but I guess it was too late already)
[18:53] <om26er> rsalveti, Hi I am almost done testing the pulseaudio silo. Is there something to look out for (except for whats mentioned in spreadsheet) ?
[18:53] <bzoltan> sil2100:  no worries... I am pushing it because it might be critical fix for those rare users who use i386 desktop
[18:53] <om26er> rsalveti, whats the regression potential ?
[18:54] <rsalveti> om26er: no, besides checking that pulse is indeed not consuming much cpu after the app goes to background, just exploratory tests (audio related)
[18:54] <bzoltan> sil2100: If there is an available silo I could use it for line 47 and tomorrow i could start landing there the UITK too
[18:54] <rsalveti> om26er: it changes a core piece in pulse, but the side effect would be that a stream could be muted when it shouldn't
[18:55] <rsalveti> so if, for whatever reason, you can't play an audio, let me know
[18:55] <om26er> sounds scary
[18:55] <rsalveti> just playback, not recording
[19:17] <om26er> rsalveti, approved. One a sider note it seems like we could easily automate the role verification tests from the pulseaudio with a little bit of effort.
[19:18] <om26er> Perhaps something to consider for the near future.
[19:19] <rsalveti> om26er: which ones exactly?
[19:20] <rsalveti> if from https://wiki.ubuntu.com/Process/Merges/TestPlan/pulseaudio, yeah
[19:20] <rsalveti> just need a real hardware
[19:20] <om26er> rsalveti, yes, those.
[19:20] <rsalveti> but creating a test script at least should already help indeed
[19:21] <om26er> yeah, just attach to the wiki and the tester could execute that.
[19:21] <om26er> I might try to put something together if I get sometime.
[19:22] <rsalveti> cool, yeah, that is doable
[19:28] <sil2100> ogra_: hmmm, and my e-mail still didn't appear in the archive... not even in the date.html one
[19:28] <sil2100> This is ridiciulous
[19:29] <ogra_> mine didnt either
[19:29] <ogra_> (the announcement for adb)
[19:29] <ogra_> but looks like i have a nightshift ahead anyway
[19:29] <ogra_> rolling back all these changes
[19:29] <sil2100> Which changes?
[19:30] <ogra_> adbd
[19:30] <sil2100> Right, ouch
[19:42] <rsalveti> ogra_: publishing silo 2 then
[19:42] <rsalveti> guess we want a new image after that is in
[19:42] <rsalveti> olli: ^
[19:43] <ogra_> yeah, i'll take care
[19:43] <olli> rsalveti, nice
[19:44] <sil2100> o/
[19:46] <sil2100> ogra_: btw. I know you're busy now, just a quick question - did you have a time for that quick packaging ACK I asked 1h ago? :)
[19:46] <ogra_> sil2100, oops
[19:47] <ogra_> sil2100, this is weird, i'm sure i answered but i dont see it above
[19:48] <sil2100> ogra_: I know you +1ed one earlier packaging ACK, but I poked about another one ;)
[19:48] <ogra_> oh
[19:48] <ogra_> sil2100, ack then
[19:49] <ogra_> (seems to be the same in a different package :P )
[19:50] <sil2100> :D
[19:50] <sil2100> Thanks!
[19:50] <sil2100> (I also sanity-checked it, but formalities are formalities!)
[19:57] <olli>  ogra_, are we building the next image with just the pulse fix
[19:58] <ogra_> olli, yes, once it landed
[20:32] <ogra_> image build triggered ...
[20:34] <imgbot> [20:52] <bfiller> robru: can I have a silo for line 48 please?
[20:53] <robru> bfiller: alright, vivid 7
[20:53] <bfiller> robru: thank you
[20:53] <robru> bfiller: you're welcome
[21:32] <robru> tvoss: vivid 11
[21:33] <tvoss> robru, thanks
[21:34] <robru> tvoss: you're welcome
[21:41] <robru> mandel: vivid 15
[21:42] <mandel> robru, silo 15 you mean?
[21:42] <mandel> awesome
[21:42] <robru> mandel: yeah
[21:43] <robru> mandel: a little shorthand since I have to type that like 50 times per day ;-)
[21:43] <mandel> robru, no problem, I was missing just a little context :)
[21:49] <imgbot> [21:50] <imgbot> [21:50] <ogra_> olli, ^^^one for you
[21:50] <olli> nice!
[21:50] <olli> happy testing
[21:51]  * ogra_ waits for the upgrade-notification on his phone ... 
[21:51] <bzoltan> robru:  the silo5 is good to go
[21:54] <bzoltan> robru:  I see on the http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html that the qtbase is "regressing" on kdeplasma-addons. That is nonsense :) this change is a single line change what can not effect the kde package.
[21:54] <cjwatson> bzoltan: Looks like flaky testbed issues.  I'll retry
[21:54] <bzoltan> robru: This is the delta in qtbase http://launchpadlibrarian.net/191089972/qtbase-opensource-src_5.3.2%2Bdfsg-4ubuntu5_5.3.2%2Bdfsg-4ubuntu6.diff.gz
[21:55] <bzoltan> cjwatson: Thank you
[21:55] <robru> cjwatson: yeah I was just gonna say. thanks.
[21:57] <cjwatson> Was just passing.  I should be a good boy and go away again
[22:05] <popey> I'm trying to summon up the energy to file the 14 bugs I found on the flight over here
[22:07] <ogra_> bah
[22:08] <ogra_> upgrade and my location indicator is gone
[22:08]  * ogra_ blames rsalveti ... since pulse was the only thing landing in this image
[22:11] <ogra_> hmm, and the indicator was actually correct ... GPS was disabled
[22:22] <bzoltan> robru: May i ask for a reconf on the silo16? I have just added the -gles twin package what comes from a different project.
[22:23] <robru> bzoltan: sure one sec
[22:23] <bzoltan> robru:  thanks
[22:24] <robru> bzoltan: done. you're welcome!
[22:36] <rsalveti> ogra_: haha, indicator might be talking with gps via sound or something
[22:36] <ogra_> ah, you mean thats the weird sounds i hear at boot ?
[22:36] <ogra_> :)
[22:37] <ToyKeeper> Er, I get beeps and clicks and buzzes from my stereo speakers whenever a krillin is nearby and trying to use cell data...  but I don't otherwise tend to hear weird sounds from it.
[22:37] <ogra_> yeah, i was joking, no worries, no new bugs :)
[22:39] <rsalveti> :-)
[22:42] <ToyKeeper> It does have a curiously strong magnet inside...  I wonder if that'll change for production units, to avoid wiping credit cards and such.
[23:16] <michi> cihelp: Anyone around to look at Jenkins for me?
[23:19] <michi> cihelp: Apparently not.
[23:20] <michi> cihelp: cloud-worker-08 has had problems since yesterday.
[23:20] <michi> cihelp: It runs unbelievably slowly, taking ages to compile anything. My arm build finishes buliding and testing *before* the same build finishes compiling on amd64.
[23:21] <michi> cihelp: cloud-worker-08 yesterday reported 4000 ms response time. Now, when I look, it says
[23:21] <michi> “Time out for last 1 try”
[23:23] <michi> cihelp: Could someone please take a look and fix it or take it off-line? Every time my build happens to get scheduled on that machine, things take well over two hours to finish. Normally, it takes about 20 minutes.
[23:26] <robru> michi: ok, I marked that one as offline. hope that helps until somebody is around to fix it for real.
[23:26] <michi> robru: thanks heaps!
[23:26] <robru> michi: you're welcome