imgbot=== trainguards: IMAGE 27 building (started: 20141120 02:05) ===02:03
=== chihchun is now known as chihchun_afk
imgbot=== trainguards: IMAGE 27 DONE (finished: 20141120 03:30) ===03:28
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/27.changes ===03:28
=== chihchun_afk is now known as chihchun
Mirvbarry: hi! you've had vivid silo 004 in use for three weeks, is it abandoned and can it be freed?06:44
Mirvlool: same ^ for your vivid silo 020, assigned 3 weeks ago, no actions for 2 weeks06:46
MirvI'm just checking the statuses as we are out of silos06:46
Mirvbregma: could you consider testing the indicator-session trusty silo 023, or abandoning it?06:47
Mirvbzoltan: you've had qtcreator-plugin-ubuntu in vivid silo 021 for two weeks, but it looks it should be abandoned?06:52
bzoltanMirv:  let me check...06:53
bzoltanMirv:  yes, that MR got merged together with the latest landing. Sorry.06:54
Mirvbzoltan: ok, freeing up06:54
MirvAlbertA: I think you will need to rebase mir and rebuild - it seems bdmurray has pushed a no change rebuild to archives so the changelog in your branch is out-of-date and CI Train would complain: https://lists.canonical.com/archives/vivid-changes/2014-November/001800.html06:59
dbarthgood morning08:01
dbarthjustinmcp_: hi, i'm here08:01
sil2100yay, sanity tests for 166 were really good \o/08:08
ogra_sil2100, yeah, but we have one toopblocker left08:16
ogra_(see ricardos mail)08:16
ogra_and the browser cache bug is also not so nice08:17
sil2100ogra_: yeah... I actually asked oSoMoN a few days ago if the oxide fix is enough08:41
oSoMoNsil2100, ogra_: talking about rsalveti’s comments on the bug? I’m looking into it08:43
ogra_oSoMoN, which one now ? :)08:48
ogra_bug 1391230 or bug 139438008:49
ubot5bug 1391230 in pulseaudio (Ubuntu RTM) "[TOPBLOCKER] web audio, pulse runs at 6% and screen will not blank on idle" [Critical,Confirmed] https://launchpad.net/bugs/139123008:49
ubot5bug 1394380 in lxc-android-config (Ubuntu RTM) "QML cache not regenerated correctly on image update" [Critical,Confirmed] https://launchpad.net/bugs/139438008:49
oSoMoNI was talking about the first one08:52
sil2100ogra_: how much does it take to re-generate the QML cache btw.?08:54
ogra_sil2100, one start of the spp08:54
ogra_the cache is per app ... created on first start if it doesnt exist08:55
oSoMoNre- the QML cache, I don’t understand how that could possibly affect the oxide upgrade, oxide is pure C++, there’s no QML to compile and cache…08:55
sil2100Right, but it's not a time-consuming operation anyway I suppose08:55
ogra_it speeds up the startup once it is in place, so the drawback of wiping it means the apps start a bit slower the first time after an updated08:55
ogra_oSoMoN, the webbrowser is QML ... and a small piece of the container too08:56
ogra_(and i'm not sure it is just QML in that cache ... ricmm ??)08:57
oSoMoNogra_, sure, but the issue reported by Bill about UA strings doesn’t make sense to me08:57
ogra_well, i have seen it myself08:57
sil2100ogra_: then I would personally give a +1 on your workaround until a proper solution is prepared, but anyway poke Pat and olli first08:57
ogra_sadly i bluntly deleted all dirs that had any trace of browser or webapps in them on my phone08:57
ogra_bill seems to have seen that and done it dir by dir08:58
olliogra_, sil2100, what's up08:58
ogra_sil2100, i dont think  it is a reason to re-spin ... so we can discuss it in the bug meeting08:59
olliread backscroll, don't think I have all context08:59
ubot5Launchpad bug 1394380 in lxc-android-config (Ubuntu RTM) "QML cache not regenerated correctly on image update" [Critical,Confirmed]08:59
sil2100ogra_: that's for sure, I think this milestone should stay closed, but maybe next weeks08:59
sil2100olli: so there's this bug that we noticed ^08:59
ogra_olli, after OTA some webapps and the browser behave weird (like serving the desktop variant of pages etc) ... until you wipe the QML cache for them09:00
sil2100olli: ogra_ prepared a quick-fix that simply clears out the QML cache on every update09:00
ogra_right, i think we should have a solution for the final image ...09:00
sil2100olli: we don't think it's needed for this milestone, but we might consider adding this (or something better) for the next milestone09:00
ogra_but rsalveti disagrees in the bug, i'd like his input first09:01
ogra_right, there might be something better (though i would prefer the safe solution and just wipe everything to prevent future surprises)09:01
olli_ogra_, sil2100, let's try again, I am on ethernet now09:02
* olli_ throws unfriendly words at the BF wifi09:02
sil2100Let me copy-paste09:03
olli_you can pm that too09:03
ogra_bah, to the wrong olli09:03
sil2100hah ;)09:03
ogra_better now :)09:04
olli_so.. that bug seems to be triggered in updates only09:06
olli_is there a way the upstart change can be applied via OTA09:07
olli_in a pre-hook or so09:07
ogra_you mean before an OTA ?09:07
ogra_it has to come in with a system upgrade09:07
olli_will that be sufficient though09:07
olli_or does it have to be in GM09:08
ogra_oh, well09:08
ogra_if we i.e. upgrade oxide or webapps after the GM it needs to be in place to prevent it09:08
ogra_(and we dont know how/if it affects other apps, webapps are the only ones exposing something really visible)09:09
olli_ogra_, can't the update wipe the cache (once) while being installed?09:11
ogra_well, the thing runs on every first boot after upgrade ... so yes, it runs when it is shipped09:12
ogra_why would you want to do that only once ?09:12
ogra_that defeats the whole purpose09:12
ogra_you want this on every system-image upgrade09:13
ogra_(which this upstart job will do)09:13
ogra_"start on boot-hooks WHEN=new-version"09:13
ogra_(new version points to the system-image, it will only run after an OTA happened)09:14
ogra_psivaa, we seem to be missin results for one device in the krillin rtm smoketests09:21
psivaaogra_: yes, one device failed to provision with wifi, i've kicked the missed tests off09:21
sil2100jibel: in the meantime, are you continuuing the regression tests on #166?09:28
jibelsil2100, we do09:28
sil2100jibel: excellent :)09:28
sil2100Give us a sign if any serious issues emerge09:28
sil2100popey: meeting!09:33
popeysorry, network connection went funny09:34
=== vrruiz_ is now known as rvr
cjwatsonrobru: I'm assuming somebody dealt with that ubuntu-keyboard core-dev ack, since that URL is 404 now09:45
Mirvcjwatson: yes, it was an universe package09:48
sil2100psivaa: if you could give us a poke when the test results are all in it would be awesome09:50
psivaasil2100: ack will do. they are roughly 1 hour and 30 mins away, but i'll ping to let you know09:51
ogra_sil2100, the QA regression tests will take the whole day anyway ... no need to hurry :)09:53
sil2100ogra_: ;)09:54
ogra_i just had my session restart10:26
psivaasil2100: ogra_ the testing with 166 is complete, but hasn't synced to the dashboard yet10:39
sergiusens_can I get a silo for line 54?10:43
sergiusens_ah, it moved :-P10:44
psivaaogra_: sil2100: one new failures that i can see is this in dialer: http://rtm-dashboard.ci.ubuntu.com/smokeng/utopic/touch_stable/krillin/166:20141119:20141119-db417fa/184/dialer_app/10:54
ogra_thanks !10:55
ogra_i guess we should let bfiller know10:56
ogra_i looks like the app went away (dbus cnt find it anymore) but i see no .crash or anything10:56
ogra_(unlike the constant camera-app crash we have on krillin)10:56
sil2100psivaa: thanks!11:01
psivaanp, there is no kernel logs for a minute from 20:31:04, roughly when this happened. not sure if there is any relevance11:11
ogra_is there anything like zzzZZZZZZ in it perhaps11:12
Mirvjoke of the day:"I'll have a quick oxide-qt build"11:49
sil2100Mirv: :D11:50
olliogra_, sil2100, what's the plan now11:59
olliI am trying to round up the team here for a quick call11:59
ogra_we wait til QA finished the regression tests and publish11:59
ogra_future plans need to be discussed then imho11:59
ollipublish with the topblocker still open11:59
sil2100olli: we need to assess how much the leftover oxide issue is still top-priority12:00
ogra_it is being actively worked on12:00
sil2100olli: if it's not12:00
ogra_so we can expect it to be fixed by next week i think12:00
ogra_it is also not a regression over our last promoted image12:00
sil2100olli: ...premature enter, but yeah: we can tackle it for next week's milestone I suppose12:00
john-mcaleelysil2100, ogra_ jibel ^ vivid krillin device tarball12:00
sil2100olli: as rebuilding oxide can take ages12:01
john-mcaleelydoes that need QA signoff?12:01
ogra_john-mcaleely, just go ahead12:01
ollisil2100, so you are saying it's not feasible to fix it in this weeks build12:01
sil2100john-mcaleely: hey! Not really ;) But if you want you can ask QA to help out12:01
olliand then spot test12:01
ogra_olli, we dont have a fix yet12:01
john-mcaleelysil2100, It's got a test pass from me. I'm happy to push it12:01
john-mcaleelyyou're short handed at the moment12:01
ogra_olli, if we had we might be able to consider it ... but even then ... it isnt a regression, we had it in many former images and we are confident to get a fix before final12:02
john-mcaleelyogra_, to be clear - it's ok to push now (build machine wise)12:02
sil2100olli: yeah... since if we have a fix and it requires an oxide rebuild (which is probable from what oSoMoN mentioned), then it would really push things behind12:02
sil2100john-mcaleely: then you have a green light :)12:02
ogra_john-mcaleely, sure12:02
john-mcaleelyogra_, sil2100 jibel done. new vivid tarball in the next build12:03
ogra_might be :)12:03
* ogra_ didnt look at vivid for a while12:03
oSoMoNsil2100, olli: it requires an oxide rebuild indeed, chrisccoulson is taking care of it as we speak. I’d like to mitigate to impact of the issue though: as pointed out by rsalveti in the bug, the issue is there only the first time after boot, subsequent uses of the browser won’t exhibit it12:04
olliogra_, sil2100, are you guys available for a quick HO right now12:04
ogra_gimme 5 min12:04
ollioSoMoN, ^12:04
oSoMoNolli, so maybe it doesn’t deserve to be an urgent topblocker anymore?12:05
oSoMoN(I’m available for a quick HO if you need me)12:06
sil2100john-mcaleely: thanks :)12:06
sil2100oSoMoN: fact12:06
pmcgowanoSoMoN, in my view it will still make an impact 100% of the time so we really need the fix but we can discuss12:07
oSoMoNpmcgowan, indeed, it will always be an issue the first time the browser is launched after rebooting, I’m not denying that this needs to be fixed quickly (in fact the fix is ready), just saying that maybe we don’t want to delay the image validation and promotion any longer12:08
sil2100pmcgowan: I just think we shouldn't delay this week's milestone but maybe include it in the one next week12:08
ogra_pmcgowan, no doubt that we need it12:09
ogra_pmcgowan, but there is no way it can make this milestone12:09
pmcgowanwell lets discuss, the curent image will not make gm12:09
ogra_obviously not, but we''ll promote it12:09
olliogra_, there is no point12:10
ogra_this isnt a regression12:10
ogra_last milestone had this prob, and many before12:10
ogra_so for the good of oour users we'll definitely promote it to get testin for the rest of the image12:10
olliogra_, this is applying the LT criteria12:10
olliI think we wanted to include the product team criteria as well for a promotion12:11
ogra_only talking about this atm12:11
olliogra_, , sil2100, oSoMoN pmcgowan, victorp https://plus.google.com/hangouts/_/canonical.com/olli12:11
ogra_*we* will promote it, *you* definitely should wait til there is a fix on the horizon12:11
ogra_olli, reading that bu again from top to bottom i actually think having media-hub/pulse never go to sleep (which this bug causes) is as bad as keeping the display on, so we should try to get some fix from rsalveti as well if that is possible in time12:26
ogra_else your phone will never sleep if there is a webapp backgrounded12:26
ogra_olli, pmcgowan as per the discussion i turned bug 1394380 into a topblocker12:30
ubot5bug 1394380 in lxc-android-config (Ubuntu RTM) "[TOPBLOCKER] QML cache not regenerated correctly on image update" [Critical,Confirmed] https://launchpad.net/bugs/139438012:30
ollithx ogra_12:30
sil2100olli, ogra_: I'll put it on the list for the next milestone then12:33
olliwhat is the next milestone?12:33
sil2100wave2, next week12:33
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
oSoMoNolli, pmcgowan, sil2100: oxide 1.3.5 building at https://launchpad.net/~phablet-team/+archive/ubuntu/ppa/+sourcepub/4579784/+listing-archive-extra13:03
ogra_sil2100, ^^13:11
sil2100ogra_: no free silos for vivid right now...13:13
ogra_sil2100, thats fine ... vivid can land later13:15
ogra_(they are diverted enough that i needed to create two different uploads anyway)13:16
ogra_argh, i think i clicked "build" to fast ... the PPA didnt produce binaries yet13:23
* ogra_ tries that again ... but now with binaries in place :P13:38
rsalvetiogra_: olli: right, it'll never to go deep sleep because, because pulse will stay up13:51
rsalvetiI'm checking that now, should hopefully have a fix for next week iteration13:51
sil2100rsalveti: o/13:54
rsalvetiogra_: and regarding the qml cache thing, let's land your change if that indeed only runs after every flash/update14:14
ogra_rsalveti, right14:14
ogra_safety net :)14:14
ogra_(it is already in silo2)14:14
tedgtrainguards, can you republish vivid/25, marcustomlinson fixed the top approval.14:37
sil2100tedg: ACK14:37
bfillersil2100: I need to sync a package from rtm to vivid, please see line 56, not sure I got the format right14:37
sil2100bfiller: sure thing, let me take a look14:37
bfillersil2100: also, is there a script that can be run that compares rtm versions to vivid? I'm worried that some fixes may have only landed in rtm and not in ubuntu vivid (like qtorganizer5-eds)14:38
ogra_bfiller, given you only care about stuff on the touch image, you could worst case pull both manifest files from cdimage.ubuntu.com and diff them ...14:39
sil2100bfiller: ok, the format looks right, let me assign the silo - as for the second question, one time I prepared a list of approximate missing landings from both sides (rtm->vivid and vivid->rtm), but it's probably outdated now14:39
sil2100It's actually generated from a diff between the manifests14:40
sil2100I can regenerate that list later today and put somewhere14:40
bfillersil2100: that's great, thanks14:40
sil2100bfiller: so, I see you already have a silo with qtorganizer5-eds for vivid (silo 15)14:41
sil2100bfiller: it seems to be a normal merge-based silo - you want to have this sync assigned first though?14:41
bfillersil2100: yes, we can ignore that for now. having problems with that14:41
sil2100bfiller: silo 11 assigned, it should sync the package from rtm when 'build' is pressed14:42
sil2100tedg: I approved the packaging changes now and publishing14:43
tedgsil2100, Great, thanks!14:44
tedgmarcustomlinson, ^14:44
marcustomlinsonsil2100: thanks :)14:44
sil2100yw :)14:44
bfillersil2100: great14:45
cyphermoxsil2100: I'm taking care of vivid silo 003 myself14:47
sil2100cyphermox: ok, will try to keep my hands out of it :)14:47
cyphermoxugh, more snow :(14:48
* sil2100 wants snow14:49
sil2100I'm in a strange christmas-ish mood right now (which is strange, considering it's Nov still) - but I'm missing snow outside of my windows14:50
* ogra_ is happy he doesnt have to turn th heating on yet ... 14:52
ogra_or to shovel snow14:52
sil2100hah, yeah, the few downsides of having a house :)14:53
sil2100As an apartment user I don't have much more work when snow is around14:53
* cwayne1 is getting prepared for first snow as a homeowner14:53
sil2100Just when wanting to use the car14:54
sil2100Damn, 30 silos for ubuntu and all are occupied :o14:54
ogra_you need to stock up ... to 60 :)14:55
cyphermoxsil2100: it's not that I don't like snow, but it's cold in my office and I wasn't mentally prepared for the snow14:56
om26ercwayne1, which project should I use to report bugs for Grooveshark scope ?15:33
cwayne1om26er: ubuntu-rest-scopes15:34
=== chihchun is now known as chihchun_afk
fgintheralan_g, I have some more info on the mir test failures you mentioned yesterday. The builds that were failing were all running on a newer instance with a 3.13.0-39-generic kernel instead of a 3.13.0-36-generic kernel16:08
alan_gfginther: odd. Thanks for the update16:09
greybacktrainguards: can I get a silo for line 58 please? Is for a qtmir build system switch16:32
sil2100greyback: is that for vivid?16:32
greybacksil2100: yep16:32
sil2100greyback: since currently we're still lacking silos... all are full16:33
greybacksil2100: ah ok16:33
sil2100greyback: I'm waiting for some to empty up16:33
greybackno rush16:33
sil2100Oh, ok, I see one is ready now16:33
sil2100jibel: btw. do we have someone performing sanity testing for the 166 equivalent for mako?16:36
jibelsil2100, not yet.16:38
oSoMoNgotta leave for now, I’ll be back online later tonight to handle the silo request for oxide 1.3.516:39
sil2100I wonder if oSoMoN needs a silo for the oxide-qt landing already16:59
sil2100As it's not set to Ready: 'Yes'16:59
ogra_i guess it still builds16:59
ogra_oh, thanks16:59
sil2100greyback: I can't assign a silo for you now since I see silo 009 already has qtmir in it (new Mir release)16:59
sil2100ogra_: we had some free silos finally :)17:00
greybacksil2100: ack17:00
=== chihchun_afk is now known as chihchun
sil2100ogra_, olli: hey! I sent out an e-mail to you guys regarding the milestone update17:55
* sil2100 needs to drive to the store now17:59
sil2100See you tomorrow o/17:59
=== alan_g is now known as alan_g|EOD
=== chihchun is now known as chihchun_afk
AlbertA2trainguards: can someone review this: https://code.launchpad.net/~mir-team/ubuntu-seeds/use-new-Mir-metapackages/+merge/24240819:52
AlbertA2trainguards: and related question, can I include that branch in my mir release silo (009) so that upgrading does not result in19:53
AlbertA2unable to boot a phone19:53
robruAlbertA2: no, we definitely want upgrades to break phones ;-)19:53
AlbertA2robru: :) in that case I'm ready then heh19:54
robruAlbertA2: so that branch looks fine to me but you need a core dev for seed changes. I recommend ogra_, he does most of the seed changes I know of19:54
AlbertA2robru: thanks!19:57
robruAlbertA2: you're welcome19:57
ricmmmanual acking?20:12
robruricmm: it's ok20:13
ricmmrobru: ok20:13
oSoMoNtrainguards: hey, can I haz a silo for line 56, please21:40
robruoSoMoN: rtm 321:41
oSoMoNrobru, thanks, would you mind doing the binary copy of oxide-qt from https://launchpad.net/~phablet-team/+archive/ubuntu/ppa ?21:42
robruoSoMoN: sure one sec21:54
robruoSoMoN: which one? the newest one has a lower version. confused21:55
robruoh rtm ;-)21:55
oSoMoNrobru, sorry, I should have specified: 1.3.5-0ubuntu0.14.10.1~rtm21:56
oSoMoN(I hadn’t noticed that there was a 1.4.0 test build in there)21:56
robruoSoMoN: hm, not sure if this'll work, as it won't let me choose 14.09 as the series.21:56
robruoSoMoN: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-003/+packages yeah the copy failed.21:57
oSoMoNrobru, why not? it worked yesterday when copying 1.3.4 from the ubuntu-mozilla-security PPA21:57
robruoSoMoN: yeah that one you were copying from vivid to vivid. This is a copy from utopic to 14.09, the series don't match21:57
robruoSoMoN: there's probably some other way to sync it but I don't know what it is. the web form on the ppa won't work21:58
oSoMoNrobru, I wasn’t referring to the vivid one, actually the 1.3.4 that landed in RTM yesterday was also binary-copied from that PPA (the copy was not done yesterday though, it was two days ago)21:59
oSoMoNrobru, wasn’t there a script that you guys use to perform this kind of copy, instead of going through the web form?21:59
robruoSoMoN: who did that one for you?21:59
oSoMoNrobru, probably sil210022:00
robruoSoMoN: I just use the web form. the only script I ever had for this kind of thing was the one that did source copies and mangled the series.22:00
oSoMoNrobru, I guess that at this point a source copy won’t hurt anyway, as I’m not gonna test it before tomorrow morning22:01
robruoSoMoN: but will it fail to build due to running out of space? ;-)22:01
oSoMoNrobru, that PPA has 4GB of space, that should be enough22:01
robruoSoMoN: if you're not building until tomorrow morning anyway, just check with sil at the start of your shift. he should be able to do it again22:02
oSoMoNrobru, I’d rather have it build tonight so that it’s ready for testing tomorrow morning at the start of my shift22:02
robruoSoMoN: but binary copies are really fast, just minutes even.22:02
robruand will tax the build farm less22:03
oSoMoNrobru, right22:03
oSoMoNrobru, ok, I’ll check with sil2100 tomorrow morning then, thanks for the help22:03
robruoSoMoN: ok sorry I couldn't help, get sil to teach me the secret of cross-series binary copies ;-)22:03
oSoMoNwill do :)22:04

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!