[01:08] <robru> out for dinner, bbl!
[02:05] <imgbot> [02:05] <popey> ooh
[02:05] <popey> that must mean bed time
[03:05] <imgbot> [03:40] <imgbot> [03:40] <imgbot> [04:25] <imgbot> [04:25] <imgbot> [05:18] <bzoltan_> trainguards: May I ask for a reconf of the rtm silo1? I just have added the gles branch
[05:18] <bzoltan_> robru: Mirv^
[05:22] <robru> bzoltan_: done
[05:37] <bzoltan_> robru: Thank you
[05:44] <robru> bzoltan_: you're welcome
[05:44] <robru> Hmmmm
[05:52] <robru> bzoltan_: no idea why that didn't work for you. Anyway, building.
[05:55] <bzoltan_> robru:  black magic :)
[05:56] <robru> bzoltan_: i think there's some kind of race condition, i guess i reconfigured before the previous build finished, and the previous build saved it's state over top of the new reconfigure.
[06:08] <Mirv> magic morning
[06:10] <Mirv> robru: saviq's unity8 was compiled against the new Qt correctly, but yes misses the clog entry
[06:12] <robru> Mirv: good to know the released version is compiled correctly, but really we're just lucky that your release was a no change rebuild. Had your change actually had some content to it, it would have been reverted by the duplicate publication. Definitely not a happy situation.
[06:15] <Mirv> robru: yes, but indeed I published Saviq's Unity 8 and checked it was alright, just missing that it should have nevertheless been rebuilt to pick up the changelog entry. I also pushed force rebuilds of all other components that were conflicting, but misunderstood the Unity8 silo was recent build enough
[06:16] <Mirv> robru: but indeed we'll end up in more problematic situations sooner or later since we nowadays tend to be ok with assigning conflicting silos since it improves workflow otherwise
[06:18] <robru> Mirv: yeah there's a few cases where conflicts need to be handled better. Eg when a conflict is published, I'd like the dashboard to indicate that the other conflicts are dirty and need rebuilding.
[06:19] <Mirv> kgunn: yes Qt 5.4 actually part of vivid now, including the vivid image #102
[06:22] <Mirv> robru: and even flagging the conflicting silos in general (like 018 having red "003" text besides it) reminds people more often that they need to co-operate
[06:22] <robru> Mirv: yeah that's a good idea too.
[06:49] <bzoltan_> Mirv:  could you help me to restart this build http://s-jenkins.ubuntu-ci:8080/job/qtcreator-plugin-ubuntu-ci/515/rebuild ?
[07:00] <Mirv> bzoltan_: done
[09:02] <Davmor3> jibel sil2100: phone just reminded me I need to go to the docs at 09:30
[09:03] <jibel> Davmor3, OK, enjoy.
[09:05] <sil2100> davmor2: k
[09:05] <nerochiaro> oSoMoN: good morning. Just saw the email you messages me about yesterday. any updates ?
[09:06] <oSoMoN> nerochiaro, not much, still trying to figure out a workaround for the fullscreen/autopilot issue
[09:07] <sil2100> cihelp: hey, what is the reason that we don't have smoketesting results for manta and flo devices for vivid/devel?
[09:08] <nerochiaro> oSoMoN: ok, so camera-app has still AP tests failing on krilling that need attention, right ?
[09:08] <oSoMoN> nerochiaro, yes, can you have a look at those?
[09:08] <nerochiaro> oSoMoN: ok, i am on it
[09:09] <oSoMoN> cheers
[09:09] <nerochiaro> oSoMoN: should i use the packages from here https://chinstrap.canonical.com/~bfiller/com.ubuntu.gallery_2.9.1.1149_armhf.click as bill said or build trunk myself ?
[09:09] <oSoMoN> nerochiaro, that’s a package for gallery-app :)
[09:10] <vila> sil2100: all flo and manta devices appear to be offline on q-jenkins
[09:11] <vila> sil2100: did you notice this recently ?
[09:11] <nerochiaro> oSoMoN: right. he has camera packages on there too, but i guess i will try both rebuild and use from there, hopefully they will give the same errors
[09:12] <sil2100> vila: no, it seems they're gone since quite a while, we just didn't really put too much attention to that before
[09:12] <sil2100> But I suppose it would be nice to at least try getting those two working on smoketesting
[09:18] <vila> sil2100: will raise the issue
[09:20] <sil2100> Thanks
[09:20] <sil2100> :)
[09:24] <ev> sil2100: can you help me understand the severity of this? Is someone explicitly needing manta/flo for a project?
[09:25] <sil2100> ev: currently we still don't put much pressure on tablets and flo, but these are still our officially supported devices for the development channel
[09:26] <sil2100> ev: with MWC around the corner, it would be also nice to actually see if those devices are still booting at least, and what's their general status
[09:27] <ogra_> ev, marketing and sales use the tablets to demo the sidestage
[09:27] <pete-woods> trainguards: hi folks. I've added a new MR for indicator-network to line 41 of the sheet (rtm silo 007), and line 32 (vivid silo 015). could these be reconfigured appropriately?
[09:28] <Mirv> pete-woods: sure
[09:28] <pete-woods> thanks :)
[09:28] <ev> so we're bringing manta and flo to MWC and showing off the sidestage there? That's very useful information.
[09:29] <Mirv> pete-woods: there's no vivid silo 015?
[09:29] <Mirv> pete-woods: unping, wrong page :)
[09:29] <ev> (the big problem we've had with those two devices is that they're near-impossible to wire for automation - we cannot programmatically reboot them like we can with mako/bq)
[09:30] <ogra_> ev, not sure, but that is what happened the last years
[09:30] <ogra_> someone should confirm that indeed
[09:30] <ev> yes, indeed
[09:30] <pete-woods> Mirv: no, I think you're correct. I was obviously hallucinating when looking up the silo for vivid, it doesn't have a silo allocated yet
[09:32] <pete-woods> oh wait, now it does?? I'm super confused
[09:32] <Mirv> pete-woods: it did have, but the spreadsheet was then empty for a little while, and now that spreadsheet again knows about I'm reconfiguring it
[09:33] <pete-woods> oh, cool. glad to know I've not lost my mind
[09:33] <Mirv> the spreadsheet occasionally makes you think that
[09:33] <pete-woods> :D
[09:36] <sil2100> john-mcaleely: hey! Is the device tarball ready already? :)
[09:36] <sil2100> I mean, did you test it fully already?
[09:36] <sil2100> Ah, I see you did
[09:37] <popey> cihelp: jenkins seems busted. http://paste.ubuntu.com/10270569/ - trying to rebuild this. http://91.189.93.70:8080/job/generic-mediumtests-vivid/1019/rebuild/?
[09:37] <popey> (is this known)?
[09:39] <vila> popey: /me looks
[09:39] <popey> ta
[09:40] <vila> popey: O_0 where did you get that jenkins gut spilling ?
[09:40] <popey> trying to re-run https://code.launchpad.net/~pkunal-parmar/ubuntu-calendar-app/LiveEventModification/+merge/247711
[09:40] <popey> clicked http://91.189.93.70:8080/job/generic-mediumtests-vivid/1019
[09:40] <popey> then rebuild-> http://91.189.93.70:8080/job/generic-mediumtests-vivid/1019/rebuild/?
[09:40] <popey> then rebuild button
[09:41] <popey> Boom!
[09:41] <vila> popey: ha, indeed :-/
[09:42] <popey> :)
[09:42] <vila> :-D
[09:42] <Mirv> charles: the rtm-019 diff somehow magically seems to have all of vivid in it as well even though the branch that was compiled is targeted against the rtm branch, last updated 20140925: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-019/+files/ubuntu-themes_14.04%2B14.10.20140925-0ubuntu1_14.04%2B15.04.20150213%7Ertm-0ubuntu1.diff.gz
[09:43] <vila> popey: but indeed (too) the job doesn't define candidate_revision....
[09:43] <vila> which is very surprising
[09:43] <Mirv> charles: QA has signed off the silo, but instead of a few files changed it's 29MB diff (compressed) <- sil2100
[09:44] <vila> popey: nor any of 	merge_proposal packaging_branch project_name 	use_description_for_commit
[09:45] <Mirv> charles: so we'd kind of need to know what to do the silo. should you rebuild it? it will then miss the deadline for this milestone.
[09:46] <vila> popey: yet, http://91.189.93.70:8080/job/generic-mediumtests-vivid/1090/parameters/? has them and has been started 15 mins ago
[09:46] <popey> wierd, huh?
[10:01] <popey> vila: any ideas?
[10:07] <john-mcaleely> sil2100, yeah, all good to go
[10:08] <vila> popey: nope, the config file for that job has been last modified on 2014-10-31
[10:08] <vila> popey: I should be missing something obvious...
[10:25] <psivaa_> popey: so to rebuild https://code.launchpad.net/~pkunal-parmar/ubuntu-calendar-app/LiveEventModification/+merge/247711, Why are you rebuilding from 1019?
[10:25] <psivaa_> the MP has 1067 as the latest failed build
[10:27] <psivaa_> you would not be able to rebuild a downstream job on its own, there are someparameters coming from the upstream job
[10:28] <popey> psivaa_: vila I am just trying to rebuild a failed landing
[10:28] <popey> psivaa_: vila clicking the links provided. I don't quite understand what broke and where
[10:29] <psivaa_> popey: the 'rebuild' link provided in the MP is http://91.189.93.70:8080/job/ubuntu-calendar-app-ci/1067/rebuild
[10:29] <psivaa_> not http://91.189.93.70:8080/job/generic-mediumtests-vivid/1019/rebuild/
[10:30] <psivaa_> the second one is a downstream job, which will be triggered by the first one ^ and will use some parameters from the first build (1067)
[10:31] <psivaa_> popey: http://91.189.93.70:8080/job/ubuntu-calendar-app-ci/1074/console is now running
[10:31] <vila> psivaa_: ooooh, thanks for the explanation, http://91.189.93.70:8080/job/ubuntu-calendar-app-ci/configure defines the missing parameters as 'predefined parameters' in the 'trigger/call builds on other projects' indeed
[10:32] <vila> psivaa_: that's the "obvious" bit I missed ;)
[10:33] <popey> ahhh
[10:33] <popey> I see. you're right. I am a doofus.
[10:34] <psivaa_> vila: popey: np, i'm glad that its running now
[10:34] <popey> sil2100: do we plan to release a mako update any time soon?
[10:34] <popey> (being asked by community people running mako)
[10:53] <sil2100> popey: mako ubuntu-rtm?
[10:53] <popey> ya
[10:53] <sil2100> popey: waiting for slangasek to be up and get status on the channel changes
[10:54] <sil2100> popey: in any way, the stable channel will only see updates once per month, but there will be an RC channel available for mako users with 2-week updates as well
[10:57] <popey> ok, will pass that on...
[11:00] <dbarth> o/ hi trainguards, can i have a silo for line 63?
[11:04] <sil2100> dbarth: sure
[11:07] <dbarth> ty
[11:14] <sil2100> davmor2: how's the device tarball testing going so far?
[11:15] <davmor2> sil2100: it's downloaded
[11:18] <jgdx> trainguards: can you reconfigure rtm 7?
[11:20] <sil2100> jgdx: sure, new component added?
[11:20] <davmor2> sil2100: it was too late last  night to start it, I needed to test something for tiagosh first thing so I've just downloaded it and started the flash process now, does that help?  Probably looking at 1:30-2:00 hours
[11:20] <jgdx> sil2100, a new mp for u-s-s.
[11:20] <jgdx> sil2100, might not warrant a reconfigure, but a build?
[11:21] <sil2100> jgdx: it still requires a reconfigure, but in cases like these the lander can reconfigure it by himself - but I already did it just now :)
[11:22] <jgdx> sil2100, okay, thank you. :) /me makes note.
[11:46]  * sil2100 jumps out for lunch
[11:46] <sil2100> I might be off ~1.5h since I need to jump to the store as well
[11:50] <brendand> sil2100, walk, it's safer
[12:12] <bzoltan_> sil2100: Mirv: who is the QA go-to-person in these hours? I wish to know if I can land two MRs with this round.
[12:14] <Mirv> bzoltan_: sil might know the answer to that, but during these ours QAs eg jibel, davmr2
[12:20] <bzoltan_> Mirv: sil2100: jibel: davmor2: I have two MRs in the RTM silo1 (CI sheet line #61) Both are requred to the W9. But the build-test-plan-qa takes 3 days as we know. One of the MR is literaly a single line and this change is already merged to the Vivid branch. Soi it is a negative risk issue. But I need your ack on landing two MRs in one round.
[12:37] <davmor2> bzoltan_: I defer to jibel on that
[12:49] <jgdx> trainguards: when a silo has been reconfigured, does the build need any special parameters?
[12:52] <Mirv> bzoltan_: while waiting for that answer, note that of the three unfixed bugs linked to https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/textHandlerCleanUpRTM/+merge/247388 only one has ww9 milestone currently, the rest should possibly be escalated to be crystal clear it's allowed to land at this time
[12:52] <Mirv> jgdx: not usually
[12:53] <jgdx> Mirv, does it hurt if I try? The silo was reconfigured with the new branch, and built without it (it seems).
[12:53] <bzoltan_> Mirv: I am proposing to land two fixes for two bugs from this list -> https://launchpad.net/canonical-devices-products/+milestone/ww09-2015
[12:53] <Mirv> jgdx: no, it does not hurt. it should detect there's a new branch and rebuild, but if not then specify the package name on the next attempt.
[12:54] <boiko> Mirv: hi, I now got top approval on the MR on vivid silo 7, all good to land now
[12:55] <Mirv> bzoltan_: my question is about line 26, ie bug 1407723 - the branch lists two other bugs and they probably should also have ww09 tag if you plan to land a fix for that bug
[12:55] <Mirv> boiko: ok!
[12:55] <boiko> Mirv: thanks
[13:01]  * Mirv goes through the whole spreadsheet
[13:03] <bzoltan_> Mirv:  I think the line 26 can be deleted
[13:03] <Mirv> bzoltan_: thanks
[13:03] <jibel> bzoltan_, no problem with landing 2 fixes. Is it silo 1?
[13:04]  * bzoltan_ hugs jibel
[13:04] <bzoltan_> jibel: Yes, silo1
[13:04] <jibel> bzoltan_, because it contains 5 fixes :)
[13:04] <bzoltan_> jibel: hehe... true, it depends how you look
[13:05] <jibel> bzoltan_, that's fine
[13:06] <Mirv> jibel: so I was asking whether those two other bugs need to be also tagged ww09, which that one branch fixes
[13:06] <Mirv> but I guess that doesn't matter as long as there's a branch that fixes a ww09 bug, even if there are other bugs linked
[13:07] <jibel> Mirv, yes they should for tracking purpose.
[13:07] <Mirv> jibel: oh, ok. bzoltan_ ^ you need to get the other linked bugs other than 1407723 marked as ww09 too, so that they are properly tracked.
[13:07] <Mirv> from PM
[13:08] <bzoltan_> Mirv:  i think it is there
[13:08] <jibel> bzoltan_, and fix the silo so that the package builds on every archs
[13:09] <bzoltan_> Mirv: https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1395118 is on w9
[13:41] <Mirv> bzoltan_: https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/textHandlerCleanUpRTM/+merge/247388 -> bug #1391335 and bug #1415548 do not have canonical system image project or a milestone
[13:54] <jgdx> cihelp: rtm silo 7 is ready for testing, btw.
[13:56] <vila> jgdx: you probably want trainguards ^
[13:56] <jgdx> vila, right
[14:01] <sil2100> jgdx: QA will automatically have it on their queue once it's marked as tested
[14:02] <jgdx> sil2100, good.
[14:20] <sil2100> kenvandine: hey! :)
[14:21] <sil2100> kenvandine: you working on u-s-s recently as well, right?
[14:24] <kenvandine> sil2100, yeah
[14:27] <seb128> hey kenvandine, did you figure out the issue with u-s-s and CI?
[14:27] <kenvandine> seb128, no... it's worse than i thought too
[14:28] <kenvandine> smoke testing started failing too
[14:28] <kenvandine> between images 95 and 98 i think
[14:28] <kenvandine> and it's all crashes related to QtFeedback i think
[14:29] <seb128> shrug
[14:30] <sil2100> kenvandine: could you take a look at vivid smoketesting? ;)
[14:31] <sil2100> Almost all tests are failing
[14:31] <kenvandine> sil2100, yes... that's what i'm talking about with seb128
[14:32] <kenvandine> sil2100, it's a crash
[14:32] <kenvandine> and it's crashing down deep in QtFeedback
[14:32] <kenvandine> which isn't anything we should be tickling ourself, i would think it's the uitk
[14:32] <kenvandine> but then we'd see crashes all over the place
[15:24] <davmor2> jibel, sil2100, john-mcaleely: device tarball looks good  and that ^ is probably the announcement for it :)
[15:25] <sil2100> o/
[15:25] <sil2100> john-mcaleely: you are free to push the tarball
[15:25] <jibel> davmor2, thanks! any news about a new custom tarball today?
[15:26] <sil2100> john-mcaleely: ^ ?
[15:26] <sil2100> I don't see any request for that on the spreadsheet
[15:27] <davmor2> jibel: I don't see cwayne in here
[15:29] <pmcgowan> sil2100, custom should have fixes to scopes using OA and an apparmor cache update
[15:30] <sil2100> cwayne: hey, is the custom tarball ready already?
[15:30] <davmor2> \o/ cwayne is here now, we can party \o/  /me slaps cwayne for not being here earlier and making move the mouse to find a channel he was in ;)
[15:30] <cwayne> sil2100: just about to be, see #phablet
[15:34] <john-mcaleely> sil2100, ack, will push now
[15:34] <john-mcaleely> thanks davmor2
[15:34] <charles> Mirv, wrt rtm silo 19, the indicator-power diff at https://launchpadlibrarian.net/197544824/indicator-power_12.10.6%2B15.04.20150203~rtm-0ubuntu1_12.10.6%2B15.04.20150213~rtm-0ubuntu1.diff.gz looks safe to me
[15:35] <john-mcaleely> sil2100, pushed!
[15:35] <Mirv> charles: indicator-power is ok, ubuntu-themes is the question mark
[15:35] <charles> Mirv, however I was hoping to get someone to look over my shoulder on the ubuntu-themes packaging changes in that silo, as there wasn't an RTM branch before this
[15:36] <charles> ack
[15:36] <Mirv> charles: I looked that the rtm branch + MP look sane, but the end result looks like coming from vivid so it's trange
[15:36] <Mirv> strange, even
[15:36] <Mirv> sil2100: ^ in practice I don't know even how it's possible that the ubuntu-themes in that PPA is like it is, since the rtm branch is correctly from September and the MP is simple
[15:37] <charles> yeah, would welcome guidance on what the Right Thing is here
[15:40] <Mirv> charles: sil2100: https://code.launchpad.net/~ubuntu-art-pkg/ubuntu-themes/rtm-14.09 + https://code.launchpad.net/~charlesk/ubuntu-themes/lp-1388235-add-new-power-icons-rtm-14.09/+merge/249695 looks sane, but somehow that ended up as https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-019/+sourcepub/4776206/+listing-archive-extra
[15:42] <Mirv> charles: sil2100: I'm pretty EOD but I'd mostly ask from sil2100 if he thinks we should try force rebuild of ubuntu-themes to try to get the contents correct, or consider shipping ubuntu-themes as is as it was already approved by QA
[15:42] <charles> ack, will wait for opinion from sil2100
[15:45] <charles> it would probably be better to have a clean diff on this though
[15:46] <charles> looks like most of the other changes are gtk/gnome related and would be no-ops for rtm, but looks like the weather apps got moved into a different directory for bug #1289465
[15:47] <charles> my preference would be to fix the MP, though looking at the first two links from Mirv above I don't see what went wrong :P
[15:48] <charles> s/weather apps/weather app icons/
[15:48] <rsalveti> sil2100: what is the syntax to request a sync from another silo (vivid->rtm)?
[15:52] <rsalveti> sync:<silo number> it seems
[16:00] <sil2100> charles, Mirv: sorry, was in a meeting
[16:00] <sil2100> Need to backlog
[16:01] <charles> sil2100, ack
[16:04] <sil2100> john-mcaleely: thanks!
[16:10] <sil2100> charles: ok, one more meeting... but will be finished soon
[16:10] <charles> :)
[16:10] <sil2100> popey: hey, how's the calendar going?
[16:11] <popey> sil2100: iahmad is on it I believe
[16:18] <jibel> popey, oops iahmad_ EOD long time ago.
[16:18] <jibel> popey, sil2100 can you add a line to the spreadsheet for the calendar app and I'll find someone
[16:22] <sil2100> jibel: will add it
[16:23] <sil2100> popey: can you provide me with all the click links, test plans etc.?
[16:25] <sil2100> rsalveti: yeah, sync:<number> is enough if its vivid <-> 14.09, like sync:6
[16:35] <sil2100> charles: ok, I would propose rebuilding ubuntu-themes in the silo now
[16:35] <sil2100> Since I have no idea how it ended up looking like that
[16:37] <sil2100> charles: let me do that
[16:37] <charles> sil2100, k
[17:04] <robru> sil2100: Hmmmmmmm my Wi-Fi seems dead
[17:04] <sil2100> robru: uh oh!
[17:05] <sil2100> robru: no worries, just make sure that if you don't have connectivity today, please poke cyphermox to fill in re. landings
[17:05] <robru> I guess i can't make the meeting
[17:06]  * cyphermox sends robru some wifi waves
[17:11] <oSoMoN> trainguards: can silo 11 be published, please?
[17:18] <sil2100> cwayne: just so you know, I filled in the landing request ;)
[17:19] <cwayne> sil2100: thank you :)
[17:32] <oSoMoN> trainguards: can I haz a silo for line 73?
[17:32] <oSoMoN> (please)
[17:33] <robru> oSoMoN: CONFLICTS WITH SILO EIGHT!!!!!!!!11!!eleven!!!!
[17:33] <robru> oSoMoN: just kidding, got you silo 25
[17:33] <oSoMoN> :) thanks!
[17:34] <robru> oSoMoN: you're welcome
[18:00] <seb128> hum
[18:00] <seb128> why are those rtm landing (e.g indicator-power) having an empty changelog?
[18:00] <seb128> indicator-power (12.10.6+15.04.20150213~rtm-0ubuntu1) 14.09; urgency=medium
[18:00] <seb128>   *
[18:00] <seb128>  
[18:00] <seb128> seems buggy
[18:02] <robru> seb128: indeed, not sure why that's happening.
[18:03] <robru> seb128: will look
[18:03] <seb128> thanks
[19:28] <pmcgowan> om26er, once you bless silo 7 we can let it land
[19:31] <om26er> pmcgowan, ok, thanks for letting me know. I am almost there
[19:32] <pmcgowan> om26er, great
[19:32] <pmcgowan> om26er, myself and john-mcaleely tried it and while we agree UX could be better its ok for now
[19:32] <john-mcaleely> yeah
[19:35] <robru> brb, lunch
[19:36] <kgunn> trainguards i'm getting 404 for the reconfig link the train sheet ...known issue? or am i the issue?
[19:38] <om26er> pmcgowan, everything is fine. except there is one issue that I found.
[19:38] <om26er> With the silo installed if I do factory reset, put a SIM card in slot2 and leave slot1 empty. When the phone boots if I go to cellular settings page, it only shows 2G option. I have to go back and come in again, only then I can see 3G option. It would be safe to have that fixed atleast.
[19:38] <om26er> this is the state that a new user will have when they first use their phone.
[19:38] <kgunn> oh nvmd...i recall now, i need to erase some of the url
[19:39] <kenvandine> om26er, i think jgdx said that was a race condition
[19:39] <pmcgowan> om26er, is that just a iming thing
[19:39] <pmcgowan> ah
[19:39] <kenvandine> om26er, but i think that's there without the silo?
[19:40] <om26er> kenvandine, without the silo we never have 3G on second slot, with the silo, the option is not there when the first time you open Cellular settings
[19:40] <om26er> probably some property it needs to read when Cellular page is opened first.
[19:40] <kenvandine> but i don't think that only happens on the second SIM
[19:41] <kenvandine> i think it's a race from libqofono
[19:41] <kenvandine> jgdx, you were looking at that right?
[19:41] <om26er> let me share a screenshot
[19:41] <kenvandine> om26er, i know we have that in vivid on mako (single SIM)
[19:41] <kenvandine> om26er, and the tech switch stuff hasn't landed in vivid yet, we have that race without it
[19:42] <kenvandine> om26er, so if anything it's introduced by the new libqofono in that silo
[19:45] <om26er> kenvandine, this: http://i.imgur.com/OAeY5Un.png
[19:45] <kenvandine> oh... a little different
[19:46] <om26er> Now if I go back and come back in, it will have both 2G only and 2G/3G entries.
[19:46] <kenvandine> so on vivid sometimes the first time you open the page, the wrong one is checked
[19:46] <om26er> this always happens the first time and at a few unknown occasions which I was not able to create steps for.
[19:46] <kenvandine> but it does show all the technologies
[19:47] <kenvandine> om26er, but does it happen without the silo?
[19:47] <kenvandine> i'd bet that is also a race condition related to the libqofono update
[19:47] <kenvandine> like the listview not handling the model update
[19:48] <pmcgowan> kenvandine, tested silo 14 and worked as expected
[19:48] <kenvandine> pmcgowan, great, can you mark the spreadsheet?
[19:48] <om26er> let me give it a try without the silo.
[19:48] <kenvandine> om26er, thanks
[19:49] <pmcgowan> kenvandine, I dont have write access
[19:49] <kenvandine> om26er, the more i think about it, i am thinking it is from this silo, but confirmation would be good
[19:49] <kenvandine> pmcgowan, ok, you're on 237 right?
[19:49] <pmcgowan> kenvandine, yes
[19:49] <pmcgowan> I did a clean flash in the end
[19:50] <kenvandine> pmcgowan, thx, i marked the spreadsheet
[19:50] <kenvandine> maybe we can at least get that landing for this milestone... if we can't land 7 :(
[19:51] <kenvandine> om26er, so you have a single SIM in right?  which is it showing, it just not showing 3g as a choice?
[19:51] <kenvandine> om26er, and is that after you changed it to 3g?
[19:52] <kenvandine> man my english is terrible :)
[19:52] <om26er> kenvandine, hah, yes I have a single SIM, only in slot2.
[19:52] <om26er> this issue only happens with slot2
[19:52] <kenvandine> after changing slot 2 to 3g right?
[19:56] <om26er> kenvandine, without silo it always have 2G... because the feature is only implemented in the silo.
[19:56] <kenvandine> oh right, it never says it can have 3g
[19:56] <robru> kgunn: wait what? the only 404 issue I'm aware of is if you're not logged in, but I thought I fixed that so it logs you in first and redirects. shouldn't be any 404s.
[19:57] <om26er> kenvandine, regarding the other question, I think slot2 is on 2G since if I try to change to 3G is spins for a while
[19:57] <kgunn> robru: i'm definitely logged in
[19:57] <kgunn> robru: willing to play if you'd like to help :)
[19:57] <robru> kgunn: what URL is 404ing? and what did you delete to make it work?
[19:58] <kgunn> robru: and...altho deleting gets me there...looses all the relevant info (mainly unique request id)
[19:58] <kgunn> one sec
[19:58] <kgunn> robru:
[19:58] <kgunn> https://www.google.com/url?q=https://ci-train.ubuntu.com/securityRealm/commenceLogin?from%3D/job/ubuntu-landing-000-0-reconfigure/parambuild%253FREQUEST_ID%253D1422983604742%2526DISTRIBUTION%253Dubuntu%2526SERIES%253Dvivid%2526LANDERS%253Dkgunn%2526MERGE_PROPOSALS%253Dhttps%25253A%25252F%25252Fcode.launchpad.net%25252F~mir-team%25252Fmir%25252Fexpose-cursor%25252F%25252Bmerge%25252F248396%252520https%25253A%25252F%25252Fco
[19:58] <kgunn> de.launchpad.net%25252F~andreas-pokorny%25252Fmir%25252Foverride-orientation-for-input-region-and-cursor%25252F%25252Bmerge%25252F248897%252520https%25253A%25252F%25252Fcode.launchpad.net%25252F~kdub%25252Fmir%25252Fno-abi-break-mm%25252F%25252Bmerge%25252F250046%252520%252520https%25253A%25252F%25252Fcode.launchpad.net%25252F~mir-team%25252Fqtmir%25252Fport-to-msh-shell-and-mirevent2%25252F%25252Bmerge%25252F248433%252520
[19:58] <kgunn> https%25253A%25252F%25252Fcode.launchpad.net%25252F~dandrader%25252Fqtmir%25252FsupportedOrientations%25252F%25252Bmerge%25252F242213%252520%252520https%25253A%25252F%25252Fcode.launchpad.net%25252F~mir-team%25252Fqtubuntu%25252FshellRotation-mirclient%25252F%25252Bmerge%25252F248431%252520%252520https%25253A%25252F%25252Fcode.launchpad.net%25252F~phablet-team%25252Fubuntu-keyboard%25252FshellRotation%25252F%25252Bmerge%25
[19:58] <kgunn> 252F248399%252520%252520https%25253A%25252F%25252Fcode.launchpad.net%25252F~dandrader%25252Funity-api%25252FshellRotation%25252F%25252Bmerge%25252F242212%252520%252520https%25253A%25252F%25252Fcode.launchpad.net%25252F~unity-team%25252Funity8%25252FshellRotation%25252F%25252Bmerge%25252F248400%252520https%25253A%25252F%25252Fcode.launchpad.net%25252F~unity-team%25252Funity8%25252FshellRotation-no-indicators%25252F%25252Bme
[19:58] <kgunn> rge%25252F250057%252520https%25253A%25252F%25252Fcode.launchpad.net%25252F~mzanetti%25252Funity8%25252Finputinfo%25252F%25252Bmerge%25252F248407%252520https%25253A%25252F%25252Fcode.launchpad.net%25252F~mzanetti%25252Funity8%25252FsaveRestoreWindowSizePosition%25252F%25252Bmerge%25252F247840%252520https%25253A%25252F%25252Fcode.launchpad.net%25252F~mzanetti%25252Funity8%25252Freveal-launcher-with-mouse-hover%25252F%25252Bm
[19:58] <robru> heh
[19:59] <kgunn> erge%25252F248913%252520%252520https%25253A%25252F%25252Fcode.launchpad.net%25252F~mir-team%25252Funity-system-compositor%25252Ftoggle-cursor%25252F%25252Bmerge%25252F248520%252520https%25253A%25252F%25252Fcode.launchpad.net%25252F~andreas-pokorny%25252Funity-system-compositor%25252Foverride-orientation-dbus-api%25252F%25252Bmerge%25252F248896%252520%252520%252520https%25253A%25252F%25252Fcode.launchpad.net%25252F~mir-team
[19:59] <kgunn> %25252Fplatform-api%25252Fexpose-mir-connection%25252F%25252Bmerge%25252F245054%252520%252520https%25253A%25252F%25252Fcode.launchpad.net%25252F~andreas-pokorny%25252Fubuntu-touch-session%25252Fenable-hardware-cursor%25252F%25252Bmerge%25252F248531%252520https%25253A%25252F%25252Fcode.launchpad.net%25252F~andreas-pokorny%25252Fubuntu-touch-session%25252Fgu-evaluation-in-usc-wrapper%25252F%25252Bmerge%25252F248994%252520%25
[19:59] <kgunn> 2520https%25253A%25252F%25252Fcode.launchpad.net%25252F~seb128%25252Fubuntu-system-settings%25252Fbluetooth-key-hint-workaround%25252F%25252Bmerge%25252F249622%2526SOURCES%253Dlibevdev%252520qtsystems-opensource-src%2526SYNC_REQUEST%253D%26delay%3D0sec&sa=D&usg=ALhdy2-JDnpVXgeISlkg_USJ1wxF7_iGxg
[19:59] <robru> kgunn: let me guess, you s/parambuild/build to make it work?
[19:59] <kgunn> sorry...
[19:59] <kgunn> how bout
[19:59] <kgunn> https://pastebin.canonical.com/125771/
[19:59] <davmor2> kgunn: man what did irc ever do to you to deserve that ;)
[19:59] <kenvandine> robru, trying to publish vivid silo 15
[20:00] <kenvandine> it's showing packaging changes for dialer-app
[20:00] <kenvandine> robru, which isn't in the silo
[20:00] <kenvandine> robru, should i be worried?
[20:00] <robru> kenvandine: did it used to be in the silo?
[20:00] <kenvandine> dunno
[20:00] <kenvandine> maybe :)
[20:00] <kenvandine> it's not built in the ppa
[20:01] <kenvandine> and it was never part of my landing
[20:01] <robru> kenvandine: ok well it's not in the PPA, so there's no risk of anything incorrect being published. I'd just ACK it.
[20:01] <kenvandine> ok
[20:01] <kgunn> robru: and actually no, s/parambuild/build just gets me to ci-train.ubuntu.com
[20:01] <robru> kenvandine: after you publish, check the packagelist artifact, it should have just one line per package in the ppa
[20:02] <robru> kgunn: so that url looks fine to me, what are you changing to make it work?
[20:02] <kenvandine> robru, ok, and the full diffs included dialer-app and history-service
[20:02] <kenvandine> so maybe just a bug in your new (and very cool) diff stuff :)
[20:02] <kgunn> robru: well thats just it....i cant make it work, i just get to jenkins proj page only
[20:02] <kenvandine> robru, indeed the packagelist is right
[20:03] <robru> kenvandine: my only guess is that the contents of the previous assignment for that silo got resurrected when we migrated to a larger disk. there's definitely no code that adds dialer-app to silos that don't have it ;-)
[20:03] <kgunn> robru: i tried to copy in the mp list, but it still wants a unique id...which i see in the url, but can't get there with that in place
[20:03] <robru> kgunn: oh I thought you said you could delete a bit of the URL to make it work.
[20:03] <robru> kgunn: which spreadsheet row?
[20:03] <kgunn> ...*almost* worked :)
[20:03] <kenvandine> robru, figured...
[20:03] <kgunn> robru: 36
[20:04] <kgunn> thanks for the help
[20:04] <kenvandine> robru, btw... i do love the silo diffs!
[20:04] <kenvandine> robru, thanks for that
[20:05] <robru> kenvandine: you're welcome! I wish I'd been able to do that 3 months ago when brendand asked, but there was a lot of stuff that had to be fixed first to get here.
[20:05] <robru> kgunn: https://pastebin.canonical.com/125772/ try the link in this paste, does that work for you?
[20:06] <robru> kgunn: it's a bit tricky because there's two layers of redirects here, google has their own click-counter redirect thing they put on URLs, and then the internal link redirects through the SSO login. what I pasted is the final URL after all redirects are done.
[20:12] <robru> kgunn: also, while we're fiddling with this, want me to just reconfigure for you? ;-)
[20:12] <kgunn> robru: woohoo!
[20:12] <kgunn> worked
[20:12] <robru> kgunn: hmmm, ok so if that worked it means the redirects are broken...
[20:12] <robru> kgunn: when was the last time the reconfigure link worked for you? weird that it works for me...
[20:15] <pmcgowan> kenvandine, what was the verdict on silo 7
[20:20] <pmcgowan> om26er, ^^
[20:20] <kenvandine> there is some kind of race condition there, it works but the UI is wonky
[20:20] <om26er> we have the exact steps.
[20:21] <kenvandine> i'm browsing the code now to see if i can figure it out
[20:21] <kenvandine> but i'm thinking it might be in libqofono
[20:24] <jgdx> kenvandine, what's up? When's eod for us guys?
[20:24] <jgdx> om26er, exact steps plz
[20:25] <om26er> jgdx, I mentioned them in the trello, do you have the link ?
[20:25] <kenvandine> jgdx, it could be the model tweaking in onCompleted from MultiSim.qml
[20:26] <jgdx> om26er, yea
[20:26] <jgdx> kenvandine, right, I'll take a look.
[20:27] <kenvandine> if ((sim.radioSettings.modemTechnologies.indexOf('umts') [20:27] <kenvandine> 198	+                     && (sim.mtkSettings.has3G [20:27] <kenvandine> jgdx, ^^ maybe something with that the first time we load the page
[20:30] <jgdx> kenvandine, yeah, the techs are probably added async. So s/onCompleted/onModemTechnologiesChanged
[20:30] <kenvandine> jgdx, that's what i was thinking
[20:30] <jgdx> om26er, when do you close shop?
[20:31] <jgdx> om26er, thanks for excellent testing, btw. Again.
[20:31] <om26er> jgdx, in ~30 minutes
[20:52] <jgdx> om26er, I can't repro this
[20:53] <jgdx> om26er, it's on 2g, and when I click 3g it does the tech switch dance and comes back as 3g
[20:53] <jgdx> (krillin, 1 SIM in slot 2, --wipe, rtm, silo 7)
[20:53] <jgdx> I am missing something here…
[20:57] <jgdx> om26er, do I have to "Erase & Reset everything…"?
[20:57] <om26er> jgdx, yes
[20:57] <robru> uh huh
[20:58] <om26er> well --wipe+silo should be the same, but incase you might have missed something, try after "Erase & Reset everything…"
[20:58] <jgdx> --wipe+silo seems to be different though, it's resetting now
[20:59] <davmor2> cwayne, rsalveti, robru:  Custom tarball is good, signon-apparmor-extension works with the custom tarball.  I don't know if you can add the package to the seed and then release custom so that the package is pulled in or what needs to happen there.
[21:00] <rsalveti> I can add the package back to the seeds
[21:00] <rsalveti> would need cwayne for the custom tarball
[21:00] <robru> davmor2: rsalveti: I have no opinion. go ahead with what you think is right.
[21:00] <rsalveti> alright, let me push signon-apparmor-extension
[21:02] <cwayne> im good to push whenever you want me to
[21:02] <rsalveti> cwayne: alright, I'll ping you in a few
[21:03] <rsalveti> but guess we need to build a new rootfs
[21:03] <cwayne> cool beans
[21:03] <cwayne> i dont think thats a requirement, new custom should work without s-a-e as well
[21:03] <cwayne> but im fine to wait if that's what we want to do
[21:03] <rsalveti> oh, cool then
[21:11] <davmor2> cwayne: I would prefer them to both land together-ish as one adds security and the other adds the fix to make it work :)   However one landing before the other I don't care about as long as neither are forgotten :)
[21:11] <davmor2> rsalveti: ^
[21:12] <davmor2> and with that I wish you both a good night
[21:15] <rsalveti> davmor2: cwayne: https://launchpad.net/ubuntu-rtm/+source/ubuntu-touch-meta/1.202
[21:15] <rsalveti> will be available in the next image, which should be out in ~4 hours
[21:15] <rsalveti> cwayne: so I'd say push it :-)
[21:18] <kenvandine> om26er, if this is only reproducable after doing a erase and reset, how do you feel about landing it and fixing that issue as a bug
[21:18] <kenvandine> it's probably not a common case, erase&reset with only a SIM in the second slot
[21:18] <kenvandine> i'd really rather get this landed for ww09
[21:18] <kenvandine> so people can have 3g on slot 2
[21:19] <kenvandine> pmcgowan, jgdx: ^^
[21:20] <om26er> kenvandine, that happens on a clean install
[21:20] <om26er> I did not have to reset my device for it to happen
[21:20] <cwayne> davmor2: rsalveti: \o/ pushing now
[21:20] <om26er> just --wipe (that's what a user will have when he buys the phone.)
[21:20] <kenvandine> jgdx, said he couldn't reproduce it when flashing with --wipe
[21:20] <jgdx> two times in a row
[21:21] <jgdx> but I'm not sure if this is ofono, libqofono or u-s-s yet.
[21:22] <cwayne> and pushed :D
[21:22] <cwayne> thanks davmor2
[21:23] <pmcgowan> om26er, kenvandine hard to know but probably folks will boot the phone, then insert the sim and reboot, and likely use top slot
[21:23] <kenvandine> yeah
[21:23] <kenvandine> i just started a flash with --wipe
[21:23] <kenvandine> see if i can repro it
[21:24] <jgdx> thanks kenvandine
[21:24] <kenvandine> pmcgowan, but i do think it's kind of a corner case anyway, it's more interesting to allow 3g on the second slot
[21:24] <kenvandine> i think most people will only have a SIM in slot 2 if they have 2 SIMs
[21:26] <pmcgowan> kenvandine, om26er that silo is holding up several others so I think we should land it and improve that case later
[21:28] <om26er> pmcgowan, I am fine if you think it is. I and Jean-Baptiste tested the silo, we didn't find any functional regressions, just a few bugs/behavioral issues.
[21:29] <kenvandine> jgdx, can you please file a bug to track this issue?
[21:29] <kenvandine> om26er, thx, lets do that
[21:29] <kenvandine> this will really help users with dual sims
[21:30] <pmcgowan> om26er, thank you
[21:30] <pmcgowan> we have a list in this area already so we will keep improving things
[21:32] <kenvandine> om26er, and thanks again for the thorough testing!
[21:33] <om26er> kenvandine, heh, no problem, the change was a bit big at this stage :)
[21:33] <kenvandine> flash done... adding silo
[21:33] <kenvandine> om26er, indeed, but an important feature
[21:38] <balloons> ping fginther
[22:07] <kenvandine> pmcgowan, i couldn't reproduce it with --wipe either
[22:07] <kenvandine> pmcgowan, it's landed!
[22:09] <pmcgowan> it has
[22:09] <kenvandine> pmcgowan, i think that means it's time to call it a day :)
[22:09] <pmcgowan> kenvandine, is 14 ready to go or need a resync?
[22:09] <kenvandine> pmcgowan, i kicked a rebuild
[22:09] <pmcgowan> ok
[22:10] <pmcgowan> we need one more day, dang
[22:10] <kenvandine> pmcgowan, we still need QA to verify it
[22:10] <kenvandine> pmcgowan, it's as far as we can take it
[22:10] <kenvandine> need QA
[22:11] <rsalveti> pmcgowan: yeah, seems we'd need at least one more day for everything to be as we expect
[22:11] <rsalveti> which is a bummer
[22:11] <pmcgowan> rsalveti, lets see what we can work out with jibel tomorow
[22:12] <kenvandine> pmcgowan, we got the silo ready for QA verification in time, i assume they will be doing verifications tomorrow right?
[22:12] <rsalveti> kenvandine: that's the idea yeah
[22:12] <rsalveti> but they got a long list it seems =\
[22:12] <kenvandine> yeah
[22:12] <kenvandine> glad we got tech switch in!
[22:13] <pmcgowan> we need to get 11,14, 0 and maybe 15 and 20
[22:13] <rsalveti> boiko: building, should be there in ~20 min
[22:13] <rsalveti> jezz
[22:13] <rsalveti> ahaha
[22:14] <boiko> rsalveti: great! I'll go grab some food meanwhile, thanks :)
[22:14] <rsalveti> pmcgowan: 9 and 3 are good to go as well
[22:14] <kenvandine> pmcgowan, in the morning can you help give them our list of priorities?
[22:14] <kenvandine> so they can work down them in that order, instead of the order in trello
[22:14] <rsalveti> indeed
[22:15] <kenvandine> at least 14 and 11 are way down on their list
[22:15] <kenvandine> i don't even see 0
[22:16] <pmcgowan> 0 failed needs fixing
[22:16] <pmcgowan> wats in 3 rsalveti ?
[22:16] <rsalveti> pmcgowan: https://launchpad.net/bugs/1421170
[22:16] <kenvandine> well good night guys!
[22:16] <robru> bfiller: just need this approved: https://code.launchpad.net/~phablet-team/camera-app/fix-failing-tests/+merge/250054
[22:16] <rsalveti> g'night!
[22:16] <robru> kenvandine: goodnight!
[22:17] <bfiller> robru: done
[22:17] <pmcgowan> oh you are here
[22:17] <pmcgowan> how's skiing? bfiller
[22:17] <bfiller> pmcgowan: trying to make sure stuff lands :)
[22:17] <bfiller> pmcgowan: skiing good, cold temps but good snow
[22:18] <pmcgowan> bfiller, sounds right, freakin cold
[22:18] <rsalveti> still prefer summer
[22:19] <bfiller> rsalveti: so tomorrow when hopefully silo 17 finally lands would you mind updating the seed before they spin the final image?
[22:20] <bfiller> rsalveti: qtdeclarative5-ubuntu-ui-extras0.2
[22:20] <rsalveti> bfiller: sure, just ping me when it lands (if you're around)
[22:20] <rsalveti> otherwise I can try to keep my eyes on it
[22:20] <bfiller> rsalveti: I'll let the guys know to ping you if I"m not around
[22:21] <rsalveti> bfiller: great, thanks