[00:08] <cwayne_> rvr, thanks for catching
[00:08] <rvr> cwayne_: You're welcome
[00:20] <cwayne_> rvr, so would it just be Fotos de Telegram then?
[00:20] <rvr> cwayne_: Right
[00:52] <cwayne_> rvr, fix pushed, building image now
[00:52] <rvr> cwayne_: Ack
[01:18] <cwayne_> rvr, image ready for you tomorrow morning :)  ill flash now and give it a looksie
[01:19] <rvr> cwayne_: Oki doki! :)
[01:26] <cwayne_> rvr, looks good, please shoot me an email when it's ready (I'll start early tomorrow so I can push as soon as we're ready)
[01:26] <rvr> cwayne_: I just flashed it
[01:28] <rvr> Mis fotos de Facebook, that's +1
[01:28] <rvr> Now login in Telegram
[01:29] <rvr> Fotos de Telegram
[01:30] <rvr> Mensajes recientes
[01:30] <rvr> cwayne_: It's ok
[01:30] <cwayne_> :D
[01:30] <cwayne_> so what happens now, can I push, or do I need to wait for sil?
[01:31] <rvr> I don't know! :)
[01:32] <cwayne_> I guess I can't push without a +1 from someone on landing team..
[01:32] <rvr> To which channel is the image being pushed?
[01:33] <cwayne_> 14.09-proposed
[01:33] <rvr> robru: You there?
[01:33] <robru> rvr: hi
[01:33] <rvr> robru: ^
[01:34] <robru> rvr: what? Are you talking about a silo?
[01:34] <rvr> robru: cwayne_ wants landing team approval before pushing the proposed-customized image to 14.09-proposed
[01:35] <robru> rvr: cwayne_: well I'm not aware of any reason why not...
[01:37] <cwayne_> good enough for me
[01:37] <rvr> robru: cwayne_ will blame you if he breaks Internet ;)
[01:37] <cwayne_> rvr, just to double check, you checked the functioanlity and stuff earlier right? i.e. you weren't *just* testing i18n
[01:37] <robru> rvr: cwayne_ I'm a bit confused, are you talking about printing an image?
[01:38] <cwayne_> robru, 'promoting' the custom tarball, so it gets pulled into 14.09-proposed
[01:38] <rvr> cwayne_: Some minutes ago, I logged into Telegram, and checked that the photos and messages are displayed both in Today's scope and in Photos scope
[01:38] <cwayne_> from 14.09-proposed-customized
[01:39] <rvr> cwayne_: Earlier today, in previous images: «Exploratory testing with Today, NearBy, Photos, Telegram and Fitbit scopes. Logged in Facebook Photos, Telegram, FitBit, Instragram and Flickr. All of these are ok.Exploratory testing with Today, NearBy, Photos, Telegram and Fitbit scopes. Logged in Facebook Photos, Telegram, FitBit, Instragram and Flickr. All of these are ok».
[01:39] <robru> cwayne_: yeah I'm not really up to speed with those kinds of decisions... Maybe check with pmcgowan if you really need some kind of approval.
[01:40] <cwayne_> rvr, ah great, and the only things that've changed since then is translations, great
[01:40] <rvr> cwayne_: You can leave an email to sil2100 and jibel for tomorrow if you prefer
[01:40] <rvr> cwayne_: I guess sil2100 can promote from one channel to another, right?
[01:40] <rvr> And that's a quick process, isn't it?
[01:42] <cwayne_> yeah it's very quick, I'll just shoot an email to sil and do it tomorrow morning, should've gotten a +1 from sil earlier, but oh well
[01:46] <rvr> Time to sleep, see you tomorrow!
[02:10] <imgbot> [03:40] <imgbot> [03:40] <imgbot> [04:11] <robru> veebers: ah, no vivid silos available at the moment. I sent an email asking people to clean up some silos that seemingly aren't being used, hopefully one will free soon
[04:12] <veebers> robru: ack, thanks :-) I'll make sure the rest of the team is aware so that when possible we start testing (once we get a silo)
[04:19] <veebers> robru: hmm, when I tried to close the spreadsheet page it complained that some data might not get saved, also while filling out the row it also complained a couple of times about fatal errors
[04:19] <veebers> do I need to double check anything?
[04:19]  * veebers eyeballs the row
[04:19] <veebers> seems good to me
[04:19] <robru> veebers: yeah i just got that as well, it seems the spreadsheet is imploding again. Not much we can do
[04:21] <veebers> ack, thanks robru. As long as it wasn't my fault :-)
[04:21] <robru> veebers: nope, this is well known pain and misery
[04:21] <robru> veebers: you're welcome
[07:17] <dbarth_> good morning trainguards; i have an oxide 1.5.6 release update on line 64
[07:18] <seb128> hey there, is there any plan to free vivid silos?
[07:39] <Mirv> dbarth_: seb128: we're still out of silos and 5 lines waiting for silo
[07:40] <seb128> Mirv, right, hence my question
[07:42] <seb128> Mirv, we have several dirty silos and experimental ones (like the new qt)
[07:42] <seb128> maybe some can be reclaimed to make space for pending landings?
[07:44] <Mirv> 3 of the waiting ones are ubuntu-system-settings while there's already 006 with u-s-s too. I wonder if any of those could be combined.
[07:44] <seb128> Mirv, oh, in fact 11 seems available, maybe it can be assigned :-)
[07:44] <Mirv> seb128: not without pinging, and with yesterday's poll none could be relieved.
[07:44] <Mirv> seb128: yes, I'm trying to assign that to the next one in queue
[07:44] <Mirv> spreadsheet is acting up
[07:45] <seb128> Mirv, well, settings is only in 1 by itself, the other 2 silos it's in that's part of a transition/bigger changes
[07:45] <seb128> in fact it's only in 2
[07:45] <Mirv> seb128: yes, but there are also 2/3 (2 set to ready) pending landings of u-s-s
[07:46] <Mirv> I just mean that there's a bottleneck in landing those fixes as they go in one after another
[07:46] <Mirv> not in terms of silo usage but simply that it takes maybe too much time to get all of those in
[07:46] <sil2100> hmm
[07:47] <sil2100> I wonder is silo 004 is still needed
[07:47] <seb128> Mirv, oh right, but landing are limited nowadays right? like we need an approval for fixes and QA verification, can't just batch a stack of bugfixes and get that in easily...
[07:48] <Mirv> sil2100: I think that could be a good candidate for freeing even without asking, since it's cheap to rebuild
[07:48] <Mirv> seb128: yes sure if not all of those are on the vivid milestone bug list they'd need separate approvals.
[07:48] <seb128> Mirv, need to check with jgdx and kenvandine
[07:49] <sil2100> We might need to poke some release team members about the UNAPPROVED silos I guess
[07:49] <Mirv> sil2100: we could also have 10 sru silos... :)
[07:50] <seb128> Mirv, then you would ping the SRU team ;-)
[07:50] <seb128> speaking of which, I've a trusty SRU, I'm pondering doing out of the CI due to that
[07:50] <Mirv> I mean, SRU silos could have a separate quota since they tend to keep on the silos for a longish time (approval + minimum 7 days in -proposed)
[07:53] <Mirv> pinged #ubuntu-release on the unapproved ones. compiz and unit have been there for 3+ weeks
[07:56] <seb128> right
[07:59] <Mirv> sil2100: fatal errors dance in the spreadsheet again, but some changes possible
[07:59] <Mirv> bfiller: cleaning 004 for now, ubuntu-keyboard build copied to ppa:canonical-qt5-edgers/qt5-proper
[08:07] <sil2100> Mirv: oh no...
[08:07] <sil2100> Mirv: that's too soon!
[08:09] <Mirv> dbarth_: ^ copied and silo status refreshed
[08:09] <sil2100> I give up, I have no idea what now caused the spreadsheet to go wild again
[08:09] <sil2100> There's not so many users even
[08:11] <dbarth_> Mirv: yup; seen that; thank you!
[08:13] <sil2100> Yeah, officially since 3 in the night the spreadsheet is not refreshing again
[08:19] <sil2100> This is bullshit, we only had a week of peace from those issues
[08:20]  * sil2100 is disabling stuff again
[08:51] <Mirv> thanks to infi_nity for reviewing the unapproved queue for us
[08:51] <Mirv> immediately it'll help with getting only 1 silo since those trusty SRU:s will be in the SRU queue for at least 7 days
[09:12] <sil2100> jibel, ogra_, Mirv, davmor2: how about I kick a new image now?
[09:12] <ogra_> go for it
[09:12] <jibel> sil2100, +1
[09:13] <sil2100> Actually not sure if we had anything landing inbetween, would have to check, but I think I remember some changes happening
[09:13] <sil2100> And this way maybe I'll force the importer to use the new custom
[09:14] <jibel> sil2100, new unity8 to fix a GPS issue
[09:15] <jibel> with the new custom tarball, I think that's all
[09:16] <Mirv> no problem
[09:20] <imgbot> [09:25] <popey> sil2100:  you have mail :)
[09:27]  * davmor2 deletes said mail
[09:30] <sil2100> popey: thanks! Will add it in a few moments
[09:40] <sil2100> Mirv: either google stopped reporting errors to me or the time-driven scripts stopped erroring-out
[09:41] <sil2100> Which might be a good sign
[09:42] <Mirv> hmm
[10:07] <cwayne_> sil2100, hiya
[10:07] <sil2100> cwayne_: hey! :)
[10:07] <sil2100> cwayne_: I see it picked up the tarball now
[10:08] <sil2100> cwayne_: took much longer than I expected, especially that the importer is running every 5 minutes
[10:08] <cwayne_> sil2100, \o/ its supposed to be all automagic so that;s good
[10:08] <sil2100> But yeah, it happened automagically
[10:08] <cwayne_> sil2100, weird, it's often done in a matter of minutes
[10:08] <sil2100> Thanks again :)
[10:08] <cwayne_> unless it;s doing something else which is taking its time
[10:09] <cwayne_> sil2100, np, sorry for all the troubles
[10:11] <cwayne_> sil2100, let me know if there's any other issues and I'll get em fixed
[10:11] <cwayne_> in the meantime, 6am calls for coffee
[10:14] <sil2100> cwayne_: go back to sleep! :)
[10:15] <sil2100> hmmm
[10:16] <sil2100> ogra_: image build 265 seems to have finished on the cdimage side
[10:16] <ogra_> thats good :)
[10:17] <ogra_> ogra@nusakan:~$ ps ax|grep import
[10:17] <ogra_> 13887 ?        Ss     0:00 /bin/sh -c TMPDIR=/srv/system-image.ubuntu.com/tmp /srv/system-image.ubuntu.com/bin/import-images
[10:17] <ogra_> 13894 ?        R      1:33 /usr/bin/python /srv/system-image.ubuntu.com/bin/import-images
[10:17] <ogra_> 24979 pts/5    S+     0:00 grep --color=auto import
[10:17] <ogra_> import-images only runs since 1:33 :)
[10:17] <ogra_> patience ;)
[10:18] <sil2100> I was worried something got b0rken ;p
[10:18] <sil2100> Thanks for checking
[10:24] <oSoMoN> ubuntu-qa: any chance silo 27 will be signed off today?
[10:25] <sil2100> jibel, davmor2, rvr: ^ ?
[10:25] <rvr> oSoMoN: I'll take it right now
[10:26] <davmor2> rvr: nice one
[10:26] <sil2100> ogra_: seems the importer is slowich today
[10:27] <ogra_> not really
[10:27] <ogra_> it usually takes 30min +
[10:28] <oSoMoN> rvr, awesome, thanks!
[10:50] <imgbot> [10:50] <imgbot> [10:50] <ogra_> there you go :)
[10:54] <sil2100> Phew
[10:55] <sil2100> Somehow today I'm really impatient
[11:06] <sil2100> Ok, I drive out for lunch now
[11:06] <sil2100> o/
[11:07] <brendand> sil2100, veebers made a request to get a vivid silo for autopilot yesterday, apparently there were none free. do you know anything?
[11:38] <Mirv> brendand: no such request is visible on the spreadsheet at least. we're constantly out of silos despite constant attempts to free them... currently 1 free
[12:05] <brendand> Mirv, oh - hope it didn't get lost
[12:13] <Mirv> brendand: there's nothing regarding autopilot on the spreadsheet unfortunately, but we also haven't heard reports yet of anything being magically removed on the new(est) spreadsheet.
[12:14] <Mirv> oh well
[12:14] <Mirv> oh well
[12:14] <Mirv> until now
[12:14] <Mirv> sil2100: backups..?
[12:14] <ogra_> hiccups rather
[12:14] <Mirv> brendand: my check up was anyway _before_ it now started resetting itself :D
[12:15] <Mirv> ogra_: also resetted to yesterday
[12:16] <Mirv> although it errors out constantly and reloads so it's hard to say. but from sil2100's backups it will be possible to restore the lines once the spreadsheet is even somewhat functional.
[12:16] <ogra_> yesterdays hiccups then :)
[12:16] <ogra_> we are trapped in a time loop !!!
[12:32] <jibel> sil2100, Mirv I approved line 53 3 times but the spreadsheet doesn't want it. Can you publish? silo 005/address-book-app
[12:32] <pmcgowan> jibel, sil2100 everything good? will be offlie for a bot
[12:32] <pmcgowan> bit
[12:36] <jibel> pmcgowan, we are waiting on a device tarball to trigger a new build which will be our promotion candidate. It won't include the touch panel fix.
[12:36] <pmcgowan> jibel, thats too bad
[12:37] <pmcgowan> ok
[12:38] <john-mcaleely> jibel, sil2100 I've pushed the brightness tarball you +1'd
[12:38] <jibel> pmcgowan, we'll start testing if the touch panel fix can land before tomorrow we can always respin an image with the fix
[12:38] <jibel> john-mcaleely, thanks
[12:38] <john-mcaleely> device_krillin-20150331-b430246.tar.xz
[12:38] <Mirv> jibel: sure
[12:38] <pmcgowan> john-mcaleely, any eta on the panel fix?
[12:38] <john-mcaleely> pmcgowan, working on it now. not clear if it's an hour or a day
[12:39] <pmcgowan> ok
[12:40] <ogra_> pmcgowan, for how long will you be offline ?
[12:41] <ogra_> pmcgowan, ycheng did set up a meeting about the OTA stuff we discussed yesterday ... in 20min ... i was about to ask if you could participate
[12:41] <pmcgowan> ogra_, well I am double booked then but I can try
[12:41] <pmcgowan> ogra_, changing my offline plan then
[12:54] <sil2100> \o/
[12:55] <sil2100> Mirv: yeah, it seems it started being broken again
[12:55] <sil2100> It seemingly worked from 12:30 till 14:15, now I again get error logs from google on every timed event
[13:00] <jibel> sil2100, can you trigger a new build with the device john-mcaleely pushed so we can start testing?
[13:00] <jibel> device tarball*
[13:03] <jibel> sil2100, nm, it's 266
[13:03] <sil2100> jibel: it should automatically create the new image, but it might take the importer a few moments to pick it up
[13:03] <sil2100> I thought it's instant, but sometimes it can take a few minutes
[13:04] <jibel> sil2100, actually it was pretty fast and thought it didn't build yet
[13:04] <jibel> sil2100, so 266 is the candidate for now
[13:04] <sil2100> Strange, since I have waited for the custom tarball to appear for like 15 minutes
[13:04] <sil2100> Yeah
[13:05] <sil2100> I heard the news about the device tarball, indeed no need to wait for it to start testing
[13:05] <sil2100> Too much time would be wasted
[13:07] <sil2100> Mirv: sometimes I feel as if all these spreadsheet problems don't have anything to do with our actual trigger-scripts, but actually related to the number of people viewing the spreadsheet
[13:07] <sil2100> Mirv: when the spreadsheet got better today, I saw there were only 5 people using it - now it was around 9
[13:08] <sil2100> Mirv: I suppose google spreadsheet syncs combined with the triggers and formulas leads to the backend breaking
[13:10] <Mirv> something like that..
[13:14] <jibel> trainguards you can publish ubuntu/silo-001 approved yesterday
[13:15] <davmor2> rsalveti, Mirv, sil2100: silo9 pulse corking good to go incase there is an issue with SS still
[13:16] <sil2100> jibel: ah, ok, let me publish then
[13:16] <sil2100> davmor2: same here :)
[13:19] <sil2100> ogra_: can you +1 a packaging change for me? There's no mention of the recommends-addition in the changelog, but I suppose it's less serious than not mentioning dep-changes: https://ci-train.ubuntu.com/job/ubuntu-landing-001-2-publish/98/artifact/indicator-power_packaging_changes.diff
[13:20] <ogra_> sil2100, ACK, looks fine
[13:21] <sil2100> Thanks :)
[13:21] <sil2100> jibel, davmor2: both silos are publishing
[13:22] <ogra_> why does a silo from a core dev need manual acking ?
[13:22] <ogra_> (referring to the last queuebot msg)
[13:23] <davmor2> ogra_: because a woodchuck could chuck wood?
[13:23] <ogra_> would a woodchuck chuck wood if it could ?
[13:24] <davmor2> ogra_: wait no, take their hats off, no that is popes in a beetle, the answer will come to me at some point
[13:25] <sil2100> ogra_: it's complicated
[13:26] <ogra_> davmor2, haha
[13:26] <sil2100> ogra_: we would have to either: 1) base that on who's set as the lander or 2) auto-analyse the changelog to make sure that the only change visible is made by a core-dev
[13:26] <ogra_> well, 2 would be nice in general :)
[13:27] <sil2100> In case of 1), this is a potential security leak as we would have to doublecheck that someone didn't simply include someone's else name in the field - with 2), well, it's work to implement that and I'm not sure it's a big deal without it ;)
[13:27] <davmor2> I love it all this work just fell into the abyss
[13:27] <sil2100> Since when I see a change made only by a core-dev I anyway override it and auto-approve
[13:28] <ogra_> sil2100, well, i'D already be happy if my changelogs wouldnt be reduced to the very last entry if i built my source package with -v ....
[13:28] <ogra_> i think our changelog handlin could need some love as a whole
[13:29] <ogra_> (but yeah, low prio task ... definitely)
[13:36] <seb128> hum
[13:36] <seb128> http://people.canonical.com/~platform/citrain_dashboard/ has a weird status for 024
[13:36] <seb128> it's a u-c-c desktop landing and status has "ready to build" but also "Migration: indicator-datetime is in the UNAPPROVED queue. "
[13:37] <seb128> the migration part is weird
[13:38] <seb128> gra, the "build" url is pointing to a wrong jenkins as well
[13:39] <seb128> or not
[13:39] <seb128> how confusing
[13:40]  * ogra_ doesnt see the queuebot pick up his rebuild of silo 19 :/
[13:41] <rvr> sil2100: About to approve silo 27
[13:42] <rvr> sil2100: "Note: requires a FFe, granted at bugs/1441232"
[13:43] <rvr> Looks good
[13:43] <rvr> Will the spreadsheet work?
[13:44] <rvr> The action you're trying to perform is causing a fatal error and cannot be performed.
[13:47] <seb128> grrrr
[13:48] <seb128> the CI table keeps hitting backend error and loosing edits
[13:48] <oSoMoN> trainguards: can silo 27 be published, please?
[13:56] <Mirv> oSoMoN: sure, trello is enough even if spreadsheet keeps resetting
[13:57] <Mirv> ogra_: core dev ack for https://ci-train.ubuntu.com/job/ubuntu-landing-027-2-publish/lastSuccessfulBuild/artifact/webbrowser-app_packaging_changes.diff ? are in main.
[13:58] <ogra_> oSoMoN, Mirv, NACK, please mention the added dependencies in the changelog
[13:59] <Mirv> ogra_: thank you for reviewing. it does make sense to enforce more directly describing the packaging changes.
[14:00] <Mirv> folder list model is not mentioned at all, settings is mentioned but not that it adds a dep
[14:00] <oSoMoN> ogra_, I agree that it would be useful, but it should be automatically done by the CI train, now it’s going to take a rebuild just to add a line in the changelog…
[14:00] <ogra_> right, i warned that i would do this about 6 months ago ... and poked people about it for the last 6 months but still acked ... i think after 6 months it is now the time to expect it to be proper
[14:01] <Mirv> that would be a good feature request for train, filing
[14:04] <Mirv> bug #1441638 . cihelp, do you have some project to file future CI Train replacement feature requests under?
[14:08] <oSoMoN> Mirv, I updated the commit messages on the relevant MRs, I’ll trigger a rebuild of silo 27
[14:09] <Mirv> ok
[14:13] <pmcgowan> sil2100, 266 is building?
[14:16] <ogra_> pmcgowan, i think it is done
[14:16] <davmor2> pmcgowan: 266 is done
[14:16] <ogra_> was only a tarball update
[14:17] <pmcgowan> ah great
[14:17] <ogra_> (they are fast and not noticed by the bot)
[14:17] <sil2100> pmcgowan: yeah, QA is already testing it
[14:17] <pmcgowan> woot
[14:17] <ogra_> sil2100, any idea why the queuebot didnt pick up my watch-only rebuild of silo 19 ?
[14:22] <sil2100> ogra_: he might be a bit confused because of the spreadsheet reverting its state, but normally it shouldn't have any problems
[14:23] <jdstrand> cwayne_: fyi, apparmor-easyprof-ubuntu 1.3.10 on vivid uploaded (not sure if you are doing custom tarballs yet for vivid)
[14:25] <elopio> ping trainguards, any vivid silos available today to release autopilot?
[14:25] <sil2100> elopio: hey
[14:25] <sil2100> We currently have 2 free vivid silos
[14:26] <sil2100> We're not sure about the number of landing requests as the spreadsheet reverted itself to the state of last night
[14:26] <elopio> sil2100: can we get one of those to autopilot before somebody else take it?
[14:26] <sil2100> elopio: try filling in a request and I'll try assigning it to you
[14:27] <elopio> sil2100: ok.
[14:28] <seb128> sil2100, I've some pending, if you can try that as well :-)
[14:28] <sil2100> seb128: I see them now ;) Probably got reverted as well, right?
[14:29] <seb128> sil2100, yeah, some of them
[14:29] <sil2100> Sorry for the spreadsheet troubles again guys
[14:29] <seb128> not your fault
[14:32] <om26er> jibel, during silo 14 testing I found a regression. During flight mode, Not network or SIM lock, the app title becomes blank in the right edge switcher.
[14:32] <om26er> http://i.imgur.com/VGm6t5v.png
[14:32] <om26er> jibel, salem_ says they are aware of it and its something they can't fix right now
[14:33] <seb128> bfiller, you put a landing up for settings with the storage panel fix for arale, did you see that there was another landing request from jgdx in the list including that and some other fixes? would have been nice to picked the other fixes as well rather than superseeding with a more limited set
[14:33] <om26er> jibel, I have blocked the landing, what do you say ?
[14:35] <jibel> om26er, it is a regression introduced by the silo?
[14:35] <om26er> jibel, yes it is.
[14:36] <salem_> jibel, hi, so, the original problem is that apps can be sigpaused at any time, and in this specific case, dialer will be frozen with a certain header title that might not reflect the current state anymore when you invoke the carousel with a right-> left swipe
[14:36] <jibel> om26er, ok, so we land bug fixes, not new bugs when we find them. It's correct to reject
[14:36] <salem_> bfiller, ^
[14:39] <kgunn> Mirv: sil2100 ...hey, we can manage giving back silo 0
[14:40] <elopio> sil2100: added the autopilot row.
[14:40] <elopio> that was hard.
[14:41] <sil2100> elopio: yeah... let me refresh as I didn't see your row
[14:42] <elopio> yes, my nick disappeared. Filled now.
[14:42] <elopio> It seems I was fighting seb128 and dbarth_ on the spreadsheet.
[14:43] <sil2100> Yeah, the spreadsheet doesn't sync
[14:43] <elopio> cool :)
[14:46] <elopio> sil2100: after hitting build, I don't have to fill anything on jenkins, right? Last time I did this was long ago.
[14:47] <bfiller> seb128: no I didn't see that
[14:47] <bfiller> seb128: feel free to change, just trying to get this fix landed as it was on the arale list
[14:47] <seb128> bfiller, k, just a note for next time to maybe check pending requests then :-)
[14:48] <seb128> bfiller, well, now it's in a silo so I guess we can as well get the landing through
[14:48] <bfiller> om26er, jibel : I wouldn't say it's a regression
[14:48] <seb128> bfiller, but if somebody wants to include the other ones feel free
[14:48] <sil2100> elopio: nothing :)
[14:48] <bfiller> om26er, jibel : it's an expected change as there is no other way to solve the bug
[14:48] <sil2100> elopio: only if some special care is needed
[14:48] <bfiller> seb128: will do
[14:48] <elopio> ok, thanks.
[14:49] <seb128> bfiller, thanks
[14:51] <elopio> I don't really understand that.
[14:51] <om26er> bfiller, jibel it clearly looks like a regression, user drags from right edge and poof no title. I remember we still have issues on the design side as they are trying to show app icon in the right edge switcher. So now with no title in this case is a regression
[14:52] <sil2100> popey, ogra_, robru, davmor2, rvr: let's skip the evening meeting
[14:52] <ogra_> sil2100, +1
[14:52] <sil2100> elopio: this means that your trunk branch, so the branch to which you want to merge to, doesn't seem to have all the released versions merged
[14:52]  * ogra_ had/has enough meetings today, one less will be good :)
[14:52] <bfiller> om26er, jibel: a regression is something unintended. this was known and deemed an acceptable tradeoff to fix the bug at hand
[14:52] <sil2100> elopio: so probably someone released autopilot to the archive directly and didn't merge that back to trunk
[14:53] <sil2100> Or at least didn't merge the changelog
[14:53] <bfiller> om26er, jibel : I agree it's not ideal, but better than showing the wrong state when the app is brought to the foreground which is the case today
[14:53] <davmor2> the cancelmonger strikes again +1 though :)
[14:53] <om26er> its a regression until approved by design IMO.
[14:53] <sil2100> davmor2: ;)
[14:54] <rvr> sil2100: Ack
[14:54] <sil2100> robru: just so you know - spreadsheet b0rken againz
[14:54] <cwayne_> jdstrand, ack, thank you, will kick a vivid build
[14:56] <elopio> sil2100: I'm looking at the 1.5 branch, that's what we release. It seems I filled the wrong branches. Trying again now.
[14:56] <popey> sil2100: ok
[14:57] <dbarth_> o/ trainguards; hi, can i get a silo for line 68 please?
[14:57] <sil2100> dbarth_: hey! Let me refresh and try assigning
[14:59] <elopio> sil2100: I updated the MPs, now rebuild?
[15:01] <jdstrand> cwayne_: thanks!
[15:03] <sil2100> elopio: you only modified the code in the MPs, right? Or did you change the MPs in the spreadsheet row?
[15:03] <elopio> sil2100: changed the MPs in the spreadsheet.
[15:03] <sil2100> elopio: this needs a reconfigure
[15:04] <sil2100> Let me try reconfiguring for you as the spreadsheet is brokennish
[15:05] <elopio> sil2100: yes please. I can't find that landing tools menu.
[15:06] <sil2100> elopio: should be reconfigured and ready to build
[15:06] <elopio> thanks sil2100
[15:07] <sil2100> yw
[15:20] <fginther> Mirv, I think the current home for bug #1441638 is a good place for wishlist items, eventually these would be requested based on their priorities
[15:21] <fginther> Mirv, so these should live where other tasks for the ci-train are tracked
[15:39] <rvr> Bad news. I found a regression in image 266, related to wizard and Oxide.
[15:39] <rvr> Filling bug.
[15:46] <boiko> trainguards: can I get vivid silo 21 reconfigured? I added new components there (telephony-service and history-service)
[15:53] <rvr> mterry: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1441708
[15:54] <rvr> mterry: That's a regression in RTM proposed 266
[15:55] <mterry> rvr, sounds like the affected version of oxide got backported to rtm
[15:55] <mterry> or at least, the patch did
[15:55] <rvr> mterry: Yes, jibel told me that we have the same version in Vivid and RTM.
[15:56] <mterry> rvr, of oxide?  bummer
[15:56] <mterry> rvr, ok will mark as dup of main bug and open a subtask
[15:56] <sil2100> boiko: hey!
[15:56] <sil2100> boiko: ok, let me reconfigure while the spreadsheet still keeps the state
[15:57] <boiko> sil2100: I got a fatal error at the spreadsheet, is it broken again?
[15:57] <sil2100> boiko: yep, see the topic, it's bullshit again
[15:57] <sil2100> But we're working with google on that
[15:57] <boiko> sil2100: ok
[15:57] <sil2100> I mean, we try to :|
[15:59] <rvr> mterry: I would say this is a high priority bug, as can prevent promoting OTA3. Not that I am the one who makes those decisions, but...
[15:59] <sil2100> boiko: could you refresh the spreadsheet and double-confirm the right branches are in your row?
[15:59] <sil2100> rvr: wow, I knew we had this in vivid, but now it's in rtm as well?
[15:59] <rvr> sil2100: Yes
[16:00] <mterry> rvr, chrisccoulson is probably the guy to quick-fix this -- it's a two line fix, but needs to be applied to the rtm branch
[16:00] <boiko> sil2100: let me see
[16:01] <boiko> sil2100: yep, it is the three branches there plus telepathy-qt (which was a source upload)
[16:01] <rvr> chrisccoulson: ^^
[16:03] <sil2100> boiko: reconfiguring then
[16:05] <boiko> sil2100: thanks!
[17:04] <rvr> bfiller: ping
[17:04] <bfiller> rvr: pong
[17:04] <rvr> bfiller: https://bugs.launchpad.net/telephony-service/+bug/1441746
[17:05] <bfiller> salem_: ^^^
[17:10] <salem_> rvr, can you miss another call from the same number just to make sure the bug is still reproducible with 2?
[17:10] <rvr> salem_: Right, let me check
[17:12] <rvr> salem_: "2 missed calls"
[17:14] <rvr> salem_: http://people.canonical.com/~vrruiz/missed-calls.png
[17:42] <robru> seb128: the thing about the two different statuses in the dashboard is that the lower, smaller-font one comes from the spreadsheet, so that's just a side effect of the spreadsheet being totally busted.
[17:42] <sil2100> robru: are you getting fatal errors right now? Since I again stopped getting errors from the time-driven scripts from the spreadsheet
[17:43] <robru> sil2100: I just did an assignment without any errors
[17:43] <sil2100> (which might mean it's temporarily working)
[17:43] <sil2100> Ok
[17:43] <robru> bfiller: got you silo 15
[17:43] <sil2100> Who knows, maybe google is *actually* looking into it
[17:43] <robru> sil2100: did you report the issues to them?
[17:44] <sil2100> robru: yeah, but Didier said he did that in the past as well and they didn't do anything, but maybe this time it was different
[17:45] <robru> sil2100: I'm starting to think we should rip *all* the code out of the spreadsheet and use it purely as a dumb data-store, and do all the calcuations/formulas in jenkins, where we can write things testably.
[17:46] <sil2100> robru: might be a good way forward, although I think it actually might not be directly related to the scripts themselves... I suppose the thing that triggers it is simply the internal google sync-between-open-clients code
[17:47] <robru> sil2100: yeah the syncing is definitely impacted, but I have a hard time believing that google is incapable of making a service that can sync among 30 people. google is known for scalability, it must be our scripts/formulas that are dragging it down
[17:48] <sil2100> robru: all in all, I wouldn't waste time on this as our top-priority should be the replacement - I would push more on getting some google people actually working on this instead
[17:49] <robru> sil2100: yeah, the ticket system isn't as far along as we previously thought. I'm not sure how long it will take before it will be ready. I think we really need to stop the bleeding before we can consider the replacement. think of all the man-hours lost to spreadsheet fuckery, how many more months can we sustain that for?
[17:51] <sil2100> I would say let's then assign more resources to the replacement and get this done faster then, at least until we know that there's nothing that google can do to help
[17:51] <sil2100> *-then
[17:53] <sil2100> Me and Steve will be poking about that the CI team tomorrow
[17:53] <sil2100> Since the recent problems popped-up, we want much much more priority set on it
[17:54] <robru> sil2100: yeah, if we can get people on it that would be great
[17:55] <sil2100> robru: let's discuss all the possibilities tomorrow, we'll know more about the current priorities and we can set the plans accordingly
[17:55] <sil2100> And there's next week too, we can discuss it further
[17:56] <robru> sil2100: yeah next week will be good
[18:20] <john-mcaleely> fresh rtm tarball for krillin
[18:20] <john-mcaleely> http://people.canonical.com/~jhm/barajas/ubuntu-rtm-14.09/device_krillin-20150408-4f14058.tar.xz
[18:20] <john-mcaleely> http://people.canonical.com/~jhm/barajas/ubuntu-rtm-14.09/device_krillin-20150408-4f14058.changes
[18:20] <john-mcaleely> http://people.canonical.com/~jhm/barajas/ubuntu-rtm-14.09/device_krillin-testresults-20150408-4f14058.ods
[18:20] <john-mcaleely> sil2100, pmcgowan ^
[18:20] <sil2100> \o/
[18:20] <sil2100> davmor2: hey, I guess you'll be EOD pretty soon, right?
[18:21] <john-mcaleely> sil2100, ping me in telgram if you get a +1 I can action tonight
[18:21] <john-mcaleely> (or the mobile in the corp. dir)
[18:21] <pmcgowan> john-mcaleely, thanks
[18:21] <davmor2> sil2100: indeed
[18:22] <davmor2> jibel: who will be best for this om26er maybe or do you want to leave it till the morning
[18:23] <john-mcaleely> (also in the tarballs & clicks tab of the spreadsheet)
[18:27] <bzoltan> ogra_: any chance to push this out, to keep mzanetti happy? https://code.launchpad.net/~bzoltan/ubuntu-seeds/add_libssl_and_qtpim_devs/+merge/254902
[21:28] <lool> Hi folks, I'm not sure what's happening with silo 12
[21:29] <lool> it doesn't seem to be up in the QA board, actually I thought it had passed yesterday
[21:29] <lool> (this is for vivid)
[21:29] <lool> trainguards ^
[21:31] <robru> lool: looks like you need to run the build job. The train doesn't think anything has been done there which is why it isn't submitted for qa
[21:31] <robru> lool: i see you uploaded a package but you haven't done anything to inform the train of this
[21:32] <lool> aha, thanks
[21:32] <lool> I'll just press build then?
[21:32] <robru> lool: yep
[21:34] <lool> Ok, so it's "packages built" now; I guess I dont need to press anything for the QA dashboard addition though?
[21:36] <lool> great
[21:36] <lool> looks good in trello now
[21:37] <robru> lool: yep ;-)
[21:58] <john-mcaleely> pmcgowan, so, om26er has given a +1 to the device tarball. I'll push it now, so there's a build with it in
[22:01] <pmcgowan> john-mcaleely, great
[22:02] <pmcgowan> I think someone needs to kick a build
[22:02] <pmcgowan> rsalveti, still about?
[22:02] <john-mcaleely> pmcgowan, generally, the machines spot new tarballs and do that
[22:02] <pmcgowan> oh
[22:02] <john-mcaleely> unless that's been turned off
[22:02] <john-mcaleely> give it 10 mins
[22:17] <john-mcaleely> imgbot, status 267
[22:17] <imgbot> Error: No rootfs build found, was this a device or custom build ?
[22:18] <john-mcaleely> pmcgowan, ^ imgbot tells all :-)
[22:18] <john-mcaleely> 267 contains the device tarball
[23:24] <rsalveti> pmcgowan: yup, what's up?
[23:25] <rsalveti> pmcgowan: yeah, the device tarball is kind of automatic