[00:02] <sergiusens> robru,  plars, doanac` we are good for the test target change (no need to install camera-app-autopilot and gallery-app-autopilot)
[00:03] <robru> sergiusens, according to the plan, plars should handle that.
[00:03] <sergiusens> robru, yeah, was just a general broadcast :-)
[00:03] <robru> sergiusens, ok great
[00:04] <robru> sergiusens, ok so i'm a little bit confused: we got the debs *out* of the seed... but where is the change that makes those click apps be preinstalled?
[00:08] <sergiusens> robru, lp:click-sync
[00:08] <sergiusens> robru, it's not a package though
[00:08] <sergiusens> robru, it's something run on snakefruit
[00:09] <robru> sergiusens, what's snakefruit? the image builder?
[00:10] <sergiusens> robru, archive
[00:10] <sergiusens> robru, meh, it's not the archive per se
[00:10] <robru> sergiusens, ah ok. well it looks like you have it under control. very well, carry on ;-)
[00:11] <sergiusens> robru, but it does have access to http://people.canonical.com/~ubuntu-archive/click_packages/click_list
[00:15]  * sergiusens will brb
[00:53] <ToyKeeper> If r224 doesn't land soon, I might not be testing it today.
[00:56] <robru> ToyKeeper, r224 of what?
[00:56] <robru> image 224?
[01:02] <sergiusens> robru, do you know of anyone else who can make the testing changes on ci?
[01:10] <ToyKeeper> Yes, image 224.  Looks like it may have landed though.  My phone lied to me, probably because I was messing with PPAs.
[01:10] <robru> sergiusens, nope, sorry. well, maybe fginther
[01:11] <robru> ToyKeeper, nope, just 223 so far. I don't think we're ready to start 224 just yet
[01:15] <robru> Alright, I'm heading out for dinner, but i should be back within an hour.
[01:17] <ToyKeeper> Hmm, where did balloons manage to get r224?
[01:17] <ToyKeeper> Oh well, will check later.
[01:37] <plars> sergiusens: robru: doanac`: psivaa: ok, the mp I proposed earlier for removing the pkg installs for gallery and camera, as well as om26er's unlocker change have both been merged.
[01:54] <robru> plars, thanks!
[02:15] <sergiusens> plars, awesome
[02:15]  * sergiusens goes to bed
[02:15] <sergiusens> ty
[02:24] <robru> kgunn, what's the scoop? are you giving up on the mir landing for now?
[02:54] <kgunn> robru: if you're still on...yeah...i can give up my silo....i'm gonna leave that line & MP's in place...i'll try again after we debug a little...
[02:57] <robru> kgunn, "can"? no need to give it up right now if you're still working.
[02:59] <kgunn> if you can leave a note with someone...tvoss will need me out to unlock platform-api...which i'm happy to allow him....until then, some of my guys might use the ppa
[02:59] <kgunn> robru: ^
[03:03] <rsalveti> kgunn: please also send an email to the ml
[03:03] <kgunn> rsalveti: which ml ?
[03:06] <robru> kgunn, was more wondering if I should expect a publish request from you anytime soon, or if I can EOD ;-)
[03:06] <robru> kgunn, sure thing
[03:06] <kgunn> robru: no way...go to bed :)
[03:06] <kgunn> or watch tv :)
[03:06] <robru> kgunn, only 7PM here ;-)
[03:06] <kgunn> not gonna happen tonight
[03:07] <rsalveti> kgunn: ubuntu-touch/phone
[03:07] <rsalveti> kgunn: didrocks had a plan to land mir today
[03:07] <rsalveti> so please just give a heads up that it's not going to happen
[03:07] <rsalveti> so he knows what happened once he's online again
[03:22] <rsalveti> robru: the build happens at 3am utc
[03:22] <rsalveti> so yeah, cdimage should be done by now already
[03:22] <rsalveti> actually, in ~20min
[05:11] <Mirv> morning
[05:30] <rsalveti> Mirv: morning
[05:30] <rsalveti> Mirv: it seems florian got the needed fixes for webkit
[05:44] <Mirv> rsalveti: url or it didn't happen!
[05:44] <rsalveti> Mirv: he updated the bug
[05:45] <rsalveti> bug 1207270
[05:45] <rsalveti> there's an additional unity-mir change
[05:46] <Mirv> rsalveti: oh, so qtwebkit does not need to revive the DPR patch, but unity-mir instead?
[05:46] <rsalveti> yeah
[05:47] <Mirv> ok, great, I'll build again today and get pope_y testing too
[06:11] <rsalveti> [07:02] <rsalveti> [07:13] <rsalveti> didrocks: image 225 should be available in a few minutes in system image
[07:13] <rsalveti> didrocks: probably asac explained already, but all tests failed because they were looking for a python module that's available in unity8-autopilot
[07:13] <didrocks> rsalveti: hey, oh, what change does it contain? It was just for the infra revert, right?
[07:13] <didrocks> yeah
[07:14] <rsalveti> that was not installed by default before either (only as a side effect of gallery-app/camera-app debs)
[07:14] <rsalveti> didrocks: just infra, but we don't know how to trigger the tests again
[07:14] <didrocks> rsalveti: right, we still have an issue with the infra in general where no tests are run but we have 83% of tests passing :)
[07:14] <rsalveti> so we just decided to do a new image
[07:14] <didrocks> yeah, sounds the best way :)
[07:14] <rsalveti> didrocks: right, well :-)
[07:14] <didrocks> thanks for looking at that!
[07:15] <didrocks> (and for the messages on the phone ML, was nice to get all updates in the morning)
[07:15] <rsalveti> the problem is that we don't know how many tests we should be running before actually running then
[07:15] <rsalveti> *them
[07:15] <rsalveti> yeah, too bad mir didn't land, more fun for today :-)
[07:15] <didrocks> right, and also, if no test run, everything is counted as a test:
[07:15] <didrocks> setup
[07:15] <didrocks> systemsettle
[07:15] <didrocks> phablet-test-run failing
[07:15] <didrocks> systemsettle
[07:16] <didrocks> teardown :p
[07:16] <didrocks> phablet-test-run is clear not 20% of the global results :)
[07:16] <rsalveti> yeah
[07:16] <didrocks> rsalveti: I'm not upset to not have Mir today TBH ;) But maybe that will be after Qt 5.2?
[07:16] <rsalveti> probably
[07:17] <rsalveti> as the last big fix for qt5.2 should be in today I guess
[07:17] <rsalveti> Mirv should know more, but florian got some additional patches for that issue
[07:19] <didrocks> ok, anyway, let's try to ensure we get Mir soonish
[07:19] <didrocks> it prooved the dogfooding was done seriously, so it's not a failure per say :)
[07:29] <Mirv> rsalveti: hey. I still have input problem with DPR
[07:30] <rsalveti> yeah :-)
[07:30] <rsalveti> Mirv: hm =\
[07:30] <Mirv> I just updated https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1207270 - graphically it's now good, aside from the one glitch I'm mentioning there
[07:30] <rsalveti> Mirv: even after unity-mir?
[07:30] <rsalveti> alright
[07:30] <Mirv> rsalveti: yes, well, it's more minor, ie unlocking is harder than before
[07:30] <Mirv> not sure if it's worth landing to Qt 5.2 PPA or not, ie is it better now than without fixes
[07:31] <Mirv> there are two images and a video there
[07:32] <rsalveti> right, awesome
[07:33] <rsalveti> let's try to get Kaleo to fix the remaining issue asap then
[08:02] <Mirv> didrocks: the landing-003 was freed from Mir, but prepare-silo still claims unity-mir is attached to there. is there a need to do reconfiguration of landing-003 with null, or something else?
[08:02] <didrocks> Mirv: hum, shouldn't, is landing-003 really freed?
[08:02] <didrocks> let me look
[08:03] <didrocks> Mirv: who freed it?
[08:03] <Mirv> didrocks: o/
[08:04] <didrocks> how did you do that? :p
[08:04] <Mirv> didrocks: with the menu option
[08:04] <didrocks> argh
[08:04] <didrocks> remember, it's written "admin only", it's not what it's supposed to :)
[08:04] <didrocks> so, this is really when the spreadsheet is out of sync with the backend
[08:04] <didrocks> remember that the spreadsheet can't run jobs in the backend
[08:04] <didrocks> the way to free something is:
[08:04] <didrocks> http://<IP_ADDRESS>/job/landing-003-3-merge-clean/33/
[08:04] <didrocks> -> build with "only free silo"
[08:04] <Mirv> right: "merge and clean with "ONLY_FREE_SILO" selected."
[08:05] <didrocks> yep :)
[08:05] <didrocks> this would have removed the line on the spreadsheet as well :)
[08:05] <didrocks> (so, normally you don't need that menu option)
[08:05] <Mirv> argh indeed. I'm updating my notes
[08:05] <Mirv> and doing merge-and-clean
[08:05] <didrocks> thanks!
[08:05] <Mirv> sorry, and thanks to you
[08:05] <didrocks> Mirv: do you have any suggestion on how to make that menu option really scary? :p
[08:05] <didrocks> Mirv: no harm done ;)
[08:06] <didrocks> it's just like, let's say, the spreadsheet is going crazy and can't sync from the backend…
[08:06] <Mirv> didrocks: "didrocks only"? :)
[08:06] <didrocks> Mirv: ahah, that can be :p
[08:06] <didrocks> ok, just need to wait on the ppa to be freed
[08:07] <didrocks> and you can take the lock!
[08:07] <Mirv> yes, preparing some manual uploads meanwhile
[08:07] <didrocks> (waow, they did build quite a lot of packages)
[08:07] <didrocks> http://<IP_ADDRESS>/job/landing-003-3-merge-clean/34/console
[08:07] <didrocks> you can see how many times people retried :p
[08:07] <Mirv> yeah, I saw there was some middle-of-the-night efforts already the day before
[08:07] <didrocks> yeah
[08:07] <didrocks> but I liked the fact that they prefer to back out
[08:07] <didrocks> and communicate
[08:08] <didrocks> very positive experience in the end
[08:08] <Mirv> yes, the process was working well
[08:08] <Mirv> also, this "do something while waiting for Qt 5.2" worked well with robru
[08:08] <Mirv> he e-mailed me on the status and also reminded to rebuild the new trunk against Qt 5.2
[08:09] <Mirv> for qtorganizer5-eds
[08:09] <didrocks> excellent
[08:09] <didrocks> Mirv: do you have a lock on the toolkit?
[08:10] <didrocks> Mirv: as for clock app, we may have a fix to be able to promote an image
[08:10] <didrocks> (but need more infos first)
[08:10] <Mirv> didrocks: yes, a lock is there on the ui-toolkit, can be removed temporarily if/when needed.
[08:11] <didrocks> Mirv: ok, let's keep an eye on that
[08:31] <sil2100> Almost though Freenode was down
[08:36] <popey> didrocks: balloons posted a new weather app at 5am (bzr 217) and asked me to test it.. I get 8 failures of 23.
[08:36] <popey> http://paste.ubuntu.com/7048809/
[08:36] <popey> http://paste.ubuntu.com/7048811/
[08:37] <didrocks> popey: so, more than the previous version?
[08:37] <didrocks> popey: are the changes related to test only?
[08:38] <popey> not analysed, just ran and pasted so far
[08:52] <popey> didrocks: aha! I think I may know why..
[08:52]  * popey tests again
[08:52] <didrocks> popey: all your fault again, I assume! :)
[08:53] <Mirv> cjwatson: was it that there is zero way of rebuilding or removing a single arch of "successfully" built package in the PPA? I've gone through the landing-006 PPA and found 12 packages that will be a problem for proposed migration because they built for powerpc or pp64el with the old Qt
[08:53] <popey> of course, my fault the phone dropped off wifi, and I have no 3g data allowance left ☻
[08:54] <Mirv> cjwatson: so the problem comes from that they depend on libqt5core5 instead of the new libqt5core5a
[08:55] <Mirv> there was a time where powerpc build was not available of qtbase, and then when ppc64el was added there were some uploads made before qtbase was rebuilt for that (in those cases powerpc binary is fine but ppc64el isn't)
[08:55] <didrocks> popey: ah, and as the tests are not isolated… :p
[08:55] <Mirv> so either those should be handled at the proposed migration time or I'll reupload 7 packages manually and have CI Train rebuild 5 packages
[08:57] <bzoltan> didrocks: would you please point me the bug report about the Clock app issue?
[08:58] <didrocks> sure
[08:58] <didrocks> bzoltan: I think it was bug #1285958
[08:58] <bzoltan> didrocks: thanks ... that is what I have too :)
[08:59] <didrocks> bzoltan: I heard qtorganizer5-eds was half the fix
[08:59] <didrocks> bzoltan: not sure about the other half :p
[08:59] <bzoltan> didrocks:  I am looking after that one ... btw, why it is not "Critical"?
[09:00] <didrocks> bzoltan: because the sdk team set it to high?
[09:00] <didrocks> Zsombor Egri (zsombi)
[09:00] <didrocks> Undecided → High
[09:00] <didrocks> and bill set to high as well before
[09:01] <bzoltan> didrocks: if you consider a bug to be critical, please ping me in the future. I can take care of the prioritization.
[09:01] <didrocks> bzoltan: sure, will do that. You were supposed to be in touch through Nicholas though
[09:01] <didrocks> not sure why he didn't happen
[09:01] <didrocks> bzoltan: as we thought first it was in the application itself
[09:02] <didrocks> I just learnt yesterday it was in the sdk
[09:02] <popey> didrocks: indeed.. FAILED (failures=2)
[09:02] <popey> getting better
[09:02] <didrocks> bzoltan: when I did pinged you
[09:02] <didrocks> popey: better than the previous version for you, with the same setup, right?
[09:02] <popey> better than the above 8 fails
[09:03] <popey> will roll back and run again to compare once I have 3 runs under my belt
[09:03] <didrocks> popey: ok, can you also try to dogfood that one like crazy, as: can we promote an image with that version?
[09:03] <popey> "that version" - the one in the store?
[09:03] <popey> It's not in the image yet
[09:04] <popey> store has 211, I'm testing 217
[09:04] <didrocks> popey: the new one
[09:04] <popey> ok
[09:05] <bzoltan> didrocks: as far as I know it was/is a problem what required fix from both sides. Anyhow, we are working on it now. I will keep you posted.
[09:05] <didrocks> bzoltan: thanks a lot, please do, we'll get that landed ASAP and kick an image with it (potentially the image we'll promote) :)
[09:05] <didrocks> the so-awaited-pre-qt5.2 image :)
[09:08] <bzoltan> didrocks: One communication  mistake we made ... I was not t old and so I was not aware that the so-awaited-pre-qt5.2 image has higher priority than the also so-awaited-qt5.2 image
[09:10] <psivaa> sil2100: didrocks: initial indication is that gallery app has some issues during the conversion to click.. camera is good
[09:12] <didrocks> bzoltan: ah, probably, I tried to make it clear in my email, but the idea is always to decouple risk
[09:12] <didrocks> psivaa: ok, please look at the gallery-app one :)
[09:13] <psivaa> didrocks: yea, the tests are looking at /home/phablet/.local/share/com.ubuntu.gallery/gallery-app/database/gallery.sqlite whilst that's available in /home/phablet/autopilot/gallery_app/data/default/.database/gallery.sqlite during the click setup
[09:13] <bzoltan> didrocks: of course... I am not against it :) we just need to double handshake these priorities
[09:13] <sil2100> psivaa: thanks for the heads up, too bad...
[09:14] <didrocks> bzoltan: yep :)
[09:14] <didrocks> psivaa: oh, so the tests need to be changed as well, do you think you can try ugly-patching those once the run is done to see the results?
[09:14] <sil2100> psivaa: ah, I thought they ran the gallery-app tests before publishing and everything was ok
[09:15] <didrocks> sil2100: I think gallery-app (debs) was still installed
[09:15] <didrocks> I'm ready to bet all my money on that
[09:15] <didrocks> and popey's one as well :)
[09:15] <seb128> can I bet popey's money as well?
[09:15] <psivaa> didrocks: i could do that.. but i'd let the other tests to finish first
[09:15] <didrocks> ahah ;)
[09:16] <sil2100> didrocks: maybe, although I saw Sergio talking to Robert about wiping the system clean and installing the click ones for testing ;p
[09:16] <didrocks> seb128: we all can, I heard
[09:16] <popey> seb128: s/money/bitcoins/
[09:16] <sil2100> But I don't want to bet your and popey's money for that!
[09:16] <didrocks> popey: what, you are a billionar then? :)
[09:16]  * sil2100 wants some dogecoins
[09:16] <popey> hah. 0.00000000000000001 bitcoin millionaire.. right?
[09:16] <didrocks> ;)
[09:16] <sil2100> Wow wow, such currency, much worth
[09:16] <didrocks> sil2100: yeah, but wiping won't remove the debs
[09:23] <didrocks> cjwatson: FYI, deployed the ppcel64 list (need to improve the logic in a long term and get a couple of hours to think about it). I'll need to do the same change for arm64
[09:26] <sil2100> didrocks: from the logs I see they were removing the debs first and then installing the clicks, but maybe they missed up on something indeed!
[09:27] <didrocks> sil2100: interesting…
[09:30] <didrocks> popey: time to dress and join us!
[09:56] <mhr3> sil2100, silo for row 40 pls?
[09:56] <sil2100> mhr3: lookin'!
[09:59] <sil2100> mhr3: assigned!
[09:59] <mhr3> sil2100, ty
[09:59] <sil2100> yw
[10:01] <Mirv> ralsina_: hi! I'm sorry but I'm going to free up the unity-scope-click silo so that Qt 5.2 landing can continue. unity-scope-click is the only package remaining from Qt 5.2 landing
[10:02] <Mirv> ralsina_: the silo wasn't marked as being tested, so that's why it cannot be released either. anyhow, it will be quick to reassign the silo and build after Qt 5.2 has landed.
[10:04] <Mirv> cjwatson: FYI I've started the powerpc/ppc64el related rebuilds in landing-006. my belief is that after those are done there are no other immediate ppc issues.
[10:05] <Mirv> because ppc64el was added late, some builds will start only when the copy will be made
[10:06] <sil2100> didrocks: I'm upgrading my device to the latest image, I have a hunch that I know what might be wrong with gallery-app, but need latest to be sure
[10:11] <cjwatson> Mirv: I can remove them from trusty-proposed after copying, but I might be able to remove those binaries
[10:11] <cjwatson> Mirv: is it still needed or are you just rebuilding everything?
[10:11] <cjwatson> Mirv: I don't think the web UI exposes it, but you should be able to remove single builds from a PPA using the API
[10:12] <cjwatson> didrocks: thanks
[10:12] <Mirv> cjwatson: well I'm doing the rebuilds now, shouldn't be too much of a problem. in case I missed something, some ppc mangling may be needed still but I went through the whole list and opened DEBIAN/control of the binary package to see
[10:13] <Mirv> cjwatson: it's good to know that there's such a thing in the API. in that case I could do / find out it too.
[10:13] <Mirv> I'm nowadays somewhat used to LP API via python :)
[10:13] <sergiusens> didrocks, I am looking at the results and feeling bad :/
[10:14] <cjwatson> Mirv: the method is BinaryPackagePublishingHistory.requestDeletion
[10:14] <sil2100> sergiusens: no worries ;)
[10:14] <sergiusens> sil2100, I can fix it easily though
[10:15] <cjwatson> Mirv: actually, it looks like I included PPA handling options in remove-package in lp:ubuntu-archive-tools
[10:15] <sil2100> sergiusens: it simply seems that gallery-app has problems with the right database directory
[10:15] <cjwatson> Mirv: so you don't even need to use the API directly, you should just be able to use that script
[10:15] <sil2100> sergiusens: oh, I was looking into that just now, but I guess you have more power over the process
[10:15] <sergiusens> sil2100, it's easier than that ;-)
[10:15] <cjwatson> Mirv: just be careful to use the -b option :-)
[10:15] <sil2100> sergiusens: so, if only you have a moment, please ;)
[10:16] <sergiusens> sil2100, it just needs to be ignored
[10:16] <cjwatson> Mirv: sorry I was up a bit late this morning, could've saved you some builds ...
[10:16] <sil2100> As I just now upgraded to the latest image
[10:16] <sil2100> sergiusens: you mean, the lack of the database in the AP tests?
[10:16] <Mirv> cjwatson: oh, nice. again, good to know. no problem, it's not the first time that PPA is seeing rebuilds after rebuilds..
[10:17] <sergiusens> sil2100, yeah; it's a save my state so I keep my database after the tests are run
[10:17] <sil2100> sergiusens: well, I guess you know more on how things look, so I leave the fix to you ;) Thanks!
[10:19] <didrocks> sil2100: keep us posted :)
[10:19] <didrocks> sergiusens: ah, what was the issue? You didn't remove the .deb packages?
[10:19] <didrocks> sergiusens: the fix will be in the click app itself or anything else?
[10:21] <didrocks> cjwatson: Mirv would be able as well to use remove-package on the ppa, right?
[10:21] <didrocks> ah, right
[10:21] <sergiusens> didrocks, in the test setup
[10:22] <didrocks> didn't backlog after that line, ignore me :)
[10:22] <didrocks> sergiusens: ok, leaving it to you then :)
[10:22] <didrocks> sergiusens: there was some additional fun infrastructure issue related to that as well btw (unity8-autopilot not pulled anymore)
[10:22] <didrocks> sergiusens: so, it relaunched a discussion with the QA team :)
[10:22] <sergiusens> didrocks, yeah, saw the unlock one
[10:23] <sergiusens> didrocks, I knew that wouldn't be me, but was scared anyways :-P
[10:23] <didrocks> heh :)
[10:23] <didrocks> sergiusens: see, any safe change always have unseen side-effects :p
[10:23] <didrocks> (that's why we should really build an image as per airline from the ppa)
[10:24] <sergiusens> didrocks, well, I never said migrating to click was easy; not with all the infra stuff that needs to happen in parallel at least
[10:24] <sergiusens> and the test rewriting
[10:24] <sergiusens> too many non click environment assumptions exist in them
[10:25] <didrocks> right
[10:25] <didrocks> anyway, let's try to get everything under the same process
[10:25] <didrocks> and dream about the future :)
[10:26] <sergiusens> didrocks, well I saw a comment from ev saying he wants to not use PPAs for anything, I guess the same thing would apply for not using branches as well
[10:26] <sergiusens> that would somehow fit in the airline
[10:27] <didrocks> yeah
[10:27] <ev> to be clear, what I said was that I want our infrastructure running the LTS as much as possible. If a non-testbed system needs additional packages, I consider that a leaky harness. If we absolutely must install packages and they're not in the LTS, we should backport them and put them in a PPA.
[10:27] <didrocks> ev: no ppa?
[10:28] <ev> I do not want us upgrading to trusty all over the place.
[10:28] <didrocks> hum, not sure you are talking about the same thing
[10:28] <sergiusens> ev, oh, I misunderstood, so the PPA part was fine then?
[10:28] <didrocks> building packages and testing those packages :)
[10:28] <ev> that's the only place I mentioned PPAs, as far as I recall
[10:28] <sergiusens> didrocks, ignore me then ;-)
[10:29] <ev> :)
[10:29] <ev> back in a tick
[10:30] <sergiusens> didrocks, I was trying to get infrastructure changes under control as well ;-)
[10:31] <didrocks> sergiusens: I'm *happily* ignoring you! (kidding :p)
[10:34] <mhr3> sil2100, didrocks, wrt row 40, since there's a qml plugin now in mediascanner2, ppc et al builds won't finish, so even though it's saying that it's still building, it already built everything that can be built
[10:35] <sil2100> qml plugin? uuh
[10:35] <didrocks> mhr3: ah, so it's built on ppc in the distro?
[10:35] <sil2100> didrocks: yes, I remember that being on ppc
[10:35] <mhr3> didrocks, yea, it didn't have qml plugin until now
[10:36] <didrocks> mhr3: ok, let me check the rdepends
[10:36] <cjwatson> didrocks: yes, the PPA owner can remove publications
[10:37] <didrocks> ok, seems we don't have any rdepends from libmediascanner-2.0-0 that are on those archs
[10:37] <didrocks> mhr3: so, I'll be able to remove from the distro
[10:37] <mhr3> didrocks, cool, thx
[10:37] <didrocks> cjwatson: meanwhile, you can stop the build (if the rest is published) and start testing
[10:37] <didrocks> argh
[10:37] <didrocks> mhr3: ^
[10:37] <didrocks> sorry cjwatson :)
[10:38] <mhr3> didrocks, already tested
[10:38] <mhr3> didrocks, do i just abort the jenkins job?
[10:38] <didrocks> ok, let me remove the packages
[10:38] <didrocks> mhr3: yep
[10:38] <mhr3> k
[10:38] <didrocks> mhr3: so, removing powerpc, ppc64el and arm64
[10:39] <mhr3> +1
[10:39] <didrocks> fortunately, this dance will be soon not needed
[10:39] <ralsina_> Mirv: ack, np. It was a matter of which thing got done first :-)
[10:40] <didrocks> ralsina_: we normally try to discuss with you first, but timezone one and seeing the rush in Qt 5.2, wasn't easy, sorry man :)
[10:41] <mhr3> ralsina_, i warned you yesterday :)
[10:43] <davmor2> didrocks: much happier with 225 + new weather app.  I have all the apps open now and still no crash, I'll go back to opening and closing them all a couple of times which is a likely user trait (open an app, can't remember why, close it, remember why and open it again) and see if that triggers anything
[10:43] <didrocks> mhr3: http://paste.ubuntu.com/7049288/ -> done
[10:43] <didrocks> mhr3: you will be able to rerun build with "watch only" if you want to get it clean (after next publisher cycle) :)
[10:44] <didrocks> davmor2: excellent!
[10:45] <mhr3> didrocks, will do, thx
[10:50] <davmor2> didrocks: indicators are back to their old tricks of closing as soon as you select and item, so you can't select geoip and gps for example
[10:51] <didrocks> davmor2: oh, this is fairly new, right?
[10:52] <didrocks> davmor2: wasn't that one disappearing with a reboot?
[10:52] <davmor2> didrocks: it's an old issue that was fixed and now seems to be back
[10:53] <davmor2> I will reboot to check
[10:53] <davmor2> need to go to mother-in-laws back in an hour
[10:53] <didrocks> ok, see you!
[11:03] <sergiusens> sil2100, can you be my reviewer? https://code.launchpad.net/~sergiusens/gallery-app/test_fixes/+merge/209891
[11:07] <sil2100> sergiusens: sure ;)
[11:07] <sil2100> Let me check
[11:09] <sil2100> sergiusens: code looks ok, testing in a moment :)
[11:11] <sergiusens> sil2100, I was compelled to refactor; but I don't want to introduce any errors
[11:19]  * didrocks likes the safety approach from sergiusens :)
[11:20] <sil2100> sergiusens: so far it seems to be working fine on my device, but I have been wondering if maybe we shouldn't remove the database/thumbnails after the tests are finished when there was nothing previously?
[11:20] <sil2100> sergiusens: doesn't seem to be serious enough for us to care though
[11:24] <sergiusens> sil2100, shouldn't be a problem as we remove it prior to running
[11:24] <didrocks> sil2100: ok, going out for a run, so please feel free to work with sergiusens to get those released :)
[11:24] <sergiusens> sil2100, could be considered though
[11:24] <didrocks> bzoltan: refresh us when you get any news on the sdk fix for clock-apps
[11:24] <bzoltan> didrocks: of course
[11:25] <sil2100> didrocks: sure ;)
[11:27] <sergiusens> sil2100, I preloaded l42 in the train to get the silo
[11:27] <sil2100> sergiusens: ok, let's consider that some other time
[11:27] <sil2100> Anyway, all tests pass now, yay
[11:28] <sil2100> sergiusens: approved
[11:29] <sil2100> Let me assign a silo
[11:31] <sil2100> Mirv: eeek!
[11:31] <sil2100> sergiusens: hmmm
[11:31] <sil2100> sergiusens: come to think of it, do we need a silo for gallery-app? It's click now, right? What's the way it gets released now?
[11:32] <sil2100> sergiusens: since I can't assign a silo because of Mirv's Qt 5.2 landing, and I don't know now if we should ask Mirv to release the lock for it for a moment or maybe we can simply release it to the click store some other way
[11:34] <sergiusens> sil2100, can I merge to trunk myself?
[11:35] <sergiusens> if I can do that; that solves the issue
[11:36] <popey> davmor2: #225, first run of music app unity seemed to barf..
[11:37] <sil2100> sergiusens: I guess we'll have to deprovision gallery-app from CITrain anyway, let me poke Mirv just to be sure
[11:37] <sil2100> Mirv: ping
[11:37] <sergiusens> sil2100, I think Mirv just needs to rebuild due to the qreal issue
[11:38] <popey> davmor2: how do I know if this is the known unity issue?
[11:38] <sil2100> If it's an empty merge rebuild then I guess we have green light on pushing
[11:40] <Mirv> sil2100: pong
[11:41] <Mirv> sil2100: so why it needs to be deprovisioned if it's click now? not that I'd otherwise have anything against it
[11:45] <popey> davmor2: got white screen starting system settings too
[11:47] <Mirv> elopio: any more luck with AP test runs / adb issues?
[11:49] <sergiusens> Mirv, sil2100 with that logic, you don't need to lock it yourself either ;-)
[11:50] <sergiusens> Mirv, I need to merge to trunk; that's where the tests come from
[11:50] <Mirv> sergiusens: I need to lock it so that when Qt 5.2 is landed there is no package in the archives that depends on libqt5core5 which would prevent proposed migration
[11:51] <sil2100> sergiusens: just merge it ;)
[12:01] <davmor2> popey: working fine here
[12:01] <davmor2> popey: is there a crash file in /var/crash?
[12:01] <davmor2> popey: either for unity8 or qmlscene
[12:02] <popey> davmor2: yes, one for unity8
[12:02] <davmor2> popey: okay so I'll pm you with what to do as soon as I open the file
[12:05] <sil2100> sergiusens: so, how's it going?
[12:06] <sergiusens> sil2100, hey, missed that comment; merged and no building the click
[12:07] <sil2100> Awesome!
[12:08] <davmor2> popey: didrocks: I'm going to do a bootstrap install and just ensure that everything is working as smoothly from a full install rather than just an update
[12:08] <sergiusens> sil2100, this might be a problem in the future as gallery is click + deb (and so are all the other ones in bfiller's umbrella)
[12:08] <sergiusens> the core community apps don't have this problem as they don't land in distro
[12:08] <davmor2> didrocks, popey: but for me so far big thumbs up I don't know what happened but everything has been opening fine
[12:10] <popey> davmor2: mine was a clean fresh install of the previous image, updated to 225
[12:10] <popey> sergiusens: we're planning to land core apps in universe soon...
[12:11] <sergiusens> popey, hmm; that's going to be interesting
[12:11] <sergiusens> popey, why not just click?
[12:11]  * sergiusens wonders about contradicting goals
[12:12] <popey> sergiusens: click packages don't work on desktop do they?
[12:12] <davmor2> popey: so my updated version was working really well but it is updates with data from a couple of days ago and I don't want false hope pinned on possibly altered files :)
[12:12] <popey> unless that's changed since I last spoke to cjwatson about it
[12:13] <cjwatson> not yet, I still hope to get it working for 14.04 but it'll be tight
[12:13] <cjwatson> and there's still the issue of presenting unconfined click apps being a dangerous thing to do
[12:13] <cjwatson> so actually I'll probably only get the infrastructure in place for 14.04 if that, it won't be something we'll be able to advertise
[12:14] <cjwatson> we can't really do click apps properly on X because we can't confine them properly
[12:15] <popey> sergiusens: ^
[12:15] <sergiusens> popey, they do
[12:15] <cjwatson> err they don't
[12:15] <sergiusens> well they don't work confined; true
[12:15] <cjwatson> ok, you can install them by hand, kind of
[12:15] <cjwatson> but there's no aptdaemon integration
[12:16] <sergiusens> cjwatson, I just upstart-app-launched com.ubuntu.calculator_calculator_${version} on unity7
[12:16] <cjwatson> and getting the right click install invocation is tricky.  we shouldn't be advertising them to users
[12:16] <sergiusens> right
[12:16] <cjwatson> sure, it can be done by hand
[12:16] <cjwatson> it's only sensible for developers though
[12:16] <cjwatson> reasonable way to test/develop your app, not a reasonable way to deliver it
[12:17] <cjwatson> we agreed at the client sprint that we oughtn't taint the general message of click by advertising it when it's basically a malware vector
[12:17] <sergiusens> I would just focus on them working with unity8/desktop which should be the focus next cycle anyways (unless priorities changed)
[12:18] <cjwatson> well next LTS cycle anyway, yes
[12:18] <sergiusens> right
[12:20] <popey> davmor2: are you flashing clean right now?
[12:21] <davmor2> popey: just finished now I'm transferring things onto it
[12:22] <davmor2> popey: and without the fix weather app is crashing
[12:24] <popey> davmor2: can you try this... swipe to home after putting music on it - I see no thumbnails yet - tap a song and click play, quickly
[12:24] <popey> before it has a chance to get thumbnails etc
[12:25] <popey> thats when I had the unity crash
[12:25] <davmor2> will do let me get the music on first :)
[12:27] <popey> yeah, you kinda need to be quick before mediascanner does its stuff
[12:27] <sil2100> Mirv: just to double check - there is no lock required for dbus-cpp, location-service or platform-api regarding Qt5.2, right? Didn't see those on the pad ;)
[12:28] <Mirv> sil2100: yep, those don't depend on Qt
[12:28] <davmor2> popey: yeah I think I missed it all mine have album art (well all the ones that it thinks has album art) :)
[12:30] <sil2100> \o/
[12:31] <Mirv> popey: davmor2 too: beta1 is obsolete -> if you reflash, only add landing-006 (without reflashing or manually upgrading, you keep older versions of unity8 at least)
[12:31] <Mirv> s/upgrading/downgrading/
[12:33] <davmor2> Mirv: nice, does 006 have the dpi fix in play now?
[12:34] <davmor2> popey: I'm bound to reflash some point I'll try it again as the music is transferring see if I can't trip it up that way :)
[12:37] <tvoss> sil2100, didrocks can I get a silo for the process-cpp landing, and one for dbus-cpp, too?
[12:41] <davmor2> popey, didrocks: weather app updated now everything works :)
[12:41] <Mirv> davmor2: DPR fix by apt-add-repository ppa:canonical-qt5-edgers/qt5-beta-proper - I'm uncertain if to put it yet in landing, testing and after that opinions very much welcome! it turned out the graphical glitch is no more, the unlocking/input problem only one remaining and Kaleo is now awake
[12:48] <sil2100> tvoss: I already assigned for dbus-cpp, it's building
[12:48] <sil2100> tvoss: let me see the process-cpp one
[12:48] <tvoss> sil2100, thanks
[12:48] <ogra_> dbus-cpp is dead, long live dbus-go
[12:48] <ogra_> :P
[12:49] <sil2100> tvoss: so, line 7 is ready for silo assignment, yes? Since we didn't touch it as it's set to Ready: No ;p
[12:49] <seb128> sil2100, can we still get landing for components in the old "autolanding" schema (e.g not in CI train)?
[12:49] <Mirv> didrocks: with a hunder packages the package building status check is a bit slow, maybe it could be parallized a bit some day http://<IP_ADDRESS>/job/landing-006-1-build/65/console
[12:50] <didrocks> seb128: no, it's unwired now
[12:50] <seb128> didrocks, then manual uploads? ;-)
[12:50] <seb128> didrocks, it still autocommit to trunk so I was unsure
[12:50] <didrocks> seb128: I don't think so, we need to sort out and find a lander
[12:50] <didrocks> seb128: yeah, that's going to be removed next week
[12:50] <tvoss> sil2100, referering to 35 here
[12:50] <seb128> didrocks, so if we have no lander we get stucked?
[12:51] <didrocks> seb128: we need to find someone owning the component
[12:51] <seb128> didrocks, I guess I'm just going to wait for you to need to land the new icons for touch, that's going to mean landing ubuntu-themes one way or another :p
[12:51] <didrocks> seb128: we can have an existing lander taking it as well
[12:51] <seb128> I don't want to take it
[12:51] <seb128> and I didn't find anyone to do it
[12:51] <sil2100> tvoss: oh, ok
[12:52] <didrocks> seb128: who touch this package the most?
[12:52] <seb128> so I guess I'm just going to wait for somebody to need theme updates enough to sort it out
[12:52] <sil2100> tvoss: that one is set to Ready: no as well, but let me see if we can assign
[12:52] <seb128> didrocks, design?
[12:52] <seb128> tiheum
[12:52] <seb128> didrocks, you? ;-)
[12:52] <didrocks> Mirv: it's only the checking, and packages are not checking once published on all archives, not really sure we need to parallelize that
[12:52] <seb128> didrocks, I saw your mrs for the packaging cleanups, adding a new binary, etc
[12:52] <didrocks> seb128: I'm happy to take it if needed
[12:53] <seb128> thanks
[12:53] <Mirv> didrocks: yeah, might be
[12:54] <sil2100> tvoss: it might be a problem with assigning process-cpp, as Mirv has a lock on unity-mir right now for Qt 5.2
[12:55] <tvoss> sil2100, ack
[12:56] <sil2100> brb, jumping out for lunch
[13:08] <elopio> Mirv: the device issues where supposed to be fixed, but now it says error: device not found :/
[13:08] <elopio> I'll retry.
[13:11] <davmor2> we need to stop the haptic feedback on camera snapshot button, If you zoom in and try to take a photo is blurs it all because of the vibration :)
[13:12] <didrocks> ahah ;)
[13:16] <Mirv> :(
[13:17] <Mirv> elopio: just update: landing-006 PPA _only_ now
[13:17] <davmor2> didrocks: https://bugs.launchpad.net/camera-app/+bug/1289353 only bug to date
[13:18] <didrocks> davmor2: ok, sounds gooddddd! :)
[13:19] <elopio> Mirv: it seemed to be flashing. I stopped it, updated the PPA parameters, and ran it again.
[13:20] <Mirv> elopio: ok, let's see..
[13:20] <didrocks> psivaa: do you mind looking at the test results and telling if all issues are known ones/due to the crash?
[13:21] <psivaa> didrocks: sure, just a sec. was trying to rerun gallery_app with the modified path in the test.. having some issues
[13:21] <didrocks> psivaa: don't worry too much on that one. sil2100/serio were on it I guess :)
[13:24] <psivaa> didrocks: the difference in 225 is that there is webbrowser and messaging app crashes and have the associated failures
[13:24] <didrocks> psivaa: ok, d8f8?
[13:24] <psivaa> didrocks: the other failures were flakiness/qmlscene crash and known clock app failure
[13:25] <psivaa> didrocks: let me check that
[13:25] <didrocks> ok ;)
[13:26] <davmor2> didrocks, popey: so after playing on this for an hour this is the only thing in /var/crash http://paste.ubuntu.com/7049915
[13:26] <didrocks> davmor2: not bad, so no application crash on regular application startup?
[13:27] <cjwatson> what's the desktop hook crash?
[13:27] <davmor2> didrocks: not so far only tested the core apps post fresh flash so I'm going to install a few of the common click apps and see what happens then
[13:28] <cjwatson> not seeing such a thing on errors.u.c or LP
[13:28] <davmor2> didrocks: but it is looking promising so far :)
[13:28] <didrocks> davmor2: ok :)
[13:28] <davmor2> cjwatson: I get it on every fresh install
[13:28] <didrocks> cjwatson: yeah, I don't know how e.u.c is supposed to work and publish the data, I've several reports which never showed up
[13:28] <didrocks> (from the phone)
[13:29] <cjwatson> oh, there is something on errors.u.c, it's just making my browser incredibly slow ...
[13:29] <cjwatson> Yeah, I have it here too
[13:29] <psivaa> didrocks: messaging app is d8f8
[13:31] <davmor2> cjwatson: I wonder if it is something to do with the touch start guide as it is on all fresh installs without actually unlocking the phone
[13:31] <psivaa> didrocks: and the same with webbrowser app crash
[13:32] <cjwatson> davmor2: no, it's a click hook
[13:32] <cjwatson> those run on session startup
[13:32] <cjwatson> davmor2: does yours contain "AppID: com.ubuntu.notes_notes_1.4.242"?
[13:34] <cjwatson> davmor2: this is the thing that updates ~/.local/share/applications/.  it seems to have an appropriate .desktop file for notes here though, and the .crash file is labelled "RecoverableProblem"
[13:34] <davmor2> cjwatson: duplicate sig for icon-path.....notes_notes_1.4.242
[13:35] <davmor2> cjwatson: and AppID: is indeed com.ubuntu.notes_notes_1.4.242
[13:36] <cjwatson> it's not notes' fault, though
[13:37] <didrocks> psivaa: I don't really mean it but "great" :)
[13:37] <didrocks> psivaa: thanks a lot for looking!
[13:37] <cjwatson> oh, maybe it is
[13:37] <davmor2> cjwatson: I'll leave that one with you then :)
[13:37] <psivaa> didrocks: haha, yw :)
[13:38] <davmor2> lunch
[13:38] <cjwatson> davmor2: right, the problem is simply that notes-app.desktop says Icon=notepad but there's no notepad icon in the package
[13:39] <cjwatson> davmor2: bug 1267882
[13:56] <davmor2> popey: care to confirm https://bugs.launchpad.net/camera-app/+bug/1289353
[13:57] <Mirv> didrocks: sil2100: quick FYI http://<IP_ADDRESS>/job/landing-006-1-build/65/console seems to have gotten confused that various ppc64el builds are ongoing while those builds do not exist
[13:58] <Mirv> at least some of the packages were uploaded before ppc64el was added to the PPA. but that didn't happen before I now fixed a couple of other ppc builds today.
[14:00] <didrocks> Mirv: hum… let me look then, seems I was too quick on how fixing it (relying on what I've done on other archs)
[14:01] <davmor2> popey: if you install a click app does the click store part refresh the whole scope?
[14:01] <didrocks> Mirv: it's really really interesting, it's in the ARCHS_TO_EVENTUALLY_IGNORE list though
[14:02] <didrocks> with:
[14:02] <didrocks> # an arch we will ignore for publication if latest published version in dest doesn't build it
[14:02] <didrocks> I guess they don't exist in dest
[14:02] <didrocks> (and it was working for other components like powerpc until then)
[14:03] <didrocks> Mirv: and seems it works for the rest, like http://<IP_ADDRESS>/job/landing-003-1-build/62/console
[14:03] <cjwatson> I wonder if copying the source with binaries over itself would create the missin gbuild record
[14:03] <cjwatson> *missing build
[14:03] <cjwatson> I think it probably would
[14:04] <Mirv> (sorry hangout after hangout)
[14:04] <didrocks> cjwatson: ahah, that might explain…
[14:04] <Mirv> I don't immediately have anything new to build though, before DPR input branch is final
[14:04] <didrocks> cjwatson: don't you think the "no signer" as well will be an issue?
[14:05] <cjwatson> what "no signer"?
[14:05] <didrocks> cjwatson: https://launchpad.net/~ci-train-ppa-service/+archive/landing-006/+packages
[14:05] <cjwatson> oh, on +packages?  that just means it's a copy
[14:05] <didrocks> ok
[14:05] <cjwatson> from a Debian import I presume
[14:05] <cjwatson> try: copy-package -p ci-train-ppa-service --ppa-name landing-006 -b qtsvg-opensource-src
[14:06] <cjwatson> I think
[14:06] <cjwatson> hang on a sec
[14:06] <seb128> didrocks, Mirv: things like ubuntu-system-settings are locked until qt5.2 lands right? (nothing urgent, we have some bugfixes/tweaks and I was pondering putting a landing ask for those)
[14:06] <didrocks> cjwatson: sure
[14:06] <didrocks> seb128: I think you're part of his set, let me check
[14:07] <didrocks> seb128: yeah
[14:07] <didrocks> popey: alarms were working in last promoted image, right?
[14:08] <cjwatson> didrocks: yep, can you try the above?
[14:09] <didrocks> cjwatson: sure
[14:09] <popey> didrocks: on a hangout atm...
[14:09] <cjwatson> it's actually supposed to be forbidden by copy-package but that check isn't working due to a bug somewhere; but that's all to the good :)
[14:09] <didrocks> cjwatson: done
[14:10] <cjwatson> there you go, https://launchpad.net/~ci-train-ppa-service/+archive/landing-006/+build/5668902
[14:10] <cjwatson> magic
[14:10] <sil2100> thostr_: hi! I'll try landing your landing-001 in a moment
[14:10] <cjwatson> so you can do that for all affected packages
[14:10] <didrocks> ah nice :)
[14:10] <didrocks> Mirv: ^
[14:10] <didrocks> thanks cjwatson
[14:11] <rsalveti> morning
[14:11] <didrocks> hey rsalveti
[14:11] <Mirv> that's magic, thanks cjwatson :)
[14:11] <rsalveti> didrocks: hey, did our revert work in the end?
[14:12] <didrocks> rsalveti: the Mir one? we flushed out yet, so that Mirv finish the Qt 5.2 landing
[14:12] <didrocks> syet
[14:12] <didrocks> -yet
[14:12] <didrocks> ECANTTYPE
[14:12] <rsalveti> didrocks: oh, cool, but was asking about the dashboard revert
[14:12] <rsalveti> hopefully can we can fix remaining qt5.2 issues
[14:13] <didrocks> rsalveti: oh, asac's fix was good and working for the time being :)
[14:13] <didrocks> we had an issue due to gallery-app click conversion
[14:13] <didrocks> (tests looking at the wrong directory)
[14:13] <didrocks> but sergiusens fixed it
[14:13] <didrocks> and weather-app fix is in
[14:13] <didrocks> we are just pending on the clock-app fix (in the sdk?) from zsombi and bzoltan for now to decide if we can get an image promoted
[14:14] <didrocks> davmor2 is collecting data on the number of crash in "normal" usage
[14:14] <didrocks> so that we can assess
[14:14] <bzoltan> didrocks: zsombi is on the Qt5.2 standup, he will tell you the details after that
[14:14] <didrocks> thanks bzoltan
[14:15] <didrocks> ogra_: would have been good if you used the train for mtp btw (as there is an upstream branch)
[14:16] <cjwatson> didrocks,Mirv: so I guess you just need to run: copy-package -p ci-train-ppa-service --ppa-name landing-006 -b qttools-opensource-src libqtdbusmock unity-voice libqtdbustest libdbusmenu-qt qtserialport-opensource-src qdjango qtscript-opensource-src
[14:17] <cjwatson> we have ten ppc64el builders, so ;-)
[14:19]  * didrocks did to win some time for Mirv
[14:19]  * sergiusens reads
[14:20] <elopio> asac: I'm wondering what you would like to see on the qt5.2 jenkins results to be happy about releasing it.
[14:20] <elopio> taking the notes app as an example, their user acceptance tests are failing but not because of anything that affects a user story.
[14:20] <sergiusens> rsalveti, didrocks, the gallery fix should land in the next image build
[14:20] <elopio> asac: it's a combination of poorly written tests, with not using the right tool, and a bug we are hitting by a combination of those two things.
[14:20] <Mirv> didrocks: thanks for helping
[14:21] <elopio> asac: if you want the dashboard to be green, it will take some time to improve the tests.
[14:21] <didrocks> sergiusens: published in the store, right?
[14:21] <davmor2> ogra_: daft question can't you wait adb on mtp loading?
[14:21] <rsalveti> sergiusens: didrocks: great
[14:21] <bregma> hey didrocks, it looks like we need to bump our Nux ABI, which should really have a package version change -- do I just go ahead and manually dch the debian/changelog or is there a better way under ci-train
[14:21] <ogra_> davmor2, no, they are separate and can run independently
[14:21] <davmor2> ogra_: ah okay now it makes more sense :)
[14:22] <didrocks> bregma: just do it manually in debian/changelog. The commit message associated to it though won't be collected (as you change debian/changelog manually)
[14:22] <didrocks> bregma: but please, don't land that for now, as it may impact the Touch image
[14:22] <didrocks> davmor2: I can't get the alarm working even on the promoted image
[14:23] <sergiusens> nux impacting touch still?
[14:23] <bregma> didrocks, we're hours away from landing, I'm just trying to get our ducks in a row
[14:23] <didrocks> bregma: ok, ensure all you dependencies are sorted out :)
[14:23] <didrocks> sergiusens: we still install libunity-core, so nux as well
[14:23] <ogra_> sergiusens, havent you heard ? we port from Qt to nux now .. the 5.2 landing is to painful :P
[14:24] <sergiusens> didrocks, how do I cleanly delete line 42? do you have a script?
[14:24] <didrocks> sergiusens: it didn't land?
[14:24] <sergiusens> ogra_, what?
[14:24] <ogra_> :)
[14:24] <didrocks> sergiusens: I meant, no silo/package side?
[14:25] <davmor2> didrocks: first crash by the look of it,  I used OSMtouch opened a link and then closed the browser once the link had opened, crunch. Looks like the phone is just locked
[14:25] <sergiusens> didrocks, I followed sil2100's rec
[14:25] <didrocks> davmor2: please write and report :)
[14:25] <bregma> aren't we  having a session at the next UDS to discuss moving Unity8 from Qt to Nux?
[14:25] <didrocks> sergiusens: we won't have any desktop .deb package landing ever?
[14:25] <sil2100> didrocks: it's a click package right now, so we're not really using CITrain for those anymore, right?
[14:26] <sergiusens> didrocks, this doesn't affect desktop; and the deb is still needed for desktop
[14:26] <didrocks> sergiusens: but you want your branch to be merged to trunk,right?
[14:26]  * sergiusens would prefer getting rid of debs sooner; but seems it won't be happening soon
[14:26] <seb128> bregma, what are you landing next?
[14:26] <sergiusens> didrocks, it's already merge (think of it as a translation update)
[14:26] <didrocks> ah you did it manually
[14:26] <didrocks> ok
[14:26] <sil2100> ;p
[14:27] <didrocks> so yeah, just delete the line
[14:27] <didrocks> or put "Landed"
[14:27] <didrocks> in column 3
[14:27] <didrocks> manually
[14:27] <didrocks> it will turned green
[14:27] <sil2100> It's a translation merge, it's translating from 'broken tests' to 'working tests'
[14:27] <sergiusens> sil2100, for the record; citrain is still necessary; debs are still required
[14:27]  * sergiusens wants to run aways from the process :-)
[14:27] <davmor2> didrocks: think it might of been the frame buffer the phone seems fine just the gfx stuck and no crash
[14:28] <didrocks> davmor2: maybe you want someone from kgunn's team to remotely debug?
[14:28] <sil2100> sergiusens: I think I understand, but here anyway we would have problems with Mirv's Qt merge
[14:28] <davmor2> didrocks: had to reboot to get it back up and see if it was reproducible
[14:28] <bregma> seb128, we're trying to prepare the lockscreen, we'll want to coordinate some landings with you for that
[14:29] <sergiusens> sil2100, yeah, it does't matter here particularly
[14:29] <sergiusens> sil2100, but I would prefer an either/or approach instead of an and
[14:30] <didrocks> it will be restack on top of Mirv's landing
[14:30] <didrocks> for the deb part
[14:30] <seb128> bregma, right, that's why I'm asking, I'm still pondering the details (Trevinho started an email discussion early today, should probably have CCed you, about changing gnome-screensaver to trigger the unity locking under Unity)
[14:30] <asac> elopio: at best same results as on main dashboard
[14:30] <asac> elopio: if not, we should look at the cases
[14:30] <asac> and understand then a bit
[14:30] <didrocks> asac: elopio: the only failure you should see now are the clocks and weather app ones
[14:30] <asac> didrocks: and crashes randomly
[14:30] <asac> no?
[14:31] <didrocks> asac: hum, we still have crashes with 5.2?
[14:31] <didrocks> asac: all crashes we have are the d8f8 ones
[14:32]  * didrocks erases user-data
[14:33] <bregma> seb128, as long as we're making progress:  I'd like to land everything in a single silo (I've started line 43 for this)
[14:33] <seb128> bregma, +1
[14:33] <seb128> bregma, thanks, it's about time to land that ... that's the one remaining feature right? then bug fixing? ;-)
[14:33] <didrocks> seb128: bregma: pleae do test your landing on touch
[14:34] <bregma> seb128, right
[14:34] <didrocks> it's really not the time to break it :)
[14:34] <seb128> bregma, btw you might want to do a landing to fix windows shrinking first, before people hunt your team down because that's driving them crazy
[14:35] <seb128> didrocks, yeah, don't worry, I don't think that's likely to land before qt5.2, locking is going to need integration with GNOME components and indicators and we didn't sort out those details yet
[14:35] <elopio> didrocks, asac: yes, I understand that all the errors not in the main dashboard are a regression caused by the qt5.2 upgrade. But if it doesn't affect the current user experience at all, I'm wondering why do we see it as critical and a blocker, instead of high priority to be fixed before april.
[14:35] <bregma> seb128, ack, the lockscreen may stretch into next week at the current rate
[14:35] <didrocks> elopio: because then it's hard to know if we have another regression or if the failure is impacting even more
[14:35] <didrocks> elopio: and we missed real regressions due to that in the past
[14:36] <tvoss> popey, ping
[14:40] <popey> tvoss: pong
[14:41] <tvoss> popey, hey there, can you help with testing of silo 3?
[14:41] <didrocks> popey: and my question first! :p
[14:41] <popey> heh
[14:41]  * didrocks reflashed/bootstrapped in between
[14:42] <popey> didrocks: no, because the clock app can't be updated in latest promoted
[14:42] <popey> well, thats partly the problem.
[14:42] <didrocks> popey: so, we don't have user regression on that one, just tests regression?
[14:42] <didrocks> on clock apps
[14:43] <popey> well, alarms dont work on #194, so no.
[14:43] <didrocks> it did work in the past, right?
[14:43] <didrocks> or am I crazy?
[14:43] <popey> only in non-promoted images
[14:43] <didrocks> ok
[14:43] <popey> #194 is last promoted right?
[14:43] <didrocks> yep
[14:43] <popey> It's what I have on my main phone
[14:43] <popey> and no alarm clock in the indicator when I set alarms
[14:43] <didrocks> popey: so, there actually only test regression on clock
[14:43] <popey> ok
[14:43] <didrocks> no user-visible regression?
[14:44] <popey> right
[14:44] <didrocks> ok
[14:44] <elopio> didrocks: well, yes. The thing is that we are finding some of these bugs through autopilot just by coincidence. It's not the right tool for it in most of the cases.
[14:44] <elopio> what I'm trying to define is a process to go back to green.
[14:44] <elopio> If what we want is to get all the bugs fixed, then I don't have to do anything. Report the bug and wait for the devs to fix it.
[14:44] <elopio> If what we want is just to be green again, I can workaround the issue and make all the tests pass.
[14:44] <elopio> What I would really want is to refactor the tests so we leave autopilot only checking user stories, and we use lower level tools and tests to check everything else.
[14:45] <didrocks> elopio: it's not waiting for the devs, it's getting status, pinging the devs, trying to get ETAs and so on
[14:45] <elopio> that will leave us with autopilot tests still failing for some time. Then they will go green, but the bug will not yet be fixed. What will be failing now are the unit tests.
[14:46] <didrocks> elopio: well, putting stuff that degrade test results don't allow us to know if there is a regression then
[14:46] <didrocks> and we never recover
[14:46] <didrocks> look at Mir last cycle
[14:46] <didrocks> and maguro
[14:46] <didrocks> we never went back to 100%
[14:46] <didrocks> and we never knew if it was a race or a regression, loosing hundreds of hours
[14:46] <didrocks> but yeah, agreed that some part should be unit
[14:46] <didrocks> so
[14:46] <didrocks> 15:44:17     elopio | If what we want is just to be green again, I can workaround the issue and make all the tests pass.
[14:46] <didrocks> -> seems to me the best path?
[14:47] <didrocks> ogra_: anything again building an image now?
[14:47] <ogra_> nothing at all
[14:49] <didrocks> [14:49] <elopio> didrocks: well, no. Unless we block new releases for a project based on the autopilot results on the dashboard, AND on the critical bugs reported against the project.
[14:49] <didrocks> sil2100: popey: davmor2: this will be the promotion candidate ^
[14:50] <sil2100> !!!
[14:50] <davmor2> didrocks: 3 [14:50] <popey> zoiks
[14:50] <didrocks> elopio: why critical bugs and not on autopilot results on the dashboard first?
[14:50] <sil2100> I like the sound of that
[14:50] <popey> 126 is a bit retro ☻
[14:50] <elopio> this would be so much easier for me to discuss if you speak spanish, or we were at a bar drinking :)
[14:50] <didrocks> heh :)
[14:50] <elopio> didrocks: because I would like autopilot to test only user stories, right?
[14:51]  * sil2100 didn't even notice the typo ;p
[14:51] <didrocks> elopio: I think it's too late on the cycle for doing that reshaping
[14:51] <didrocks> we learnt what gave "landing things with test failing" multiple times already
[14:51] <davmor2> didrocks: I don't want my phone back in the stoneage
[14:51] <elopio> our current suite is testing a lot more than that, and that's why I'm having so many troubles checking the results.
[14:51] <didrocks> davmor2: ahah :)
[14:51] <didrocks> elopio: agreed, but I don't think that the Qt 5.2 transition will be a way to block on that
[14:51] <didrocks> so I would propose, landing 5.2 finishing trusty
[14:52] <didrocks> and then, we can have that as a goal
[14:52] <didrocks> repurposing AP to AP tests
[14:52] <didrocks> and not unit test
[14:52] <didrocks> but not something that needs to be decided on the fly
[14:53] <sil2100> davmor2: hmm, I can't seem to reply to a message by using the indicator - is that a known problem?
[14:54] <davmor2> didrocks: it lasted too long weather app finally didn't open :D  That's not too annoying though 2hr 30 minutes of hammering apps one mir lock up one app not opening :)
[14:54] <davmor2> sil2100: worked here
[14:55] <didrocks> davmor2: yeah, I won't call that "user blocker"
[14:55] <didrocks> I will call that "popey blocker" :p
[14:55] <didrocks> "If I do x, y, z, and then back o and p, I'm getting d"
[14:55] <davmor2> sil2100: just retested and it worked again
[14:56] <sil2100> Strange
[14:56] <sil2100> For me the 'Send' button was grayed out all the time
[14:56] <davmor2> didrocks: ToyKeeper is better, If I drag in all the 4 sides I get 6 images on the screen
[14:56] <Mirv> dum dum
[14:57] <didrocks> davmor2: ahah :)
[14:57] <davmor2> Mirv: Dum dum
[14:57] <elopio> didrocks: I agree it's late, and its a goal for next cycle.
[14:57] <elopio> so what I'm asking is, now what should I do with the notes?
[14:57] <elopio> As you said, get a dev to dig into the issue and get it fixed, that's ok. But in the mean time,
[14:57] <elopio> if I workaround the bug or improve the test, we will get back to green, but as we are not blocking on critical bugs that will mean we will release with the regression. Am I right?
[14:57] <davmor2> dum dum dum dum dum didledum and a shark
[14:58] <Mirv> I'm trying to EOD but the builds linger still a small bit
[14:58] <didrocks> elopio: I'm not sure to understand the case. If you improve the test, the test will fail if the behavior doesn't work anymore, and so, we'll pick regressions, right?
[14:58] <elopio> didrocks: no, this is the case: https://bugs.launchpad.net/notes-app/+bug/1288876
[14:59] <didrocks> elopio: ok, so this is a bug which is a regression
[14:59] <didrocks> and it's making some AP tests failing, right?
[14:59] <elopio> we find that not because it's part of a user story. We are getting the error just because somebody thought it was a nice idea to start all the tests clicking the header and checking that everything is collapsed.
[15:00] <elopio> if I were to improve the tests, I would just remove that step and turn it into a qml runner test that will not be displayed on the dashboard but block on MPs
[15:00] <didrocks> ok, but the fact that notes are not collapsed anymore is not wanted?
[15:01] <elopio> didrocks: well, as a user, I don't care if the notes are collapsed or not when I click the header.
[15:01] <elopio> as a user, I want to add notes and read notes, and that doesn't affect the user story at all.
[15:02] <didrocks> elopio: sure, but I'm not talking about that
[15:02] <elopio> what the bug probably means is that the header is not clickable when it has only one item.
[15:02] <didrocks> like what's the expected behavior?
[15:02] <didrocks> is it the one with Qt 5.2
[15:02] <didrocks> or 5.0
[15:02] <elopio> and that's a problem of the header, to be tested on the toolkit, not on the notes.
[15:02] <didrocks> right
[15:02] <didrocks> but again, you are mixing 2 valid things :)
[15:03] <elopio> with makes one bigger valid things? :)
[15:03] <didrocks> - ok, the test shouldn't test that, and should really really not due that in all test :)
[15:03] <elopio> s/things/thing
[15:03] <didrocks> - but here, we are talking about 5.2 transition ONLY and we expect to have the same behavior than 5.0
[15:03] <didrocks> am I right?
[15:03] <elopio> yes, you are.
[15:04] <didrocks> so I guess you have nothing to change in the test itself in that case (for now) and the bug/behavior change itself should be fixed
[15:04] <didrocks> for 5.2 transition
[15:04] <didrocks> then, yeah, decoupling the concerns will be a nice thing to do :)
[15:04] <elopio> ok, I can wait after 5.2 is released to improve the test.
[15:04] <didrocks> yeah, I would really suggest that :)
[15:05] <didrocks> treat the tests just as a non regression checker behavior-way
[15:05] <didrocks> even if it's testing too much things
[15:05] <didrocks> or not at the right place
[15:05] <elopio> now, zsombi seems to be really busy with the other blockers.
[15:05] <elopio> didrocks: who would you suggest to take care of this bug?
[15:05] <didrocks> then, this work of refinement will be needed anyway
[15:05] <didrocks> elopio: is it a sdk one?
[15:06] <didrocks> seems so, either notes-app or sdk
[15:06] <elopio> didrocks: maybe. I don't know how to know. It could be the sdk, or it could be the notes app using the sdk in a way it's not supposed to.
[15:06] <didrocks> yeah
[15:06] <didrocks> elopio: I think the sdk guys will be the best to analyze this one
[15:06] <didrocks> as they already started
[15:06] <didrocks> drilling down to a small case
[15:07] <didrocks> so bzoltan's team ^
[15:07] <elopio> didrocks: do you have permissions to make the bug critical? I don't.
[15:07] <didrocks> ogra_: if you broke my mtp, I'll hunt you down to death! ;)
[15:07] <didrocks> elopio: oh sure
[15:07] <ogra_> lol
[15:08] <bzoltan> didrocks: yes sir
[15:08] <ogra_> didrocks, what do you do with mtp ?
[15:08] <didrocks> elopio: maybe affect as well sdk?
[15:08] <didrocks> ogra_: I don't do anything, I just want to promote an image ;)
[15:08] <ogra_> :)
[15:08] <elopio> didrocks: maybe. I suppose I can add it, and they will remove it if it's not the case.
[15:08] <didrocks> ogra_: ok, let's say "if you broke my adb…" :p
[15:08] <ogra_> yeah :)
[15:08] <ogra_> adb didnt change
[15:08] <didrocks> elopio: please, and then, I'm bumping the priority
[15:08] <didrocks> ogra_: yeah yeah… I heared that already :)
[15:09] <bzoltan> didrocks: what can I do for you?
[15:09] <elopio> bzoltan: so, this bug it's really not a big one affecting the user in a big way, but it could be an important regression.
[15:09] <elopio> https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1288876
[15:09] <elopio> so it's blocking the 5.2 release. We need a dev to take a look at it.
[15:09] <bzoltan> elopio: why not to ask the app's dev?
[15:10] <elopio> bzoltan: I don't know. I'm following didrocks' suggestion. Who's the notes dev?
[15:10] <bzoltan> elopio:  there could be like a million different reason for that.
[15:11] <pmcgowan> elopio, talk to bfiller, ugo works on notes, but remember also it is being replaced by reminders
[15:11] <didrocks> elopio: done
[15:11] <bzoltan> elopio: nerochiaro
[15:11] <didrocks> yeah, between the 2 teams, you should get to something :)
[15:11] <elopio> bfiller: any input about that?
[15:12] <bfiller> elopio: lets disable it
[15:12] <bfiller> it's going away
[15:13] <bfiller> not worth spending any time on
[15:13] <didrocks> elopio: you don't have the same behavior on any other apps, right?
[15:14] <elopio> bfiller: so, yes, but the failing test is not the important part here. The important part is to check if qt5.2 is introducing a regression here that might affect something else.
[15:14] <Mirv> sil2100: didrocks: final final update, Qt 5.2 landing is now complete. except for the Kaleo's qtubuntu + unity-mir + ubuntu-ui-toolkit branches from bug #1207270 since he's still working on the swipe input regression although otherwise they now work as of today.
[15:14] <elopio> didrocks: there is no other application that I no of that has only one tab.
[15:14] <didrocks> Mirv: so, they will ping us?
[15:14] <didrocks> elopio: even in the click store?
[15:14] <elopio> this for sure doesn't affect tab switching.
[15:15] <sil2100> Mirv: excellent, should we poke the SDK team about that one leftover issue?
[15:15] <elopio> that's what the tab is for.
[15:15] <elopio> didrocks: sorry, no other application /that I know/
[15:15] <didrocks> popey: do you know about any app in the store having that particular case? ^
[15:15] <Mirv> didrocks: I asked Kaleo to keep the bug + branches up-to-date, I believe pmcgowan & co may check the EOD situation, ie. shall we land the branches to the PPA
[15:15] <elopio> there's system settings, but it has no behavior when you click the tab.
[15:16] <sil2100> Mirv: so no reconfigure will be needed, only rebuilds if anything, yes?
[15:16] <popey> didrocks: what use case?
[15:16] <Mirv> sil2100: Kaleo is the one, yes
[15:16] <Mirv> sil2100: reconfigure needed, since those three branches are not in the config at all since before today it was pretty broken
[15:16] <sil2100> Ah, ok
[15:17] <didrocks> popey: something like that: https://bugs.launchpad.net/notes-app/+bug/1288876
[15:17] <sil2100> Mirv: so we'll be keeping an eye on Florian then, just hope they will also ping us directly when the fixes are ready
[15:17] <didrocks> popey: so clicking on the tab "dismiss" or "ack" an edit
[15:17] <Mirv> sil2100: ppa:canonical-qt5-edgers/qt5-beta-proper, if used in addition to landing-006, gives Florian's branches readily compiled as they are currently
[15:17] <Mirv> sil2100: yep, I hope so too
[15:17] <popey> didrocks: hmm, not seen that, sorry.
[15:18] <didrocks> popey: no "good" :)
[15:18] <popey> hah
[15:18] <didrocks> pmcgowan: I think we are fine if we don't know of anyone using that "feature" to break that behavior between 5.0 and 5.2?
[15:18] <didrocks> pmcgowan: well, apart from clock apps, which is rewritten
[15:18] <didrocks> notes*
[15:19] <pmcgowan> didrocks, reading, so notes tab behavior somewhat busted with 5.2?
[15:20] <pmcgowan> ah one tab
[15:20] <pmcgowan> yeah I think we can whitelist this
[15:20] <didrocks> pmcgowan: yeah, basically it seems that if you edit a note and tap on the tab to dismiss/ack the change with one tab, it doesn't end up the current transaction
[15:20] <didrocks> pmcgowan: and popey-who-install-always-all-click-apps-from-store doesn't know of any application using that behavior
[15:21] <didrocks> so I guess we can call that behavior change a non issue, just checking with you :)
[15:21] <pmcgowan> didrocks, yeah, not likely to fix that, will deprecate note apps first, but I see the point about checking it vs sdk
[15:21] <didrocks> yeah
[15:21] <didrocks> ok, so elopio, seems the way to go for now is just to remove that part of the test
[15:21] <didrocks> making sense?
[15:21] <didrocks> thanks pmcgowan for the confirmation :)
[15:22] <pmcgowan> np
[15:22] <elopio> didrocks: yeah, it does.
[15:22] <didrocks> elopio: let me remove the sdk from the bug then
[15:22] <elopio> I mean, the whole problem shouldn't be exposed here anyway.
[15:22] <didrocks> yeah
[15:23] <elopio> actually, there's something I can try to see if there's actually a bug in the sdk.
[15:23]  * elopio goes to code.
[15:23] <didrocks> elopio: bug updated and assigned to you then :)
[15:23] <didrocks> sure :)
[15:25] <elopio> jaja, that's what I get for talking to much, one more bug to my bag ;)
[15:26] <sil2100> ;)
[15:35] <thostr_> sil2100: what about silo1? doesn't seem to be published yet?
[15:35] <thostr_> sil2100: also, can you get me a silo for line 44
[15:36] <sil2100> thostr_: almost done with silo 1, looking at line 44
[15:39] <balloons> ping josepht
[15:39] <josepht> balloons: pong
[15:40] <balloons> josepht, can you check and see if a package is installed or missing on the core apps jenkins merge bots; it's passing tests which should be failing and we believe it's because it's missing an eds package
[15:40] <sil2100> thostr_: silo assigned, publishing 1 now
[15:40] <thostr_> sil2100: thanks
[15:41] <balloons> josepht, the package is qtorganizer5-eds
[15:48] <davmor2> didrocks: hows 226 coming along?
[15:48] <didrocks> davmor2: building nicely, did you finish and prepared the report on crashers?
[15:49] <didrocks> like is it good enough, not yet, horrible? :p
[15:50] <davmor2> didrocks: I'm yet to have one, still only got the upstart-app-launch_desktop-hook in /var/crash
[15:50] <didrocks> davmor2: oh, so no crash even hammering the click apps?
[15:51] <davmor2> didrocks: that's right
[15:51] <didrocks> great ;)
[15:51] <davmor2> ah speaking of which weather just died on me
[15:52] <davmor2> didrocks: first qmlscene crash let me confirm it is d8f8
[15:53] <didrocks> davmor2: yeah, then remove the crash file
[15:53] <didrocks> to get more :)
[15:56] <davmor2> didrocks: so I think this is the same issue popey saw earlier #0 0xb5e7b150 in ?? ()
[15:56] <davmor2> didrocks: ah no different again
[15:56] <didrocks> davmor2: ah?
[15:57] <davmor2> didrocks: on a plus side it was definitely the weather app that triggered it
[15:57] <didrocks> ok ;)
[15:57] <didrocks> keep us posted on social and other heavy-js apps
[15:59] <davmor2> didrocks: http://paste.ubuntu.com/7050648/
[16:01] <didrocks> davmor2: ok, we saw some corrupted stacks which were the same
[16:01] <didrocks> so identical frames, let's put under the same "V8 issue"
[16:07] <bfiller> fginther, sergiusens : is there a place where I can download the deb (amd64) for this build? http://jenkins.qa.ubuntu.com/job/thumbnailer-trusty-amd64-ci/20
[16:07]  * bfiller trying to avoid buiilding it
[16:07] <dbarth> didrocks: hey didier, the webbrowser / oa reverts, is that automatic? cause this branch still has the commit from that silo
[16:07] <dbarth> https://code.launchpad.net/~phablet-team/webbrowser-app/trunk
[16:07] <dbarth> rev 454 has not been reverted
[16:07] <didrocks> oh
[16:07] <didrocks> [16:07] <didrocks> davmor2: ^
[16:07] <davmor2> \o/
[16:07] <didrocks> dbarth: it will have it, once qt 5.2 lands
[16:08] <fginther> bfiller, it's not saved, but the jobs can be quickly changed to do so
[16:08] <didrocks> davmor2: jump on it!
[16:08]  * davmor2 jumps on it and 226 breaks into a million tiny shards
[16:09] <didrocks> :p
[16:09] <davmor2> didrocks: installing
[16:09] <davmor2> rebootin'
[16:09] <bfiller> fginther: don't worry about it
[16:12] <josepht> balloons: do you have a link to an example job?
[16:12] <davmor2> didrocks: I'm going to do a bootstrap to give it every chance being as it is so important :)
[16:12] <didrocks> davmor2: yeah, it completely deserves a bootstrap :)
[16:12] <didrocks> davmor2: continue on the click apps look I guess
[16:14] <davmor2> didrocks: so facebook, googlemaps, g+, osmtouch and twitter were all fine, as I say only crash was weather and that took nearly 3 hours of constant hammering opening reopening interacting with alll the different apps to get that to happen :)
[16:14] <sergiusens> bfiller, no artifacts are stored for that
[16:14] <didrocks> davmor2: ok, sounds solid!
[16:14] <pmcgowan> go davmor2 go davmor2
[16:14] <davmor2> didrocks: now everyone cross your fingers that 226 is the same
[16:15]  * didrocks wants to see fingers crossed here as well
[16:15] <didrocks> (but continue working :p)
[16:15] <balloons> josepht, the clock-app jobs specifically
[16:16] <balloons> josepht, http://<IP_ADDRESS>:8080/job/generic-mediumtests-trusty/
[16:16] <balloons> josepht, as part of http://<IP_ADDRESS>:8080/job/ubuntu-clock-app-ci/
[16:20] <josepht> fginther: is mediumtests-slave offline for a reason?  I need to get into it.
[16:21] <josepht> balloons: from dpkg-l.post.log it looks like it's not installed
[16:21] <balloons> josepht, ok, could we get it installed? I can open a bug to do so
[16:22] <fginther> josepht, yes, it's an old saucy image, it shouldn't be used by anything
[16:22] <fginther> josepht, reading the backlog
[16:23] <josepht> balloons: yes please open a bug
[16:23] <josepht> fginther: sorry I was looking at the wrong node
[16:23] <fginther> josepht, no worries
[16:24] <fginther> balloons, so the clock app tests need a dependency?
[16:24] <davmor2> didrocks: well the guide works \o/
[16:24] <didrocks> davmor2: SHIP IT!
[16:25] <sil2100> ;p
[16:25] <fginther> josepht, I'll have to check on this, there aren't any ssh keys setup for anyone else
[16:25] <davmor2> popey: managed to hit play on a blank piece of music,  music-app took it's time to open but played in the end
[16:25] <josepht> fginther: ack, thanks
[16:26] <cjwatson> didrocks: could you run "copy-package -p ci-train-ppa-service --ppa-name landing-006 -b qtdeclarative-opensource-src"?  Should let qttools-opensource-src build
[16:27] <didrocks> cjwatson: sure, done. (thanks for looking, too many things at the same time)
[16:27] <didrocks> cjwatson: I can give you access to the ppas if you need, but you will get a lot of more spam :)
[16:27] <cjwatson> no thanks :-)
[16:27] <fginther> balloons, do you know if that's going to wreck other tests? that's the problem we had earlier... And if so, is there a reason the clock-app tests can't specify this as a dependency?
[16:28] <fginther> balloons, and I can confirm it's not currently installed
[16:28] <cjwatson> didrocks: I'll try to check through for other things.  I can use my buildd-admin privileges to retry stuff
[16:28] <didrocks> cjwatson: ok, as you wish :)
[16:28] <cjwatson> didrocks: qtpim-opensource-src too
[16:29] <didrocks> done
[16:31] <cjwatson> didrocks: qtwebkit-examples-opensource-src qtwebkit-opensource-src qtx11extras-opensource-src qtxmlpatterns-opensource-src
[16:31] <cjwatson> sorry, will hopefully be done soon, just trying to chase that jenkins failure ...
[16:32] <didrocks> cjwatson: no worry, rather thanks you for looking into that :)
[16:33] <balloons> fginther, yea, I'll have to dig into the clock dependencies.. if it's specified it should be getting installed eh
[16:44] <balloons> fginther, so I suppose I would argue since it's in the images, it should be in the test environment. That said, it'll be added for clock as a dependency
[16:49] <fginther> balloons, I guess that is a weird thing, but I think it's the right answer as long as we're using apt. I assume this goes away when we start installing and testing these as click packages (although I admit to not knowing how the mechanics of that works)
[16:49] <balloons> fginther, yea, that would be even closer to the real thing :)
[17:01] <ogra_> grrr google
[17:01] <didrocks> ogra_: davmor2: sil2100: joining?
[17:01] <sil2100> Ah!
[17:01] <didrocks> ogra_: it's because the mpt change! :)
[17:02] <didrocks> mtp*
[17:02] <ogra_> so let me upload a revert then if google will start working
[17:02] <didrocks> even
[17:02] <didrocks> ahah
[17:02] <ogra_> :P
[17:02] <ogra_> damn
[17:02] <didrocks> plars-away: really away? :p
[17:02] <didrocks> ev: anyone else from your team to join the "kick the image" side?
[17:03] <sergiusens> didrocks, I'm considering myself off the hook with http://ci.ubuntu.com/smokeng/trusty/touch/flo/226:20140307.2:20140304/7039/gallery_app/
[17:04] <ev> didrocks: hm? I'm a bit heads down on Mt Hood. Do you need people to help with something?
[17:05] <didrocks> ev: just ensure that someone is looking/rerunning image #226 for CI test results
[17:05] <didrocks> if needed
[17:05] <davmor2> popey: have a look as the camera app icon on the home page and the apps page do they look the same?
[17:05] <tvoss> sil2100, ping
[17:06] <popey> davmor2: no
[17:07] <ev> psivaa: ^ can you have a look?
[17:07] <sil2100> tvoss: pong, did you see that dbus-cpp and others successfully built on the PPA?
[17:07] <sil2100> tvoss: on the first run!
[17:07] <psivaa> ev: ack, will do
[17:08] <ev> psivaa: thanks!
[17:08] <tvoss> sil2100, yup, pete-woods and Wellark are helping with the testing
[17:08] <tvoss> sil2100, so do you need any further information on the merge proposal or are we good?
[17:09] <tvoss> that is, mps for location service
[17:09] <psivaa> ev: yw
[17:11] <sil2100> tvoss: I think we're cool - could you just double-check if the list of merges in the landing is correct and has all the necessary ones?
[17:15] <balloons> davmor2, can you send along the pastebin again? did you file a bug? and what version of weather?
[17:17] <davmor2> balloons: http://paste.ubuntu.com/7050648/
[17:21] <tvoss> sil2100, ack
[17:21] <balloons> davmor2, what version did you run? ohh I suppose it was old as r226 contains new weather
[17:22] <balloons> davmor2, I just assume you hit the bug which was fixed
[17:22] <davmor2> balloons: the updated version on 225
[17:22] <balloons> davmor2, how did you install it ?
[17:22] <davmor2> balloons: however I got the same error on 226 which it the new one
[17:23] <davmor2> balloons: from click
[17:23] <balloons> davmor2, blah, fine
[17:23] <balloons> davmor2, bug?
[17:23] <davmor2> balloons: not yet busy busy testing everything
[17:25] <tvoss> sil2100, list of mps look good
[17:25] <tvoss> pete-woods, Wellark are you guys done with the testing?
[17:26] <pete-woods> tvoss: I'm happy it works
[17:26] <tvoss> pete-woods, ack
[17:26] <tvoss> Wellark, ?
[17:26] <pete-woods> tvoss: I think antti is running the Unity AP tests right now
[17:26] <davmor2> popey: did you file a bug for the camera getting the line traveling across it
[17:26] <tvoss> pete-woods, ack
[17:26] <pete-woods> he's AFK, though
[17:28] <tvoss> sil2100, you happy with pete's feedback?
[17:28] <robru> mhr3_, there's a dependency problem with your silo 2 landing
[17:28] <robru> mhr3_, http://<IP_ADDRESS>/job/landing-002-2-publish/lastSuccessfulBuild/artifact/packaging_changes_mediascanner2_0.100+14.04.20140307-0ubuntu1.diff
[17:29] <robru> mhr3_, the new package depends on "mediascanner (= ${binary:Version})" but that's wrong, should probably be "mediascanner2.0 (= ${binary:Version})"
[17:29] <davmor2> popey: it looks like if you zoom in any and then click to focus on something then take a shot it starts to do the scrolling line
[17:29] <mhr3_> robru, indeed
[17:30] <robru> mhr3_, can you add a commit and rebuild? then I can publish it
[17:30] <mhr3_> robru, can't, not my branch
[17:31] <mhr3_> robru, can only create new mp
[17:31] <robru> mhr3_, bah. ok, please do, then I can reconfigure for you
[17:31] <tvoss> sil2100, ?
[17:33] <cjwatson> urgh, qtdeclarative/ppc64el is going to need the usual patch we applied to a bunch of places
[17:34] <mhr3_> robru, so just this http://paste.ubuntu.com/7051141/ right?
[17:34] <robru> mhr3_, close, it needs to be '2.0' to match the binary package name
[17:35] <mhr3_> robru, ah, right, good that i checked
[17:35] <robru> ;-)
[17:35] <robru> brb
[17:38] <mhr3_> robru, added mp, pls reconf and feel free to build too, i will eow in a bit
[17:38] <robru> mhr3_, ok no worries.
[17:39] <didrocks> robru: reusing the new reconf one? :)
[17:39] <robru> didrocks, yes, it's working! ;-)
[17:39] <didrocks> \o/
[17:39] <didrocks> phew ;)
[17:39] <robru> didrocks, thanks for that, it's pretty slick.
[17:39] <didrocks> robru: great! glad that you like it. Will be officially announced next week and opened to everyone :)
[17:40] <robru> didrocks, ahhh I was wondering when. excellent!
[17:40] <didrocks> robru: just be aware that if you add a new component that isn't in the list, it will yell and force you to use prepare-silo
[17:40] <didrocks> as it's the goal of it :)
[17:40] <robru> didrocks, perfect
[17:40]  * mhr3_ waves
[17:40] <didrocks> see you mhr3_!
[17:40] <robru> mhr3_, bye
[17:41] <mhr3_> enjoy weekend didrocks, robru!
[17:41] <tvoss> didrocks, sil2100 do we see some u8 crashes on the current image?
[17:42] <didrocks> tvoss: we do
[17:42] <didrocks> u8 + random apps
[17:42] <tvoss> didrocks, hmmm ... wellark is reporting 5 crashes when running the u8 ap test suite
[17:43] <didrocks> yeah
[17:43] <didrocks> we can have less or more
[17:43] <tvoss> didrocks, is that in the baseline image, too?
[17:43] <mhr3_> robru, crap, forgot to set prereq branch for the mp, although i guess it should work without that as well
[17:43] <didrocks> well, you can check as well :)
[17:43] <didrocks> and see all my emails on the phone ML
[17:43] <didrocks> but yeah, 5 can happen
[17:43] <didrocks> you can check them
[17:43] <tvoss> didrocks, ack
[17:43] <didrocks> the address is finishing by d8f8
[17:43] <didrocks> (from frame 0)
[17:43] <didrocks> tvoss: so easy to check ^
[17:44] <tvoss> didrocks, that's the v8 issue, correct?
[17:44] <Wellark> tvoss, pete-woods: ping
[17:44] <didrocks> tvoss: yep
[17:44] <tvoss> Wellark, see backlog
[17:44] <tvoss> didrocks, I'm seeing 2 crashes locally
[17:44] <robru> mhr3_, should be fine since they're in the right order. it's already building
[17:44] <Wellark> tvoss: ack
[17:45] <Wellark> so unity8 ap tests are flaky
[17:45] <tvoss> Wellark, could you check for the address in the crashes?
[17:45] <Wellark> how do I retrace them manually+
[17:45] <Wellark> ?
[17:45] <tvoss> Wellark, hmmm, might even be enough to look at the crash file. didrocks^?
[17:45] <didrocks> yeah
[17:45] <didrocks> just unpack the crash file
[17:45] <didrocks> gdb the coredump
[17:46] <didrocks> and look at frame0
[17:46] <didrocks> no need for symbols
[17:46] <didrocks> as we just need the address
[17:46] <tvoss> didrocks, thanks
[17:46] <didrocks> yw :)
[17:48] <Wellark> didrocks: how do I "unpack" the .crash file?
[17:48] <didrocks> Wellark: apport-unpack <crash_file> /tmp/foo
[17:48] <didrocks> and then, you will have the CoreDump in /tmp/foo
[17:49] <Wellark> didrocks: ack
[17:50] <balloons> davmor2, I can't recreate your crash in weather. when you have a chance, more info please
[17:52] <didrocks> hum
[17:52] <didrocks> doanac`: psivaa: anything change in the way you install deps? http://ci.ubuntu.com/smokeng/trusty/touch/manta/226:20140307.2:20140304/7038/messaging_app/
[17:53] <didrocks> it's like if ofono-phonesimd isn't installed
[17:53] <didrocks> asac: FYI ^
[17:53] <didrocks> (don't have the console log for now)
[17:53] <ogra_> yeha
[17:53] <ogra_> i noticed that too
[17:53] <didrocks> doanac`: psivaa: at worse, once the tests are finished, can you ssh, install the dep (ofono-phonesimd) if not there and try?
[17:54] <psivaa> didrocks: this is on manta though.. i'll try once the tests complete
[17:54] <didrocks> psivaa: yeah, let's wait on mako, it's running as we speak it seems :)
[17:54] <ogra_> manta also has no working BT yet
[17:54] <ogra_> so the Bt indicator test will always fail
[17:55] <didrocks> psivaa: ogra_: you're right, they were as well failing on manta
[17:55] <didrocks> weird that it has this side-effect (it's failing on the setup)
[17:55] <didrocks> ok, ignore for now, let's really focus on mako
[17:55] <didrocks> current results look promising :)
[17:56] <ogra_> well, the craches get populated at the end :)
[17:56] <sil2100> Now this is interesting, after meddling with my device I now have a landscape keyboard when in portrait and the other-way around ;)
[17:56] <sil2100> Useful feature
[17:57] <ogra_> thats dual user mode
[17:57] <dobey> how long is this qt5.2 "no change rebuild" going to take?
[17:57] <sil2100> ogra_: :D
[17:57] <ogra_> bringing people together and such :)
[17:59] <didrocks> dobey: it's not a non change rebuild exactly, people are working on latest bugs, early next week we hope
[18:00] <dobey> didrocks: we have branches piling up for the click scope, and the silo we had for a few of them got wiped away because of the rebuild thing
[18:01] <didrocks> dobey: well, your lander was contacted first
[18:01] <didrocks> dobey: but if you can help getting the 5.2 Qt things out, your help is welcome :)
[18:02] <dobey> what qt 5.2 things?
[18:02] <tvoss> Wellark, any insight?
[18:02] <didrocks> dobey: bugs/regressions
[18:02] <Wellark> tvoss: still running the ap tests
[18:03] <tvoss> Wellark, ack
[18:03] <Wellark> tvoss: tvoss seems I got one crash at least
[18:03] <Wellark> ok, checking now
[18:03] <dobey> didrocks: so i should just ignore the "no change rebuild" MPs from Mirv and ask to get the other branches landed?
[18:04] <tvoss> Wellark, okay
[18:04] <didrocks> dobey: no, they have a lock on the component, don't throw their testing away
[18:04] <didrocks> dobey: check with your landers, he knows how that work
[18:04] <dobey> even on things that are not on the "ci train"?
[18:05] <psivaa> didrocks: messaging on mako came back all passing
[18:05] <didrocks> dobey: you can land anything that are not locked by the Qt 5.2 (through the ci train)
[18:05] <didrocks> psivaa: thanks \o/
[18:06] <psivaa> :)
[18:08] <Wellark> didrocks, tvoss: the adress of frame 0 is 0x3cb0d8f8
[18:08] <didrocks> Wellark: so yeah, the V8 crash
[18:08] <sil2100> didrocks: forgot asking this during the meeting - did you get any news from Kaleo regarding that last-standing 5.2 bug?
[18:08] <Wellark> ok. ignoring them then
[18:08] <sil2100> The one Mirv mentioned
[18:08] <tvoss> Wellark, perfect, thank you
[18:08] <didrocks> sil2100: just that he's working on it
[18:09] <didrocks> no more news
[18:09] <tvoss> sil2100, ^, so pete-woods, Wellark and me tested silo 3
[18:09] <tvoss> sil2100, as far as we can tell, things work as good as before
[18:09] <sil2100> tvoss: no suprises, no CPU eatage and location-service working normally?
[18:09] <tvoss> sil2100, yup. Wellark, pete-woods could you guys please check top, too?
[18:10] <sil2100> Wellark, pete-woods, tvoss: just to make sure the 100% CPU is really not an issue ever again ;)
[18:11] <tvoss> sil2100, yup, but that was caused by gcc intermixes back then :)
[18:11] <tvoss> anyway, better safe than sorry
[18:11] <sil2100> didrocks: you think we could also publish this one today? Me or Robert could also double check if it's not causing any regressions, but as long as it's not eating up 100% CPU or something similar, it shouldn't even interfere in existing integration tests
[18:11] <didrocks> sil2100: yeah, can you double check to ensure before landing? then, it will be fine for me IMHO
[18:12] <didrocks> anyway, WE are going to promote #226 isn't it?
[18:12] <didrocks> isn't it? :)
[18:12] <sil2100> didrocks: the components to be released are dbus-cpp, location-service and platform-api (p-api has only a build-dep bump, so a rebuild with latest dbus-cpp)
[18:12] <sil2100> Ah, right ;)
[18:13] <tvoss> sil2100, would appreciate you giving the silo a spin, too
[18:13] <Wellark> tvoss, sil2100, pete-woods: np. we will run the tests again and this time look at top aelo
[18:13] <Wellark> seriously speaking. didn't notice any 100% cpu usage so we should be all fine
[18:14] <sil2100> tvoss: sure thing, upgrading in a moment and spinning
[18:14] <didrocks> sil2100: tvoss: Wellark: we are as well usually trying to get lock up from the browser from a location webpage, might be worth looking at it
[18:14] <didrocks> (and it's not winter anymore, so not cold to have the window opened for 10 minutes!) :)
[18:15] <sil2100> tvoss: in the meantime, as you're the official lander, could you set the landing 003 to 'Tested: Yes' on the spreadsheet? ;)
[18:18] <Wellark> didrocks: is there a bug filed in LP?
[18:18] <davmor2> balloons: I opened it, added a city, change the F to C
[18:19] <balloons> I've done all that and more.. you can reproduce consistently?
[18:19] <balloons> and of course the tests do the same
[18:19] <davmor2> balloons: then I changed the backend once that was working and crash, then I opened it back up changed back to the other backend and crash again
[18:19] <tvoss> didrocks, pete-woods tried to get a fix in the browser and managed to do so after the usual 10 minutes :)
[18:19] <didrocks> tvoss: ah, excellent and top wasn't crazy after that? :)
[18:19] <davmor2> balloons: pass but have you checked the /var/crash dir?
[18:20] <davmor2> balloons: for the second crash everything worked but the crash still appeared
[18:20] <tvoss> didrocks, not for me, but it might be a 100%
[18:20] <balloons> davmor2, I can.. but I don't visually see any issues
[18:20] <tvoss> didrocks, that's well known :)
[18:21] <tvoss> sil2100, didrocks setting it to tested
[18:21] <didrocks> great ;)
[18:21] <Wellark> sil2100: missing a submitter checklist on this one, please add it
[18:21] <balloons> davmor2, ahh.. it's the re-opening that might be what you mean
[18:21] <Wellark> sil2100: https://code.launchpad.net/~phablet-team/location-service/bump_deps/+merge/208169
[18:21] <davmor2> balloons: while I am testing I run adb shell and then watch -d ls /var/crash
[18:21] <Wellark> tvoss: mising a submitter checklist on this one, please add it
[18:21] <Wellark> tvoss: https://code.launchpad.net/~thomas-voss/location-service/switch-to-transact-method/+merge/209451
[18:22] <davmor2> balloons: that highlights everytime a file ends up in there
[18:22] <balloons> davmor2, I think I finally reproduced
[18:22] <Wellark> tvoss, sil2100: https://wiki.ubuntu.com/Process/Merges/Checklists/location-service
[18:22] <davmor2> balloons: \o/
[18:22] <balloons> davmor2, thanks for the explainations
[18:22] <davmor2> balloons: no worries
[18:22] <davmor2> balloons: it is a lot more stable than it was :)
[18:23] <sil2100> Wellark: will add, thanks ;)
[18:24] <Wellark> sil2100: we are ready to land the MR, so only thing blocking is the checklist
[18:24] <Wellark> and me and pete are way over EOD :)
[18:25] <sil2100> Wellark: that MR will only land when we click the publish button anyways ;)
[18:25] <tvoss> sil2100, do you add the checklist?
[18:25] <Wellark> tvoss: to his own MR, you still need to do yours :)
[18:25] <Wellark> it's a small one
[18:26] <Wellark> just copy and paste
[18:27] <didrocks> davmor2: balloons: don't break the images guys, and keep us posted!
[18:27]  * didrocks really EOW now :)
[18:28] <davmor2> didrocks: nooooooooooo
[18:28] <didrocks> davmor2: what's up? last minute crisis? :p
[18:28] <sil2100> tvoss: added
[18:29] <davmor2> didrocks: No I just don't think you should go :P
[18:29] <sil2100> tvoss: ok, by some dogfooding I see it working pretty ok
[18:29] <davmor2> didrocks: Keep your eyes out for the  email, It will be long
[18:29] <sil2100> Didn't get a GPS signal yet though
[18:29] <sil2100> Ok, need to drive to pick up my girlfriend, be back later to do the final publish
[18:29] <davmor2> sil2100: takes about 15 minutes
[18:29] <didrocks> davmor2: sure ;) (my wife disagrees with you and thnk I should go and help painting the kitcken :p)
[18:29] <sil2100> tvoss, Wellark, pete-woods: give me a final +1 if all is ok and I'll publish once I'm back ;)
[18:30] <davmor2> didrocks: go man go, life won't be worth living else  ;)
[18:30] <didrocks> heh, see you guys!
[18:31] <ogra_> enjoy
[18:31] <cjwatson> Could somebody with ci-train-ppa-service access please run "copy-package -p ci-train-ppa-service --ppa-name landing-006 -b qtsystems-opensource-src" to create the ppc64el build?
[18:31] <cjwatson> (from lp:ubuntu-archive-tools)
[18:31] <tvoss> sil2100, Wellark pete-woods adjusted https://code.launchpad.net/~thomas-voss/location-service/switch-to-transact-method/+merge/209451
[18:36] <balloons> davmor2, I lied.. the crash was mediascanner
[18:36] <balloons> weather is fine :-)
[18:36] <davmor2> balloons: haha
[18:37] <tvoss> Wellark, anything to add?
[18:37] <Wellark> tvoss: nope, looks good.
[18:37] <tvoss> Wellark, ack
[18:37] <tvoss> pete-woods, ?
[18:37] <Wellark> tvoss: now, only waiting pete-woods to approve the last two
[18:38] <pete-woods> tvoss: done
[18:38] <Wellark> then sil2100 or robru need to switch testing to green on the landing sheet
[18:38] <robru> Wellark, what's tested?
[18:38] <pete-woods> silo 3
[18:38] <Wellark> robru: silo 003
[18:39] <Wellark> we would like to see that landed please :)
[18:39] <Wellark> tvoss: ^
[18:40] <robru> Wellark, ok, I can publish it soon, I just have to poke at it a bit
[18:40] <asac> robru: please continue double cehcking etc.
[18:40] <asac> until we have shot qt5.2
[18:40] <robru> asac, yes
[18:41] <asac> we want to preserve ability to do a firedrill fix on monday after we promoted the image monday morning
[18:41] <asac> thanks
[18:41] <asac> robru: can you help cjwatson ?
[18:41] <asac> or was he already helped?
[18:42] <robru> asac, oh i dunno. what did he need?
[18:42] <cjwatson> 18:31 <cjwatson> Could somebody with ci-train-ppa-service access please run "copy-package -p ci-train-ppa-service --ppa-name landing-006 -b qtsystems-opensource-src" to create the ppc64el build?
[18:42] <asac> cjwatson: i think we should give you access to such things
[18:42] <cjwatson> 18:31 <cjwatson> (from lp:ubuntu-archive-tools)
[18:42] <cjwatson> asac: I didn't want the mailspam :)
[18:42] <cjwatson> asac: it's a transient problem, new uploads won't be affected, it's just for things that happened before we switched on ppc64el, so just trying to clean things up a bit
[18:42] <tvoss> sil2100, so pete-woods, Wellark and me are +1
[18:42] <asac> cjwatson: what team is it?
[18:42] <cjwatson> ci-train-ppa-service
[18:43] <cjwatson> I'd actually rather not be able to affect that directly
[18:43] <asac> cjwatson: yeah, but in general i feel saver if we have our strong core-devs able to do something in case there isa  big problem
[18:43] <asac> hmm
[18:43] <asac> cjwatson: your call
[18:43] <robru> i don't think I have that access.
[18:43] <cjwatson> it's not urgent, anyway, I just noticed its build-deps aren't satisfiable in any case, so drop it
[18:43] <asac> cjwatson: let me see. maybe i can give you access and remove after
[18:43] <asac> cjwatson: yes, i own that team
[18:43] <asac> let me know
[18:43] <asac> https://launchpad.net/~ci-train-ppa-service
[18:43] <cjwatson> it'll need https://code.launchpad.net/~cjwatson/kubuntu-packaging/qtdeclarative-porting/+merge/209981 first, don't worry about it
[18:43] <asac> ok
[18:44] <asac> cjwatson: seems quite a few already are in that team
[18:44] <asac> think all CI-trained core devs are addded there
[18:44] <cjwatson> yeah, I haven't had training
[18:44] <cjwatson> probably should at some point but it's not the most urgent thing
[18:45] <cjwatson> stgraber ought to be there if that's the condition, though?
[18:45] <Wellark> robru: anything you need from us anymore? or can it be landed now without any additional input from me, pete-woods or tvoss ?
[18:45] <cjwatson> but probably best ask him :)
[18:46] <robru> Wellark, ideally tvoss should be around in 2-3 hours to merge & clean after the publish, but if he wants to EOW, I can take care of it.
[18:46] <robru> Wellark, but only tvoss, everybody else can go if they're done
[18:46] <Wellark> robru: so if tvoss needs to EOW, you can still take care of everything? OK. good.
[18:46] <robru> Wellark, yep
[18:46] <pete-woods> :D
[18:46] <Wellark> great! :)
[18:47] <Wellark> thanks.
[18:47] <robru> Wellark, pete-woods have a good weekend!
[18:47] <Wellark> robru: you, too
[18:47] <pete-woods> robru: you too!
[18:47] <asac> ogra_: since you might get tricked into believing that we promtoe the image when jfunk gives a +1
[18:47] <asac> ogra_: please dont do that until monday morning
[18:48] <asac> try to get up early though
[18:48] <asac> we dont want to end up having people work weekend in unlikely case there is something that we need to react on
[18:48] <tvoss> robru, I really have to eow
[18:48] <asac> tvoss: man, go off
[18:48] <tvoss> robru, would appreciate your help
[18:48] <ogra_> asac, i wouldnt do any promotion without either your or didrocks approval anyway
[18:48] <asac> thanks
[18:49] <tvoss> asac, thanks :)
[18:49] <asac> yeah. just saying because jfunk will send an official mail
[18:49]  * tvoss waves goodbye
[18:49] <ogra_> right
[18:49] <Wellark> tvoss: good luck and good weekend!
[18:49]  * asac hugs tvoss
[18:49] <robru> tvoss, i'm on it, have a good weekend!
[18:49]  * Wellark gives tvoss a man-hug
[19:00] <rsalveti> tvoss: and good luck as well :-)
[19:08] <balloons> sergiusens, https://code.launchpad.net/~sergiusens/phablet-tools/emu_prov/+merge/207440 works fine. I asked for the option to not do the setup if I wish
[19:12] <sergiusens> balloons, #2 is an option I use myself :-)
[19:13] <balloons> sergiusens, well then, it must exist!
[19:15] <sergiusens> balloons, all these options make me think it's time to move aways from a script though :-)
[19:16] <balloons> well, yes I know it makes things feel more and more cobbled together
[19:18] <sergiusens> still making the change
[19:19] <davmor2> balloons: https://bugs.launchpad.net/ubuntu-weather-app/+bug/1289536
[19:19] <balloons> davmor2, you know I still don't believe you :-)
[19:21] <balloons> davmor2, I did find this, but.. https://bugs.launchpad.net/ubuntu-weather-app/+bug/1287982
[19:21] <balloons> no one believed me :-)
[19:21] <balloons> rsalveti, can you ack this? https://code.launchpad.net/~nskaggs/phablet-tools/add-cmake-dependency/+merge/204269
[19:24] <rsalveti> robru: can I get a silo for line 45?
[19:24] <rsalveti> let me check
[19:26] <rsalveti> sergiusens: why recommends in this case ^?
[19:26] <rsalveti> from the description it needs cmake to function properly
[19:26] <rsalveti> shouldn't it be depends then?
[19:27] <om26er> fginther, hey is the new unlocker not being used in production anymore ?
[19:33] <sergiusens> rsalveti, probably right; I'm splitting that package into tiny bits today as well
[19:34] <fginther> om26er, it's in use, what's not working?
[19:35] <om26er> fginther, just wanted to make sure, i seem to have noted something in didier's email, so was under the impression the script was reverted
[19:35] <balloons> sergiusens, rsalveti so put it back into depends then? It's a trivial thing, but tools fail for new users if we don't install things we need :-)
[19:37] <rsalveti> sergiusens: how to proceed then?
[19:37] <robru> rsalveti, sure
[19:37] <sergiusens> rsalveti, balloons, yeah, or do like the devscripts where mk-build-deps asks for equivs to be installed
[19:37] <sergiusens> but doesn't make the whole package depend on it
[19:38] <robru> rsalveti, ok, you got silo 1. please build
[19:38] <rsalveti> robru: thanks
[19:38] <robru> rsalveti, you're welcome
[19:44] <balloons> sergiusens, not sure how to setup mk-build-deps to ask for equivs
[19:47]  * robru --> lunch
[19:51] <sergiusens> balloons, no worries, assign the problem to me and I'll get it proposed
[19:56] <balloons> sergiusens, done. https://bugs.launchpad.net/ubuntu/+source/phablet-tools/+bug/1289558
[20:03] <rsalveti> davmor2: http://goo.gl/l5i9SV is not public
[20:03] <davmor2> pmcgowan, ogra_, asac, didrocks(sciving off painting kitchens), popey please may I draw your attention to the phone mailing list there is a nicer breakdown of the email I sent and a big thumbs up from qa enjoy :)
[20:03] <rsalveti> ogra_: should we then promote 226? :-)
[20:03] <davmor2> rsalveti: sorry jfunk set it up
[20:05] <pmcgowan> rsalveti, I believe the plan is first thing monday to avoid weekend danger
[20:05] <rsalveti> pmcgowan: yeah :-)
[20:05] <rsalveti> not a good thing to do on a friday evening
[20:05] <pmcgowan> davmor2, was that terminal font thing a known issue?
[20:06] <davmor2> pmcgowan: yeap it's happened on and off for a while, it's my EOD and EOW so Monday first things I'll add the bugs and file any new ones
[20:06] <pmcgowan> davmor2, ok asac and I were just wondering
[20:06] <davmor2> pmcgowan: all you have to do to fix it is set a font size
[20:07] <pmcgowan> davmor2, slacker not working the weekend?
[20:08] <asac> davmor2: oh sorry. sent another mai. ill check that new mail
[20:08] <davmor2> pmcgowan: I know right, some people have wives that insist on them not going near computers all wekend cause they'll wind up working :)
[20:09] <davmor2> pmcgowan: and She is lovely, but scares me more than you guys ;)
[20:09] <pmcgowan> davmor2, understood
[20:10] <davmor2> asac: it has minor niggles and the weather app is flakey but mostly only the weather app so we are happy big thumbs up
[20:10] <davmor2> rsalveti: the doc should be public now too
[20:11] <davmor2> asac: and popey is happy too so :)
[20:11] <rsalveti> davmor2: thanks
[20:13] <davmor2> asac: is that good enough for you?
[20:16] <davmor2> right guys I'm off enjoy your weekends
[20:17] <asac> davmor2: i dont see that mail :/
[20:18] <asac> davmor2: is that hidden within a thread?
[20:19] <asac> pmcgowan: do you see the mail by davmor2 to phone ML?
[20:19] <pmcgowan> asac, no I see it
[20:19] <pmcgowan> image r226 Testing Results
[20:19] <asac> pmcgowan: on the public ubuntu-phone list?
[20:20]  * asac goes to archive
[20:20] <asac> it is in archive, not in my inbox
[20:20] <asac> guess google is again trying to slow us down :P
[20:21] <pmcgowan> asac, stop using tbird ;)
[20:21] <asac> davmor2: what is missing is what got fixed that was bad in last image
[20:21] <asac> davmor2: like "click apps didnt get updates"
[20:21] <asac> and making a tablet to put them against each other.
[20:21] <asac> anyway, i wont bother
[20:21] <asac> goes into micro managing :P
[20:21]  * asac still feels jfunk should have sent a big message
[20:22] <asac> click scope being busted
[20:22] <asac> is scary
[20:22] <asac> and we need to know if it existed in previous build
[20:22] <asac> otherwise we dont know
[20:22] <asac> really
[20:22] <pmcgowan> asac, its not busted its just wonky, has been for quite a while
[20:22] <asac> so yeah the comparison wasnt done
[20:22] <pmcgowan> not sure about 194
[20:22] <asac> right, but i wanted a comparison as we make calls based on last image vs. this
[20:22] <asac> the fact that they say we dont know is scary
[20:22] <asac> i asked for that explicitely for days
[20:23] <pmcgowan> well I dont know, dav probably does
[20:23] <asac> well, he marked it as "New breakage, needs to be checked if it existed in previous build"
[20:23] <asac> pmcgowan: see https://docs.google.com/document/d/1UB-bk31kLZMlsDFT81LWoFg1tZt_lLeKcRVLIExrAi8/edit
[20:23] <asac> the RED with white font
[20:23] <asac> so thats a regression
[20:24] <pmcgowan> he said needs investigation
[20:26] <pmcgowan> asac, I had asked about that very issue, and I think it was ralsina_ that said its expected the way the scope works, but at some point needs to be improved for sure
[20:26] <asac> pmcgowan: well, that i dont really care about. i want to know was it in previou build or not. if it was not in previous build i want a mail from jfunk
[20:26] <pmcgowan> or maybe it was saviq
[20:26] <asac> putting the new regressions in comparison to the old bugs
[20:26] <asac> and making a good argument
[20:26] <asac> we can also decide that here
[20:27] <ralsina_> pmcgowan: what issue?
[20:27] <asac> and probably will, but i feel that QA should be able to make tha tcall
[20:27] <asac> if its not a clear black and white decision anymore
[20:27] <pmcgowan> sure nt disagreeing
[20:27] <asac> but having a good assessment and describing symptoms, arguing why and so on :)
[20:27] <asac> we should learn how to do that
[20:27] <asac> yeah. i will continue to ask him fo rthat
[20:27] <asac> personally would really like to understande what this really is :)
[20:28] <asac> ralsina_: click scope is buggy in latest image
[20:28] <asac> ralsina_: see davmors mail to touch mailing list...
[20:28] <asac> ralsina_: err here: https://docs.google.com/document/d/1UB-bk31kLZMlsDFT81LWoFg1tZt_lLeKcRVLIExrAi8/edit
[20:28] <asac> ralsina_: Glitch after each app install it removes the section from the scope, flashes and then returns the updated list.
[20:28] <asac> in section Click packages
[20:28] <ralsina_> asac: right
[20:29] <pmcgowan> asac, it needs to refresh the entire sections to remove the app from available and put it in installed
[20:29] <ralsina_> asac: all the scope does is invalidate the results because one result has moved from one section to the other
[20:29] <pmcgowan> there is no api for moving it
[20:29] <ralsina_> exactly
[20:29] <pmcgowan> sorry didnt see you there
[20:29] <pmcgowan> ralsina_, so did this change recently?
[20:29] <ralsina_> maybe the refreshing in the dash can be made smarter or happen before the preview is closed, or something
[20:29] <pmcgowan> ralsina_, seems more intrusive in the latest
[20:29] <asac> "it has to refresh"? ... what does the user experience exatly?
[20:30] <ralsina_> pmcgowan: no, we had the call to invalidate there, and then the dash started actually invalidating. No change in the scope there like for a month
[20:30] <asac> i dont want to know what the fix is, but what the experience is right now :)
[20:30] <pmcgowan> it clears the page and repaints it
[20:30] <ralsina_> asac: otherwise the installed app will be listed in the store section, not the installed section
[20:30] <pmcgowan> ralsina_, I think part of the issue is the user sees the scope, then it blanks and refeshes
[20:31] <asac> so just some flickering?
[20:31] <pmcgowan> ralsina_, would be good if it was already blanked and simply restores for example
[20:31] <pmcgowan> asac, yes
[20:31] <asac> but no user impact?
[20:31] <ralsina_> pmcgowan: right, so things could be made smoother by changing order of things, to avoid flickering
[20:31] <asac> sure?
[20:31] <pmcgowan> yes
[20:31] <pmcgowan> I do it all the time
[20:31] <pmcgowan> I logged that bug ;)
[20:31] <asac> waht ralsina says above sound more like the app continues to stay in the wrong section (e.g. store, not installed)
[20:31] <pmcgowan> no it moves
[20:31] <pmcgowan> just flashy
[20:31] <asac> pmcgowan: you do what? if its just flickering then you dont need to do anything :)
[20:32] <ralsina_> asac: it would stay in the wrong section if we did not invalidate the results (whcih then causes the flashing)
[20:32] <pmcgowan> when you install an app
[20:32] <asac> ralsina_: ok but we ALWAYS invalidte after install?
[20:32] <ralsina_> asac: yes, we have to
[20:32] <pmcgowan> coming back from the app install view, it shows the scope, then clears then paints it with the app in the right place
[20:32] <asac> pmcgowan: how long is that flickering action in seconds?
[20:32] <asac> 0.1? 1, 10? :)
[20:33] <ralsina_> < 1
[20:33] <pmcgowan> yeah <1
[20:33] <ralsina_> depends on network tho
[20:33] <ralsina_> we could refresh the old results and make it take no time, but since the scope has to be stateless we can't.
[20:35] <pmcgowan> just did one and around .1 secs, very quick
[20:35] <asac> doesnt sound critical
[20:35] <asac> we should track it though
[20:35] <pmcgowan> ralsina_, that transition could be improved
[20:35] <pmcgowan> agreed
[20:35] <pmcgowan> its not nice
[20:35] <ralsina_> pmcgowan: +1 yes
[20:36] <asac> we can make the rick test... will he complain :)?
[20:36] <ralsina_> pmcgowan: the dash could be smarter, get the new results and then do something pretty
[20:36] <pmcgowan> ralsina_, has it always been this way?
[20:36] <pmcgowan> is it worse now for some reason?
[20:36] <ralsina_> pmcgowan: since the dash started doing invalidation it has always been the same
[20:37] <pmcgowan> ah so before you would not see the new app without searching
[20:37] <asac> the other way to decide if it would block is to check if we would have catched this as part of our normal image validation procedure.
[20:37] <pmcgowan> asac, now I remember
[20:37] <pmcgowan> asac, so it changed, but to fix the bug that the new apps were not shown
[20:37] <pmcgowan> at some point
[20:38] <asac> if neither rick-will-start-buggin-devs and that test are negative its good for promotion :P
[20:38] <asac> pmcgowan: can we at least upgrade click apps now?
[20:38] <asac> :)
[20:38] <pmcgowan> we can witht he upgrade app still
[20:38] <pmcgowan> not yet in settings
[20:39] <asac> so even that wasnt fixed yet? wow
[20:39] <pmcgowan> probably backed up on CI
[20:39] <asac> so no improvement over 194
[20:39] <pmcgowan> its fine, run the app upgrader
[20:40] <sergiusens> pmcgowan, it was worse before; installing a new app kept the old ref and the app was unlaunchable until a search was triggered
[20:40] <pmcgowan> sergiusens, exactly
[20:40] <ralsina_> yep
[20:41] <asac> pmcgowan: the doc says in "settings" section: updates work
[20:41] <asac> just auto download option is ignored
[20:41] <asac> pmcgowan: are you disagreeing with that?
[20:41] <ralsina_> asac: maybe that means system image updates
[20:41] <asac> this was the biggest issue we had identified in 194
[20:41] <ralsina_> the click scope is weird, it's the only scope where using the search result changes the search results :-P
[20:41] <asac> it was tracked by CI, then was claimed fixed
[20:41] <asac> etc.
[20:42] <pmcgowan> asac, I do not think app updating is in system settings
[20:43] <asac> 21:38 < asac> pmcgowan: can we at least upgrade click apps now?
[20:43] <asac> 21:38 < asac> :)
[20:43] <asac> 21:38 < pmcgowan> we can witht he upgrade app still
[20:43] <asac> 21:38 < pmcgowan> not yet in settings
[20:43] <asac> so "not yet in settings" is a fewature?
[20:43] <asac> guess then it just means that the upgrade app didnt work in 194
[20:43] <pmcgowan> yes, its staus quo
[20:43] <asac> so all good
[20:43] <asac> dont have any other explanation
[20:43] <pmcgowan> there is a branch waiting to make it so
[20:44] <ralsina_> updating apps is not in settings, that was reverted, use the updater until  https://code.launchpad.net/~diegosarmentero/ubuntu-system-settings/click-updates/+merge/208567 merges
[20:44] <asac> yeah. if it was never in, then thats surely not what i mean
[20:46] <asac> #213:
[20:46] <asac> Full list of changes in Friday's email. However, just want to mention (if you didn't read other exchanges on this mailing list), that this version introduced a download manager issue on click apps.
[20:46] <asac> maybe thats the one?
[20:46] <asac> #216:
[20:46] <asac> * this one contains the bug fix for the download-manager with click app issue. Dogfooding confirmed it's now fixed.
[20:47] <asac> but that wasnt in the promoted image
[20:48] <asac> anyway
[20:48]  * asac notes it down to post-mortem what was going on here :)
[20:49] <asac> ogra_: do you know what was broken with click apps not updating?
[20:49] <asac> what exactly that was :P
[20:50] <ralsina_> asac: that was that the fix for the system-image issue with download manager (atomic downloads) broke click apps downloads because noone followed the full test plan because of assumptions and lack of devices
[20:50] <Laney> click app updates was never in settings
[20:50] <asac> ralsina_: right. but that wasnt in 192
[20:50] <asac> so its not the thing
[20:51] <asac> what ways to update click apps do we expect to have?
[20:51] <asac> 1. upgrade app
[20:51] <asac> 2. scope?
[20:51] <asac> 3. automatic?
[20:51] <ralsina_> "expect" as in "now" or "expect" as in "someday"?
[20:51] <asac> ralsina_: 192
[20:51] <ralsina_> in 192, just the upgrade app
[20:52] <asac> ralsina_: 170?
[20:52] <ralsina_> there was one image where the upgrade app was bogusly removed, don't recall the number
[20:52] <asac> ralsina_: ok i think thats 192
[20:52] <asac> unless we had some other way to upgrade apps
[20:52] <ralsina_> ok, so that was it
[20:52] <ralsina_> nope, no other way
[20:52] <asac> wqe never had another way to upgrade apps?
[20:52] <pmcgowan> no
[20:52] <asac> good
[20:53] <asac> that thing is back now. so thats fixed :)
[20:53]  * asac doesnt know if its right, but at least can get some rest with this believe now
[20:53] <asac> hehe
[20:54] <ralsina_> asac: good enough to go to bed on a friday indeed
[20:54] <asac> yep
[20:55] <ralsina_> asac: just as a heads up, starting monday I am phasing off as a manager into a dev position in lucio's team, so click scope will be in thostr's capable hands
[20:55] <asac> pmcgowan: ralsina_: sorry for annoying on this one. we have a way to improve our problem tracking planned, then i could just look it up
[20:55] <ralsina_> asac: of course I'll be around to help as much as needed
[20:55] <asac> i am happy now. we achieved a lot this week
[20:55] <asac> and are good for a qt shot :)
[20:55] <asac> ralsina_: thanks!
[20:56] <pmcgowan> we certainly did
[20:56] <asac> yep. qt cracking
[20:56] <asac> image fixing
[20:56] <sil2100> ;)
[20:56]  * asac phases out from active discussions for the day
[20:56] <asac> cu around monday
[20:57] <sil2100> See you on Monday!
[20:57] <asac> err wednesday... :)
[20:57] <asac> i am most likely off
[20:57] <asac> but we will see
[21:04] <dobey> hmm, i presume all the "no change rebuild" merges are blocked on qt5.2 landing, or something? is there a silo for that, or what?
[21:10] <robru> dobey, yep, silo 6
[21:10] <robru> dobey, we're looking at landing those monday
[21:12] <dobey> robru: and what about the rebuilds for things that aren't on ci train yet?
[21:12] <davmor2> asac you still about?
[21:13] <robru> dobey, what isn't in ci train yet? everything should be in there by now. if not, I dunno, you'd have to ask Mirv how he'll handle those
[21:13] <dobey> robru: ubuntu-purchase-service isn't
[21:14] <robru> dobey, I guess Mirv will have to migrate it to citrain on monday then. not sure
[21:16] <davmor2> asac: it was the camera and weather click apps that were updated I needed to make sure that both of those were included in the new build but had updated them through the click store on 225
[21:17] <davmor2> at least I think it was the the camera app anyway :)
[21:18] <dobey> oh, meh, ok
[21:20] <davmor2> asac: the title is [Ubuntu-phone] Image r226 Testing Results I kept it separate so it stood out from the list.
[21:46] <asac> davmor2: yes, was received, just came through late. have a great weekend
[21:47] <asac> davmor2: sure that 226 just had those two changes?
[21:47] <asac> http://people.canonical.com/~ogra/touch-image-stats/20140307.2.changes
[21:47] <asac> davmor2: did we do smoke tests on 226?
[21:47] <asac> popey: ?
[21:48] <asac> davmor2: popey: there have been other changes, so if we havent even booted etc. we run kind of risky :)
[21:53] <asac> dont worry
[21:54] <asac> jfunk confirmed that you guys tested 226
[21:54] <asac> thanks and enjoyu!
[21:55] <davmor2> asac: no we tested on 226.  All I was saying was I upgraded from 225 to 226 but had already updated the click apps on 225 so did a fresh install to make sure that 226's image had actually pulled them in.
[21:55] <davmor2> asac: as they were kinda key to making weather app more stable
[21:55] <davmor2> asac: not perfect but more stable :)
[21:55] <davmor2> asac:  if there is anything else I'll stick around for a bit
[21:56] <asac> davmor2: nice. so extra care. thanks
[21:59] <kgunn> plars-away: i think i'm supposed to chat with you ? [Bug 1236525] Re: unity8 killed/crash then restart can result in mir unable "could not unblank display"
[22:02] <kgunn> one quick question for whomever....wrt "Special landing mode process while we are recovering	on ubuntu Touch"
[22:02] <kgunn> if Qt5.2 has a project associated with it during this time before "final qt5.2 landing"
[22:03] <kgunn> does that lock out others ?? (e.g. i'd love to reattempt mir - we fixed our 1 regression we found, but qt has unity-mir as a rebuild)
[22:05] <robru> I gotta head out, anybody need anything before I EOW slightly early?
[22:06] <robru> kgunn, yeah, projects can only exist in one silo at a time. qt5.2 is locking an enormous number of things right now
[22:18] <plars-away> kgunn: is this related to the update we got to the unlocker that didn't work?
[22:19] <kgunn> plars-away: not completely sure...i got a mail from alexander but didn't quite know what it meant...ended with "talk to plars" :)
[22:20] <plars-away> kgunn: If it's what I think it is, om26er is probably the better one to talk to. He's the one that patch came from. But is there a specific question? I'm not really familiar with that bug
[22:20] <kgunn> ok, i'm ending soonish...but i'm sure anyone will be glad to help euro mornin monday
[23:04] <asac> kgunn: plars-away: i just dropped a comment that wahtever patch landed that was referring to the bug was backed out
[23:04] <asac> as it broke all tests
[23:05] <asac> that was an infrastructure patch i referred to... guess it was omer etc.
[23:05] <asac> i dont know mnow ,mor :)
[23:05] <asac> have a great weekend