[06:44] <jin_> rvr, Hello mate,
[06:45] <jin_> rvr, I just created a task into CI-Train
[06:45] <jin_> as ticket: 1222
[07:50] <jin_> jibel, ping
[07:51] <jin_> jibel, I just created a task by CI but I found nothing shown on your dash-board,
[07:51] <jin_> tihs one -> https://requests.ci-train.ubuntu.com/#/ticket/1222
[07:51] <jin_> I am the lander and get it approved already, need your help on signing it off :)
[08:03] <jibel> jin_, Hi
[08:03] <jibel> jin_, it's because it's a click package, the QA status must be set manually to ready
[08:03] <jibel> jin_, I just did it, it'll appears on the board soon
[08:03] <jin_> jibel, ok, i got you
[08:04] <jin_> jibel, really thanks for your help.. :)
[08:04] <jin_> i will check the status there (the dashboard)
[08:27] <jibel> jin_, telegram 2.0.10.0 is just an update of the import to fix the mixed import issue with sdk 1.3?
[08:28] <jin_> jibel, yes, we schedule this update which is related to "Palette apparent" only
[08:28] <jibel> jin_, okay, it should land today
[08:28] <jin_> because it comes a huge modification - converged UI we want it to be verified from Victor
[08:29] <jin_> jin_, okay
[08:30] <jin_> jibel, okay
[08:30] <jin_> jibel, and.. I just saw you indicated it with "Fast track",
[08:31] <jin_> if you guys get it verified, just ping me directly so that I can schedule the rest (publish to store)
[09:25] <popey> jibel: davmor2 https://requests.ci-train.ubuntu.com/#/ticket/1223 weather app for QA.
[10:55] <jibel> popey, I'm trying the new weather app, does openweather works for you? it doesn't on current and new app for me
[11:06] <popey> jibel: it can be flaky
[11:07] <popey> ahayzen: 11:55 < jibel> popey, I'm trying the new weather app, does openweather works for you? it doesn't on current and new app for me
[11:07] <ahayzen> uhoh ... popey do you have the keys?
[11:08] <ahayzen> and sometimes their servers go down :-(
[11:08] <popey> a857 are the first 4 digits of the key in keys.js
[11:08] <popey> on my phone using the click I gave jibel
[11:09] <popey> (so yes, the key is in place)
[11:09] <ahayzen> yeah i think that's right
[11:10] <ahayzen> does it work for you?
[11:10] <popey> no
[11:10] <ahayzen> yeah i get "Network error"
[11:10] <popey> same
[11:11] <popey> qml: wrong response http code, got 429 /
[11:11] <popey> url works on desktop
[11:12] <popey> 429 is 'too many requests'
[11:12] <ahayzen> ugh
[11:12] <ahayzen> have we hit some kind of limit with our key?
[11:12] <popey> over use of the api key?
[11:13] <ahayzen> popey, didn't we get ours unlimited or did that not happen? (obviously it hasn't)
[11:13] <popey> https://community.openhab.org/t/openweathermap-binding-and-http-error-429/7822
[11:13] <popey> maybe not that
[11:13] <popey> might just be too many requests from the client at once
[11:13] <popey> (either way, for jibel purposes, not a regression)
[11:13] <popey> "This does not happen, when trying to use DEBUG or TRACE inside the weather binding. The problem can be avoided (partly) by defining different time schedules for the two locations -- than a 429 error happens only, when the two locations are refreshed at the same time (common multiple of the schedules)."
[11:14] <ahayzen> :-/
[11:15] <popey> I'll file a bug
[11:15] <popey> thanks jibel
[11:15] <popey> works now :)
[11:15] <popey> highly intermittent
[11:16] <popey> so yeah, we probably could do something to mitigate, but looks like an issue their end
[11:19] <popey> https://bugs.launchpad.net/ubuntu-weather-app/+bug/1566794 ahayzen jibel
[11:19] <ubot5`> Launchpad bug 1566794 in Ubuntu Weather App "Error 429 "Network Error" on openweathermap" [Undecided,New]
[11:20] <ahayzen> thanks popey
[11:20] <jibel> popey, thanks
[11:22] <bzoltan> jibel: I have top approved the silo50 MRs
[11:23] <jibel> bzoltan, thanks
[11:23] <jibel> bzoltan, do you have a changelog?
[11:26] <Mirv> jibel: bzoltan: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-050/+sourcepub/6280695/+listing-archive-extra
[11:26] <bzoltan> Mirv: jibel: more high level - http://bazaar.launchpad.net/~bzoltan/ubuntu-ui-toolkit/OTA10-landing-2016-03-10/files/head:/debian/
[11:27] <jibel> Mirv, that's good, I didn't know about this.
[11:28] <jibel> thanks
[11:28] <jibel> popey, what does "Force app into sidestage when on tablets" exactly means? I tried on a tablet and it doesn't open in side stage
[11:29] <popey> uh, it should
[11:29] <popey> I don't have a tablet
[11:29] <popey> has something changed in sidestage behaviour?
[11:30] <popey> X-Ubuntu-StageHint=SideStage
[11:30] <popey> that's set in the desktop file
[11:30] <jibel> Saviq, do you know? ^
[11:30] <jibel> did it change with recent landing of unity8?
[11:31] <ahayzen> popey, i think also, in converged mode without it was causing the whole shell to be rotated :')
[11:31] <jibel> ahayzen, true
[11:31] <jibel> and it doesn't happen with the new version
[11:31] <ahayzen> think that was the bug davmor showed me originally
[11:34] <jibel> ahayzen, popey apart from this side stage issue, everything else is fine.
[11:35] <ahayzen> \o/
[11:35] <jibel> and openweathermap that I couldn't verify
[11:36] <jibel> ahayzen, popey wat do you want to do, land it or wait until you figure out what's going on with side stage?
[11:36] <jibel> what*
[11:36] <ahayzen> jibel, what currently happens on a tablet when it is in 'tablet' mode...and then in 'convergence' mode ?
[11:37] <ahayzen> 'currently' as in the version you are testing
[11:38] <jibel> in staged mode it opens full screen, in windowed mode, it opens in the current window
[11:38] <jibel> ahayzen, ^
[11:38] <popey> this seems like a platform bug?
[11:38] <popey> what does clock do?
[11:38] <popey> hm, clock doesn't have sidestage, bad example
[11:39] <ahayzen> jibel, also in landscape does everything remain in the correct orientation when in (non)converged mode ?
[11:39] <popey> sudoku and dropping letters do
[11:39] <ahayzen> hmm system-settings?
[11:40] <jibel> popey, ahayzen correction, in windowed mode it opens in a new window
[11:40] <jibel> behaviour is the same for the clock
[11:40] <ahayzen> hmm, we should probably check with the unity8 guys if that haven't changed that sidestage hint
[11:40] <jibel> ahayzen, yes orientation is fine
[11:41] <ahayzen> otherwise i'm cool to land, but really it should go into the sidestage
[11:41] <ahayzen> ok thanks jibel :-)
[11:41] <popey> just tested it on my nexus 7 2013 running stable and it loads in sidestage
[11:42] <popey> so something has changed in the platform
[11:42] <jibel> popey, ahayzen okay, lets wait for Saviq then decide
[11:42] <jibel> overall it's an improvement over current version, so I'm fine landing it and do a subsequent landing for side stage
[11:42] <popey> http://imgur.com/a/mvnQn
[11:42]  * popey hugs marvin
[11:43] <ahayzen> popey, you need a marvin IRC bot :-)
[11:43] <popey> heh
[11:43] <popey> also need to bypass or fake the location prompt :(
[11:43] <ahayzen> hah
[11:43] <ahayzen> join the autopilot problems :-)
[11:44] <popey> :)
[12:17] <jibel> Mirv, bzoltan can you add a canonical-devices-system-image task to all the bugs fixed by silo 50 if it is not already done
[12:24] <Mirv> jibel: bzoltan: yes I'll do it
[12:24] <bzoltan> Mirv: thank you
[12:24] <jibel> Mirv, thank you
[12:32] <Saviq> jibel, popey, ahayzen, by design no app starts in side stage on its own any more
[12:33] <ahayzen> ugh
[12:33] <ahayzen> so now we get the clock and weather app fullscreen on a 10" display? :')
[12:33] <Saviq> needs to be manually put there (and then we remember)
[12:34] <Saviq> ahayzen, yeah, one thing I had in mind is take the app's {min,max}{Height,Width} into account and decide based on that
[12:34] <Saviq> ahayzen, care to file a bug against unity8 and ubuntu-ux?
[12:34] <popey> ugh
[12:35] <ahayzen> popey, i guess we should implement convergence designs :-)
[12:35] <ahayzen> Saviq, sure, stating that if an app has set a min/max height/width it should in certain cases decide to start the app in the sidestage?
[12:37] <Saviq> ahayzen, stating the problem (with screenshots, ideally) and a proposed solution, yeah
[12:37] <ahayzen> Saviq, i don't have a device :-/ ... popey ?
[12:38] <jibel> ahayzen, I think it's good to land the new weather app then?
[12:38] <ahayzen> jibel, yeah i think so, popey gets the final decision :-)
[12:39] <popey> +1 from me.
[12:39] <jibel> popey, ^ land or not?
[12:39] <jibel> great
[12:39] <jibel> approved
[12:39] <popey> thanks
[12:40] <popey> uploaded
[12:40] <popey> published
[12:43] <ahayzen> \o/ thanks jibel popey :-)
[12:44] <popey> Yes, thanks chaps!
[14:12]  * sil2100 changes location
[18:05] <Saviq> robru, hey, any idea what happened here https://ci-train.ubuntu.com/job/ubuntu-landing-013-1-build/56/console
[18:05] <Saviq> +N  debian/gles-patches/series
[18:05] <Saviq> No series file found
[18:05] <Saviq> ¿?
[18:06] <Saviq> any chance PWD isn't what I expect it to be?
[18:08] <robru> Saviq: $PWD is the bzr branch root
[18:08] <robru> Saviq: you didn't export $QUILT_PATCHES
[18:08] <Saviq> ah
[18:08] <robru> Saviq: why aren't you using my branch? I fixed that already
[18:09] <Saviq> robru, looks like you didn't push, then ;)
[18:09] <Saviq> robru, it's a branch on top of yours actually
[18:09] <Saviq> in a subsequent silo
[18:09] <robru> Saviq: bruh https://requests.ci-train.ubuntu.com/#/ticket/1221 branch pushed and built successfully
[18:10] <Saviq> robru, hrm
[18:10] <Saviq> ah I know what I did :9
[18:11] <Saviq> robru, as you were
[18:11] <robru> Saviq: let me guess, you based it on my non-quilt branch and didn't see my new quilt branch based on your quilt branch?
[18:13] <Saviq> robru, no, I had a checkout here already and didn't pull your branch that's on top of my branch
[18:18] <Saviq> robru, must say the temporary citrain user looks *really* weird :P
[18:18] <Saviq> but I ♥ the new build speed ;)
[18:20] <robru> Saviq: yeah I'll probably hide the details of the temporary user, just left it in for now since it's so new & experimental, wanted to see it all working
[18:20] <robru> Saviq: thanks though, and this isn't even parallelized, just no build deps. in a few months the parallelization stuff will land and it'll be even faster
[18:26] <Saviq> whaaa
[18:27] <Saviq> robru, can you please have a look: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-013
[18:27] <Saviq> did LP just explode?
[18:31] <robru> Saviq: it does look goofy without the buildlogs
[18:31] <robru> Saviq: I'll try retrying everything and if that doesnt fix it we should escalate to colin
[18:32] <Saviq> robru, tx
[18:32] <Saviq> robru, doesn't seem to help
[18:33] <Saviq> cjwatson, any idea what happened here https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-013/+packages
[18:33] <Saviq> all builds failed without buildlogs or any other visible reason
[18:35] <robru> Saviq: yeah those failures are quick. too quick to have even created a chroot. something's definitely wrong with the infra.
[18:35] <robru> cjwatson: ^
[20:00] <jhodapp> robru, I see that there's still 2 pending armhf builds for vivid and xenial for https://requests.ci-train.ubuntu.com/#/ticket/1225 so does that mean the "Failed to build" status is still an old status?
[20:09] <robru> jhodapp: no, once one arch fails, the whole thing is considered to be a failure (unless it's an arch that has *never* succeeded)
[20:09] <jhodapp> robru, I couldn't find the log of what failed though
[20:10] <robru> jhodapp: right, the buildlog is missing, Saviq also noticed this earlier today
[20:10] <robru> wgrant: cjwatson ^
[20:10] <jhodapp> robru, ok great, so I'm not going insane :)
[20:11] <robru> jhodapp: must be an infra issue, needs LP people to look at the ppa builders.
[20:12] <jhodapp> robru, alright...I'm off on holiday starting tomorrow but I've got koza looking after this landing for me after today
[20:34] <dobey> what's the plan going forward for dual/multi-landing, considering pending xenial archive closure, y-series opening, and our still being based on 15.04?
[20:34] <dobey> (or did i miss a mail about it?)
[20:39] <barry> robru: oh my robru https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-047/+packages
[20:40] <robru> barry: as far as I can tell all lp ppa buildds are toast. lots of people complaining about this in #launchpad
[20:41] <barry> robru: ah.  i'm never sure if i casey jonesed it or not.  i'll hop on over there
[20:41] <robru> dobey: I don't think you missed any mail (or if you did I missed it to). my understanding is that at some point we'll switch dual silos so both xenail & vivid go to overlay PPA, then at some point xenial overlay will be copied to y, then dual will be switched to y+vivid. I haven't heard any plans to get phones off vivid.
[20:42] <barry> thanks a lot queuebot
[20:42] <robru> barry: I had the same issue on a silo of my own, and same with Saviq and jhodapp. it's happening to everybody I think.
[20:42] <dobey> robru: shouldn't we be doing triple landings when y opens?
[20:43] <jhodapp> oh gosh please no :)
[20:43] <Saviq> :D
[20:43] <robru> dobey: I'll reach through your computer screen and slap you in the face.
[20:43] <dobey> at least it seems like we want to move to xenial for phone images at some point, but we just don't have a plan to do that yet, because yay gcc
[20:43] <barry> if that's not called yakkity yak it will be a serious missed opportunity
[20:44] <dobey> and my saxxity sax will be sad
[20:44] <robru> dobey: if phone images switch to xenial, then duals will be y+xenial. there's no reason to do triple. duals are always dev series + whatever stable series phones use.
[20:44] <barry> :)
[20:44] <robru> barry: don't talk back
[20:44] <dobey> robru: well, to keep things updated in xenial overlay for when we eventually do switch
[20:45] <robru> dobey: you mean after y opens, but before phones switch to xenial, we're going to need y + xenial overlay + vivid overlay? kill me
[20:46] <dobey> it seems the most logical plan
[20:47] <robru> dobey: I'd rather see the vivid->xenial migration have a minor regression at first until people start doing y+xenial landings to catch xenial up. nobody is going to QA a trual silo.
[20:47] <jhodapp> I long for the days of single landings
[20:47] <jhodapp> simplicity
[20:48] <robru> jhodapp: you need to convince somebody in management to rebase phones on dev series. resurrect the rolling release proposal.
[20:48] <dobey> robru: eh, people only QA on the phone anyway really
[20:48] <jhodapp> robru, yeah, either that or just call it good and drop xenial
[20:48] <dobey> if we based phones on devel, we'd never release phones
[20:49] <robru> dobey: right, which means triad silos were only having vivid qa'd, we'd be releasing untested crap to xenial overlay, which would make the vivid->xenial migration really hard.
[20:50] <dobey> the vivid->xenial migration is already really hard. keeping stuff compiling isn't going to make it harder
[20:50] <dobey> it's just going to consume cpu time and disk space
[20:50] <dobey> but anyway
[20:54] <robru> I don't understand why the phone wasn't migrated to wily when wily went stable. the older vivid gets the more painful it's going to be to migrate off it.
[20:54] <jhodapp> robru, yes agreed...I think we need to stop and accept the pain now before it becomes impossible
[20:57] <robru> jhodapp: not up to me :-/
[20:57] <jhodapp> robru, why not? :)
[21:00] <dobey> robru: because gcc5
[21:26] <renatu> trainguards, could you take a look on https://requests.ci-train.ubuntu.com/#/ticket/1205, it is not building
[21:27] <robru> renatu: yes, the builders are busted
[22:25] <cjwatson> robru: looking, modulo it being bedtime
[22:26] <robru> cjwatson: ah, thanks
[22:56] <cjwatson> robru,Saviq,jhodapp,renatu: LP deployment rolled back, retried all affected builds
[22:56] <Saviq> cjwatson, ack, thanks
[22:56] <robru> Thanks
[23:20] <cjwatson> https://bugs.launchpad.net/launchpad/+bug/1567132 <- analysis
[23:20] <ubot5`> Launchpad bug 1567132 in Launchpad itself "r17979 causes package build dispatch failures in devirtualised PPAs" [Critical,Triaged]