/srv/irclogs.ubuntu.com/2014/10/17/#ubuntu-ci-eng.txt

kgunnrobru: you around ? could i get a silo for line 90 ?00:09
kgunnit's a quick fix for the edge demo/intro on unity8 which seems to have broke since image 10900:09
kgunnok i gotta go eat...bbiab hopefully to build00:10
olliyou guys keep rocking...00:16
robrukgunn: rtm 5. Best to ping trainguards, pinging individuals doesn't scale when I'm on vacation, or off sick00:17
cwaynerobru: howre you, what happened to your ribs?! (/me just read the topic)00:23
robrucwayne: apparently I'm 80 years old, because i literately just fell over and broke my ribs. It was ridiculous00:26
robrucwayne: I'm recovering best i can, thanks00:26
cwaynerobru: can't really judge here, im 26 and already have arthritis, so apparently i'm also 80 :)00:32
robrucwayne: yikes, sorry to hear that00:35
popeyanother report on the list that #94 is badly broken00:36
cwaynerobru: meh, could be worse :)  glad to hear you're recovering well00:40
popeyhttps://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/138227800:46
ubot5Ubuntu bug 1382278 in unity8 (Ubuntu) "Image #94 on mako/flo fails to start - mir crash" [Undecided,New]00:46
popeyif there's some "list" that needs to be on it00:46
popey#94 is busted00:46
popeyrobru: ^00:53
popeyactually, Mirv bug 1382278 will need looking at in the morning00:57
ubot5bug 1382278 in unity8 (Ubuntu) "Image #94 on mako / #88 on flo fails to start - mir crash" [Undecided,New] https://launchpad.net/bugs/138227800:57
elopiotrainguards: anybody around to build the silo 5?01:47
elopioI could test it, but I'm not sure what are the parameters required for the build.01:48
robruelopio: typically build job doesn't require any parameters in the default case01:49
robruelopio: which silo 5?01:49
elopiorobru: ubuntu-rtm/lannding-005. The recent one with the fix by Saviq.01:50
robruelopio: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-005-1-build/76/console OK started a build for you. Yes in this case the build job didn't require any parameters. The parameters are only for edge cases, for a first silo build it doesn't need any01:54
elopiorobru: thank you.01:54
robruelopio: you're welcome!01:55
imgbot=== trainguards: IMAGE 290 building (started: 20141017 02:10) ===02:09
kgunnthanks guys02:21
popeycihelp in the morning can someone look at why https://code.launchpad.net/~dinko-metalac/sudoku-app/fix-1366007/+merge/238533 that is spamming from jenkins?02:31
fgintherpopey, I'll look now02:31
plarswow02:32
popeyyay02:32
popeythanks02:32
fgintherpopey, there's a bzr lock on the branch, I should be able to break it and end this madness02:33
popeythank you.02:34
* popey goes to sleep knowing the best people are on the case02:34
plarsfginther: how did that cause this? It looks like the job to update the MP only ran once02:35
bzoltanelopio:  the UITK failures came between #106 -> #10702:47
imgbot=== trainguards: RTM IMAGE 113 building (started: 20141017 03:10) ===03:09
bzoltanelopio: fginther: Here are my logs -> http://people.canonical.com/~bzoltan/UITK-AP-FAILURES-106-107/03:10
elopiohey bzoltan03:10
bzoltanelopio: fginther: Here is the diff between 106 and 107 -> http://people.canonical.com/~ogra/touch-image-stats/rtm/107.changes03:10
elopiosorry I haven't been able to help you03:10
elopiostill testing z.Z03:11
bzoltanelopio: fginther: one might think that the UITK is to blame because it landed on #107 ... but I have tested the exact same UITK on 106 and it is not failing as on 10703:11
bzoltanelopio:  no worries dude... I am just pushing this problem to the queue :)03:12
elopiobzoltan: what I've been seeing during this testing is that at random points, the screen freezes.03:14
elopioI have also seen media-hub consuming all CPU. And some people have been seing unity8 being killed by oom.03:14
bzoltanelopio: the 107 introduced new qtmir-android and unity803:15
elopiobzoltan: usually, when we see random errors, it's because we are excercising the device too much and it stops listening to swipes and clicks.03:15
bzoltanelopio:  wow... that sounds strange03:15
elopiobzoltan: it would be useful to look in the results for crashes03:16
bzoltanelopio: my tests are pretty clear ... 4 tests 2 with 106 and 2 with 107 ... with the same latest UITK ... 1-2 faulres vs 66-67 failures... befoew 106 there was no problem and since 107 we have problems03:16
bzoltanelopio:  now I am cornering my suspects... I will test on 106 with the display server from 10703:17
elopioand something we were thinking with ToyKeeper was to collect information of CPU and memory usage during runs.03:17
bzoltanelopio:  that would be fairy easy03:18
ToyKeeperWell, if one process consistently uses > 95% CPU for ... > 30 seconds, perhaps, it's probably an issue.03:18
elopiobzoltan: as the toolkit has the biggest suite, it is sadly the one that puts more pressure on the system.03:18
bzoltanelopio: pressure in what sense?03:19
ToyKeeperI saw a few processes explode but not crash, and cause other processes to get OOM-killed or otherwise fail.03:19
elopiobzoltan: if lrt have a mean time to failure of less than 5 minutes, it's clear that a suite that takes 40 minutes to run will cause many crashes.03:19
bzoltanelopio:  I see03:19
ToyKeeper("explode" as in excessive memory use or a dead-end CPU busy loop)03:19
bzoltanelopio: the UITK tests do not take longer than 30 minutes03:21
elopiobzoltan: well, that's still a lot more than the mean time to failure. We are not touching a lot of things that the lrt tests touch, like scopes and multimedia.03:24
elopiobut still we need to increase the mean time to failure.03:24
ToyKeeperFWIW, I wasn't thinking of monitoring CPU/mem load during regular autopilot tests...  mostly just during LRT.03:24
elopioToyKeeper: on bug #138230703:24
ubot5bug 1382307 in indicator-messages (Ubuntu) "reply to SMS (via indicator) fails silently if no default SIM is set" [Undecided,New] https://launchpad.net/bugs/138230703:24
elopioI get a dialog asking me to choose a sim03:24
ToyKeeperelopio: Huh, interesting.03:24
ToyKeeperI should re-test that.03:25
elopioToyKeeper: any chance you tried to send a single word without pressing space?03:25
ToyKeeperelopio: I tried to send "Boooooooooooog.", and it auto-corrected to "Bookkeeping." as I hit "send", and I think it then tried to send.03:25
elopioToyKeeper: yes, weird. When I tried to send "Test" without pressing space and then the send button was not enabled.03:26
elopioand when I clicked the disabled button, it was closed. It seems it silently succeeded.03:27
ToyKeeperelopio: I think the '.' will work too, not just space.03:27
elopioToyKeeper: yes, I'm not sure why I got the dialog. I had the sim on the second slot.03:27
ToyKeeperelopio: I've got both my SIMs in the krillin, and simply hadn't set one as default yet for SMS.  But I think perhaps I should re-test to confirm.03:28
cwayneToyKeeper: elopio: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1369737 ?03:32
ubot5Ubuntu bug 1369737 in ubuntu-settings-components (Ubuntu) "Send button does not enable until you press spacebar" [Critical,In progress]03:32
ToyKeeperI tried it later after setting a default SIM (again just one word followed by a period), and it worked.03:34
ToyKeeperelopio: Fresh after flashing, it does indeed ask me to select a SIM.  I wonder what happened last time.03:38
ToyKeeperelopio: If I manage to reproduce it, I'll update the bug accordingly.  For now, it's ... mysterious.03:39
kgunnToyKeeper: elopio if you guys are still on, silo5 looks good - fixes the edge demo and the AP tests all pass03:41
ToyKeeperkgunn: ... and I think 113 is currently building from cron with no changes.  :(03:41
kgunndang it...missed that boat03:41
elopiocwayne: yes, what we are trying to figure out is why the dialog to choose the sim didn't appear.03:42
elopioToyKeeper: ok, thanks.03:42
ToyKeepercwayne: I haven't been able to reproduce what I saw...  marked the bug as invalid until I can find a way to trigger it.03:42
cwayneah, sorry :)03:43
ToyKeeperelopio: It could be something else entirely...  like, after testing last night and thinking a message had been lost, my android phone received a SMS about 6 hours later while I was asleep...  not sure what caused the delay.03:44
elopiokgunn: I can confirm the silo and give the QA green light to get it in the next image.03:45
elopiobut let me finish the maps tests, because I keep getting distracted.03:45
kgunn:)03:46
kgunndistracted ? it's like 4am there or something03:46
kgunni'll keep doing a little exploratory manual testing as well...03:47
elopiokgunn: nah, it's 10 pm.03:49
Mirvmorning03:59
imgbot=== trainguards: IMAGE 290 DONE (finished: 20141017 04:00) ===03:59
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/290.changes ===03:59
Mirvpopey: ah, Mir bug, not a bug for me (or in me)04:03
Mirvoh, but it's on mako, maybe for me after all. I first read flo only. /me flashes04:05
* ToyKeeper -> lunch, or something approximating it04:13
imgbot=== trainguards: RTM IMAGE 113 DONE (finished: 20141017 04:20) ===04:19
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/113.changes ===04:19
bzoltanelopio:  the unity8 is clearer. It is not the troublemaker in #107 ... Now my top suspect... the mir04:29
bzoltanHello Mirv04:29
Mirvhi bzoltan04:29
Mirvbzoltan: the qtmir change in #107 added reading of localized app names from .desktop files04:31
Mirvpopey: yes, mako seems busted also after OTA upgrade to #9504:32
bzoltanMirv: and something made the UITK to fail ~67 tests -> http://people.canonical.com/~bzoltan/UITK-AP-FAILURES-106-107/04:34
Mirvbzoltan: yeah, but this is newer, this problem. your #107 problem is interesting if it's indeed not unity8 like you said.04:38
Mirvsince the qtmir change would sound like innocent and not affecting English usage04:39
bzoltanMirv:  I am checking these  http://people.canonical.com/~ogra/touch-image-stats/rtm/107.changes04:45
Mirvargh, I just can't get mako to bootloader menu since it's playing for me the red lights of dead play and only (barely) accepting the charger05:13
elopiotrainguards: rtm silo 5 ready to be published.06:25
abeatotrainguards, could I get a silo for gst-plugins? Line 39 of the spreadsheet06:33
Mirvelopio: thanks!06:34
Mirvelopio: do you know what has been agreed, that is supposed to be going in?06:34
Mirvabeato: rtm-01206:36
elopioMirv: I think nobody has been around to make that decission.06:36
abeatoMirv, awesome, thanks06:36
elopioMirv: but it wouldn't hurt to make a new version for it to be ready to test it in case they decide it should go, right?06:36
Mirvelopio: you're talking about 005 still? I mean, was it agreed to go in?06:41
Mirvbut at least it's surely good to have silos tested and ready to go06:42
popeyMirv: yeah, not a bug in or for you, but figured you'd be first online so if people needed poking you'd be around ☻06:42
Mirvpopey: right!06:45
MirvI've been trying to kick this mako alive after it lost the battery, and it finally did. bootstrap flash did not help, I'm retracing a couple of crashes in case they'd help something.06:49
elopioMirv: yes, I'm talking about silo 5. The bug still doesn't have a tag to see if it goes for 10/17 or not. I've just send an email with what we found today.06:54
elopiosomebody should reply with priorities for them.06:54
Mirvthanks elopio07:02
Mirvlocal retracing seems somehow broken for all of my crashes, so letting them off towards LP07:07
Mirvnot sure if I could connect to wifi from command line, but I'm just using USB networking07:15
dbarthmorning guys07:42
dbarthi have a problem with silo 20 which took a bad libmir dependency07:43
dbarthit seems to be a recurring pb for the online-accounts package07:43
dbarthlast time cjwatson made silo configuration changes to the silo07:44
dbarthcan you advise on what i should do to get this silo to build properly? just rebuild (?) ask for that same configuration change? or make a change in our packaging for example?07:45
Mirvdbarth: which bad mir dependency you're seeing? the same problem as previous time shouldn't be there as mir is the same version as in utopic08:03
=== tvoss|food is now known as tvoss
ogra_popey, Mirv, i updated bug 138227808:05
ubot5bug 1382278 in unity8 (Ubuntu) "Image #94 on mako / #88 on flo fails to start - mir crash" [Undecided,Confirmed] https://launchpad.net/bugs/138227808:05
Mirvogra_: popey: updated my notes too, I've already tried reverting libhybris, media-hub and qmenumodel but those don't seem to help08:08
Mirvoh, actually I didn't do media-hub correctly, trying again08:09
bzoltanogra_:  The qtmir-android qtdeclarative5-qtmir-plugin in the #107 makes the 66 UITK AP tests fail08:12
ogra_bzoltan, filed a bug already ?08:14
bzoltanogra_:  not yet, I just got the results...08:14
ogra_thanks for tracking that down !08:15
ogra_good work :)08:15
dbarthMirv: yes a libmirclient8; maybe i will rebuild cause i got it will it was in transit08:16
bzoltanogra_:  Should I file the bug here -> https://bugs.launchpad.net/qtmir08:16
ogra_bzoltan, yeah08:16
bzoltanogra_:  OK, I collect my logs and file it08:17
Mirvpopey: ogra_: ok correcting my mistake of reinstalling just the same version of media-hub, I can confirm that reverting media-hub (only) fixes mako08:18
ogra_Mirv, oh ... not even hybris ?08:19
Mirvogra_: no, I upgraded it back and it still works08:20
ogra_wow08:20
Mirvthe media-hub however seems like the one that tries to use new android interface (via hybris)08:20
popeyahh08:20
Mirv"Make use of MediaRecorderObserver interface"08:21
ogra_oh right08:21
ogra_well i think a simple upload of the android package with the changes is needed08:21
Mirvyes08:22
bzoltanogra_: Mirv: https://bugs.launchpad.net/qtmir/+bug/138241408:24
ubot5Ubuntu bug 1382414 in QtMir "New qtmir makes UITK AP tests fail" [Undecided,New]08:24
* ogra_ wonders if sil2100 will get up in time for the meeting 08:31
ogra_(perhaps not :) )08:31
=== vrruiz_ is now known as rvr
ogra_that looks pretty landed to me09:10
ogra_and rmadison agrees :)09:10
* ogra_ kicks an image09:10
Mirv\o/09:11
imgbot=== trainguards: RTM IMAGE 114 building (started: 20141017 09:15) ===09:14
* asac goes 11309:47
ogra_113 is sweet09:47
ogra_(114 will be even better)09:48
asacwill we promote that?09:48
ogra_114 ?09:48
ogra_hopefully09:48
asaceither09:48
asacok09:48
asacwhats coming in 114?09:48
ogra_not either09:48
ogra_see my mail :)09:48
ogra_(to phablet@)09:48
ogra_114 has a fix for the broken edges intro09:48
asacoh thats broken?09:49
* asac should do that intro regularly09:49
ogra_sadly mako and flo are completely broekn in both ... they will need a 115 ince rsalveti is up09:49
ogra_*once09:49
asacI wonder if we should make the intro available as an app so folks that did miss or didnt get it can retry etc.09:49
ogra_we have a phablet-config command  to en/disable it09:49
asacogra_: 114 is completely broken on mako?09:49
asac113 too?09:50
ogra_asac, yes, and flo (see my mail)09:50
asacok, well let me read email in a bit then09:50
ogra_back to 11209:50
ogra_a media-hub fix landed that needed a device tarball change09:50
asacguess we dont want to promote iuf mako is really broken09:50
ogra_that change is only in the krillin tarball09:50
asacah ok09:50
asacbut the change needed is already in thge code base?09:51
ogra_no, we ant to wait til rsalveti shows up and can do an android upload into rtm09:51
ogra_and then roll 115 ....09:51
ogra_but we might promote 114 for krillin inbetween09:51
asacsure dont want to do it without rsalvetu. just wondered if it was a sync problem09:51
asacguess we can check once 115 is there09:51
ogra_kind of09:51
asacright09:51
asaccoordination problem09:51
ogra_its a sync problem on the git level :)09:52
asacoh... interesting09:52
asacweonder how we do that at all09:52
ogra_the oofficial android images simply didnt get ti yet09:52
asackeepinhg our android code bases insync09:52
asacthat is09:52
ogra_usually we land first in the official android tree, then port over to krillin09:52
ogra_this one change was the other way round09:52
asacright. guess folks were ambitious to ge3t it into krillin09:53
asacgreed09:53
ogra_to fix krillin quickly09:53
asachehe09:53
ogra_the pressure was a lot higher in wed :)09:53
ogra_*on09:53
ogra_113 already looks very very good though ... i hope victor gives his go for 114 then ...09:54
ogra_(and i wonder if/when sil2100 will show up :) )09:54
ogra_seems he worked with Saviq on the edges fix last night, they were both up til 2am09:55
ogra_(and sil was up he night before til 4am (or later, thats when i went to bed))09:55
sil2100...10:03
Mirvsil2100: morning! :)10:03
sil2100I overslept, no idea why the alarm didn't wake me up10:03
Mirvsil2100: it's just good for you...10:03
sil2100First time that happened10:03
brendandsil2100, probably because you were shattered10:03
sil2100ogra_, Mirv: anything happened on the meeting? ;)10:04
Mirvsil2100: we received a "go" for 005 from victor, and discussed the mako issue10:07
sil2100Mirv: is 005 the fix for the swipe tutorial?10:07
Mirv005 fixed the edges intro. mako needs android upload but it can be manually fixed by reverting media-hub to previous version.10:07
Mirvsil2100: that10:07
sil2100Excellent o/10:07
Mirv#114 with it should be built within 30 mins or so (started 1h ago)10:08
sil2100Yay, thanks everyone!10:08
* sil2100 feels really stupid about oversleeping10:08
sil2100I blame my phone10:08
nik90sil2100: may be the alarm rang, but you didn't hear it in your deep sleep. :P ?10:09
* nik90 always pop out when there is an conversation about alarms ;)10:09
sil2100No, I think my phone died due to low battery power, hmmm10:09
Mirvnik90: /hilight alarm ? :)10:09
sil2100hah10:09
nik90sil2100: ah...that's ain't my fault :)10:09
sil2100;)10:09
popeyis it possible to set a custom ringtone yet? or is that not done?10:10
nik90Mirv: lol..I didn't do that until now,, but that sounds better than keep an eye on this channel10:10
popeyi.e. an ogg file I have on my phone.10:10
sil2100Oh gosh, so Saviq actually did the fix at that hour?!10:10
sil2100ogra_, Mirv, john-mcaleely: so the plan is to roll out a new device tarball for all the other platforms after this image finishes?10:12
sil2100I think we might want to open up the gates after this image is finished then10:14
ogra_sil2100, morning !10:16
ogra_sil2100, we cant just "roll" another device tarball10:16
ogra_that needs rsalveti ... and an upload of the android package10:16
sil2100hm, right, we don't have a new device tarball right now to roll out10:17
ogra_sil2100, i think we should wait with opening the gates til that is in10:17
ogra_sil2100, but 114 could be promoted if victorp signs it off10:18
sil2100brendand: how many people do we have from QA today?10:18
ogra_sil2100, we also decided 114 doesnt need a full test run ... the change is a 1 liner thats easy to verify10:19
sil2100ogra_: do we need QA to sign-off the delta in this agreenment, or does Victor want to take it as it is?10:19
sil2100That makes sense10:19
ogra_right, we want a delta check ... and some dogfooding10:19
ogra_and then talk to victor again10:19
ogra_... get his sing-off and promote krillin ...10:20
sil2100You mean, only promoting for krillin?10:21
ogra_yes10:21
ogra_and promote 115 afterwards for the other arches10:21
sil2100Ok, makes sense, but I guess I'll have to wait for the official announcement once we have all promoted10:21
ogra_(which i why i said we need to keep the gates still locked)10:21
sil2100No need to promote something broken10:21
bzoltanogra_: sil2100: Do you think it would be acceptabe from the QA point of view if I run my 9h tests on #106 image and not on the #107+ what are all busted for UITK tests?10:22
bzoltanbrendand: ^10:22
sil2100bzoltan: I think I saw some discussions here regarding UITK being a bit brokenish, but do you know maybe why UITK tests are busted on the newer images?10:22
bzoltansil2100:  No, the UITK is not broken, not even brokenish... simple the new mir broke the UITK tests10:23
bzoltansil2100: https://bugs.launchpad.net/qtmir/+bug/138241410:23
ubot5Ubuntu bug 1382414 in QtMir "New qtmir makes UITK AP tests fail" [Undecided,New]10:23
sil2100This is a very tricky situation - I leave the decision in QA's hands, but we really need to get someone from qtmir team working on it then10:25
sil2100Maybe add a section in their test plan to at least run some sub-set of your UITK tests during release10:26
brendandsil2100, just me really10:26
bzoltansil2100:  that was my first thought too10:26
brendandsil2100, well rhuddie and vrruiz are around as well10:26
sil2100ricmm, camako: can you guys maybe find someone to take a look at LP: #1382414 ?10:27
ubot5Launchpad bug 1382414 in QtMir "New qtmir makes UITK AP tests fail" [Undecided,New] https://launchpad.net/bugs/138241410:27
sil2100brendand: ACK, ok, so even with the gates opened we'll have rather a slow day for releases anyway :)10:27
sil2100brendand: you guys busy with iso testing still??10:28
sil2100(- one ?)10:28
brendandsil2100, iso?10:28
bzoltanbrendand:  my question is that which one you prefer: (1) I run UITK silo13 validation against #107+ and see 67 failures or (2)on #106 where everything is as normal?10:29
ogra_brendand, desktop RC10:29
brendandogra_, yeah but why would i be doing that :)10:29
jibelsil2100, almost all the team is traveling today or will be really soon10:29
ogra_no idea, tell me :)10:29
imgbot=== trainguards: RTM IMAGE 114 DONE (finished: 20141017 10:30) ===10:29
sil2100jibel: ACK10:29
sil2100Yay!10:30
ogra_hey10:30
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/114.changes ===10:30
ogra_ah10:30
jibelsil2100, and next week davmor2 and omer will help me with the release of utopic10:30
sil2100Now for a QA sign-off on that and to Victor we go10:30
* ogra_ just wanted to complain aboutteh missing changelog10:30
sil2100We like changelogs like these10:30
ogra_yeah10:30
brendandok time for a smoke test10:30
* ogra_ OTAs10:31
ricmmmzanetti: hey ^ can you take a look at 138241410:31
ricmmlooks like the desktop file reader changes10:31
ogra_ricmm, do you knwo if rsalveti will be around today ? (i cant remember him saying anything ... i know sergio is in the air)10:32
sil2100As we can't really revert media-hub right now, at least not without introducing a regression10:35
ogra_yeah10:35
ogra_114 looks fine here after OTA10:35
* sil2100 checks the changelog for the last upload10:35
sil2100I'm flashing with the u-d-f10:36
ogra_sil2100, well, we dont miss bits in media-hub ... media-hub makes uses of the changes in the device tarball10:36
sil2100Right, so looking at the changelog we might be able to revert it temporarily as a last resort, but we basically get rid of a pretty good fix10:38
sil2100And the fix itself is not at fault here10:38
ogra_yeah, and it will cause chaos10:38
ogra_lets rather wait ... it isnt like people cant push fixes to silos :)10:38
ogra_or that we are low on silos10:38
ogra_(we just dont release then yet)10:39
ogra_*them10:39
nik90will the promotion happen on mako as well since it looks like 114 might be promoted?10:40
ricmmogra_: he should be around10:40
ogra_no, mako is obviously broekn10:40
ricmmwhat hppened to media-hub ?10:41
sil2100nik90: we need to wait for one thing before we promote for mako10:41
nik90ah the boot issues10:41
ogra_which is what tthe discussion above is about10:41
sil2100nik90: we basically need a new android upload and device bits10:41
ogra_ricmm, the devlice tarball changes didnt land in mako or flo ...10:41
ogra_ricmm, so both dont boot anymore10:41
nik90ah ok10:41
ricmmah you landed silo 00510:41
ricmmlol10:41
ogra_right10:41
ricmmdid you land that today? or last night when salveti was on10:41
ogra_which is fine on krillin :)10:41
ogra_last night10:42
ricmmyea there was no android source pkg pushed in there10:42
ogra_i think nobody thought about the android package10:42
ricmmthe patch lnded to phablet git10:42
ogra_due to the krillin pressure10:42
ricmmif you are able to build an android package, you cn do it10:42
ogra_i dont know if it automatically checks out during build ... i fear not10:42
ricmmno, you have to build it manually10:43
ricmmafaik10:43
ogra_and i dont have a phablet tree here ... til that is checked out he will be up10:43
ricmmI need to run to the bank as I have an appointment but I'll be back in a bit10:43
ricmmmaybe I can help10:43
ogra_cool10:43
sil2100ricmm: thanks!10:43
sil2100Anyway 114 looking good here10:43
ogra_yeah10:44
ogra_really good10:44
brendandogra_, sil2100 - we *might* have a problem10:44
ogra_!10:44
ogra_stop finding them !10:44
ogra_brendand, with the fix or did you find something new ?10:45
sil2100brendand: wha's happening?10:45
sil2100Ah the suspence10:46
sil2100;)10:46
ogra_heh10:46
brendandsil2100, sorry my wife called me just after typing that :)10:47
ogra_you make that up, right ?10:47
ogra_:P10:47
ogra_you just want to raise the excitement :)10:48
brendandsil2100, i need 5 more minutes to double check what i found10:48
sil2100brendand: but is that a problem with the fix itself, or something completely new that we didn't see before?10:48
ogra_4:30 ...10:48
ogra_(we seem to have some improvement for the fix from dednick )10:49
sil2100hm?10:50
ogra_he pinged me after we landed the silo10:50
ogra_saying he has some improvements10:51
brendandogra_, i think the new fix doesn't work well10:51
ogra_dednick, ^^^10:51
ogra_where is your change ?10:51
brendandogra_, as in - worse than it was before10:51
ogra_uuuh10:51
brendandand i'm a bit annoyed at elopio now10:51
ogra_why did elopio sign it off thn10:51
ogra_*then10:51
brendandbecause if i confirm this then he obviously didn't test it right10:51
brendandso i'm hoping it was a fluke10:52
sil2100ACK10:52
ogra_tsdgeos, ^^^do you know wehere dednick's improvement is ?10:52
dednickhavent pushed yet10:52
ogra_brendand, are you doing a full day today ?10:54
brendandogra_, yeah10:54
ogra_cool10:54
brendandogra_, but not longer10:54
ogra_heh10:54
brendandogra_, 5:30 sharp finish10:54
ogra_5:30 ? portland time ?10:54
ogra_:P10:54
brendandphew it was a fluke10:54
brendandbreaths in10:54
sil2100Phew10:55
ogra_oh man10:55
brendandbut still it seems there might be some flaky behaviour there10:55
ogra_at least now i'm fully awake :)10:55
brendandbasically i pulled down the indicator and it was stuck10:55
ogra_brendand, right, we can land dednick's improvement in 11510:55
brendandwould not go back up10:55
brendandthis time it didn't happen10:55
ogra_(if that fixes it indeed)10:55
sil2100ogra_: is there a landing for that?10:56
ogra_no10:56
ogra_see above :)10:56
ogra_not pushed yet10:56
brendandogra_, let's promote after lunch if i don't find anything further10:56
ogra_brendand, tell victor and asac :)10:57
ogra_i think the final decision should be in tehir hands10:57
ogra_(i agree though)10:57
Mirvphew10:58
sil2100The indicator drop down works reliably on my device at least10:59
ogra_sil2100, in the edge intro ?10:59
bzoltanwhat? we got a promotable image?11:02
sil2100bzoltan: we *might*, yes, waiting for management decision11:03
bzoltanfingers crossed11:04
asacogra_: sil2100: can we technically promote just one device without stgraber?11:14
ogra_yes11:15
brendandbzoltan, i didn't answer your question sorry11:16
bzoltanbrendand:  no worries.. I started to test against #11411:17
brendandbzoltan, if you need to land the fix for https://bugs.launchpad.net/bugs/1368492 then we could make an exception, but we'd be much more comfortable if your tests were working again11:17
ubot5Ubuntu bug 1368492 in ubuntu-ui-toolkit (Ubuntu) "crash opening image file" [Critical,In progress]11:17
brendandbzoltan, you need to get them working again asap anyway11:17
bzoltanbrendand:  https://bugs.launchpad.net/qtmir/+bug/138241411:18
ubot5Ubuntu bug 1382414 in QtMir "New qtmir makes UITK AP tests fail" [Undecided,New]11:18
bzoltanbrendand:  I am a victim here...11:18
brendandbzoltan, no-one around to help you with that?11:18
bzoltanbrendand:  the qtmir landed on #107 broke the UITK tests11:18
Mirvbrendand: peo11:19
Mirvple have been pinged11:19
brendandpeople?11:19
brendandok11:19
brendandsil2100, agggh - i might need to take back what i said... so frustrating11:20
brendandsil2100, sorry11:21
bzoltanogra_: sil2100: brendand: Mirv: the reason why I run ~800 tests and all available app's AP tests before each UITK release is to ensure that the UITK does not break the apps or the AP tests of the apps... because they all depend on UITK. I would recommend the same QA measure for other components with similar dependencies on them.11:21
tvosstrainguards, can I get a silo for line 54?11:21
brendandbzoltan, well yes i hope that if peoples tests are failing they are fixing them11:22
Mirvmzanetti was last pinged on that issue, but not sure if he's travelling11:22
brendandMirv, i guess he is - i saw he arrived today on the spreadsheet11:22
ogra_what is he doing on that spreadsheet ?11:23
bzoltanbrendand: it is not that simple... I would say that if your release breaks the tests of other projects then you are expected to react. The same way my team was and is fixing app tests sometimes.11:23
* ogra_ would have flown direct to washington instead11:23
tvossogra_, alter ...11:23
tvoss:)11:23
brendandsil2100, the bug might depend on the indicator you drag down11:23
pete-woodsjust checking, is there any chance of silo assignment (for genuine critical bug) today?11:23
brendandor not11:24
ogra_tvoss, hehe11:24
Mirvtvoss: rtm-00611:24
tvossMirv, utopic silo wouldbe good actually :)11:24
Mirvtvoss: utopic is in final freeze...11:24
tvossMirv, ah okay11:24
tvossMirv, with that, I can just reuse rtm 411:24
Mirvsince midnight11:25
tvossMirv, could you trigger a build of rtm 4? not sure I can easily do it11:25
Mirvhttps://wiki.ubuntu.com/FinalFreeze11:25
tvosslool, ^11:25
Mirvtvoss: oh sorry, right, not rtm-006 but 006 :)11:25
tvossMirv, now I'm confused11:25
tvoss:)11:25
Mirvtvoss: I mean, 54 is utopic line so it got utopic silo as well - 006. but of course, probably not to be landed to utopic.11:26
Mirv"release critical bugs, security critical bugs, exceptional circumstances"11:26
Mirvogra_: do you know if we'd still land things to utopic until ~release day or not?11:27
Mirvtvoss: we can try with your line 54 of course and see if it still gets auto-accepted :)11:27
ogra_Mirv, i think sil2100 wanted to hold back utopic too (for touch)11:27
tvossMirv, ack11:27
Mirvogra_: right, so sil2100 is our barrier, not the fact that 14.10 is being released :)11:28
MirvI think on Tuesday utopic uploads will need to stop anyhow11:28
MirvI'll call 15.04 now "viper", the first on https://wiki.ubuntu.com/DevelopmentCodeNames#A15.0411:29
Mirvv-series is so boring11:29
=== renato is now known as Guest37257
Laneyargh11:33
Laneysomeone help me upload to an RTM silo with dput-ng11:34
ogra_sudo apt-get install dput11:34
ogra_:P11:34
MirvLaney: ^ :)11:34
* ogra_ never used -ng11:34
Laneynever11:34
MirvI was about to say something along those lines too11:35
Laneynot since I accidentally uploaded to the wrong release11:35
Laneyok, no help here, I'll go figure it out11:35
MirvI added default_host_main = notspecified after I accidentally uploaded something to the main archives (before I had rights to do so), and I'll only comment it out when I really want to upload something to archives11:35
LaneyIt was in Debian and I had sbuild -d unstable instead of experimental11:36
ogra_Laney, wouldnt have happened if debian used silos ;)11:36
MirvDebian would surely love google docs spreadsheet for package management11:37
lool:-)11:38
Laneyok, now we're trolling, really going to find out for myself11:38
loolLaney: dput ppa:ci-train-ppa-service/ubuntu-rtm/landing-004 worked for me11:38
loolbut I think I commented out some checks11:38
Laneyit's trying to append /ubuntu/11:40
ogra_Laney, but its FRIDAY !11:40
Laney/ubuntu11:40
ogra_we are supposed to troll, no ?11:40
loolproblem is that I didnt take time to note down what I had patched11:40
loolI have /etc/dput.d/profiles/ppa.json: http://paste.ubuntu.com/8578672/11:40
loolrecently editied11:40
=== boiko__ is now known as boiko
loolok, I edited /usr/lib/python2.7/dist-packages/dput/hooks/distro_info_checks.py11:42
loolLaney: http://paste.ubuntu.com/8578686/11:43
loolI know, classy11:44
Laneynice11:44
LaneyI did something like that, yeah, having problems with the incoming path11:44
LaneyLaunchpad failed to process the upload path '~ci-train-ppa-service/ubuntu-rtm/landing-012/ubuntu':11:44
loolLaney: I pasted my ppa.json above, uploaded worked for me with above dput invocation yesterday11:45
LaneyCould not find suite 'ubuntu'.11:45
Laneyit's the same as mine11:45
Laneyblerg11:45
loolcan't tell why, mine says: 2014-10-15 20:42:07,529 - dput[62836]: uploader.invoke_dput - Uploading lxc-android-config using ftp to ppa (host: ppa.launchpad.net; directory: ~ci-train-ppa-service/ubuntu-rtm/landing-004)11:45
loolno /ubuntu at the end11:46
loolLaney: maybe check your .changes has Distribution: 14.0911:47
Laneysure does11:47
Laneywhat about your /etc/dput.d/profiles/ubuntu.json?11:47
loolit's from july, I didn't touch it, http://paste.ubuntu.com/8578695/11:48
lool/etc/dput.d/metas/ubuntu.json has http://paste.ubuntu.com/8578703/11:49
Laneyhmm ok11:49
looltrainguards, I understand custom tarball has landed, would you mind updating line 46 to say so?11:51
sil2100lool: ah! Right, doing11:51
loolis it worth staging utopic updates in utopic-proposed for post-release SRUs?11:53
lool(trying to figure out how we land stuff in trunks in the next couple of weeks)11:53
looltrainguards, line 41 (location-service sync to rtm to pickup fixed gps provider): I've changed "sync:ubuntu,utopic location-service lxc-android-config" to "lxc-android-config sync:6 location-service", is that correct? mind reconfiguring11:56
loolI dont want to add lxc-android-config to the utopic silo as it would require using a version higher than the one in utopic which has unwanted changes11:56
sil2100lool: uh, I was just assigning that before you changed11:56
loolsil2100: rtm silo 4? sorry11:57
loolsil2100: was trying to fix it, I can revert11:57
sil2100lool: no no, it's fine, let me think about this11:57
loolsil2100: so right now I think we want to combine a manually created lxc-android-config with a cherry-pick just for rtm and a location-service binary from an utopic silo -- that wont actually go in utopic11:58
sil2100lool: ah, ok, then we need to do it differently11:58
sil2100lool: let me prepare the line11:58
sil2100lool: ok, so, I prepared the line in such a way that CI Train will understand, but there is a small 'but'12:02
loolsil2100: I prefer small buts12:02
sil2100lool: whenever you want to sync packages with the build job, you need to list the package name you want to sync in the list to rebuild, i.e. the location-service12:02
sil2100;)12:02
loolok12:03
sil2100lool: lxc-android-config you can just upload directly to the PPA and then run watch-only12:03
loolit's there already12:03
looland cant go in the other PPA anyway12:03
sil2100Ok, then I suppose it should be ok with that, just remember to not do any builds without any parameters in the list12:03
loolok12:04
looltvoss: ^ fyi12:04
looltvoss: binaries ready12:07
tvosslool, in rtm 4, or utopic 6?12:07
loolutopic 612:08
tvosslool, ppc64el falied, looks flaky12:08
Mirvtvoss: so, I've tested that non-seeded utopic uploads still go in, so when/if something is allowed to go in by sil2100, we can still land to utopic (until ~Tuesday)12:09
looltvoss: binaries installed; testing now12:09
Mirv"tested", ie. released qt creator plugin12:09
tvosslool, ack12:11
looltvoss: I'm getting some errors in HERE webapp, but it eventually works12:11
loolthis is espoo only12:12
tvosslool, ack12:12
tvosslool, a test seems to be flaky, let me try to address that12:12
loolgoogle maps webapp worked fine and square; openstreetmap webapp didn't12:12
looltesting browser now12:12
loolin browser, I could get here to work too with similar errors; google shows correct location, but no dot12:14
olligm12:15
ollisil2100, how is 114 coming along12:15
looland bing works12:15
looltvoss: so that's a really huge improvement over what we had; trying GPS now12:15
tvosslool, in here, hitting the button on the bottom left while it's gray is supposed to give an error12:15
tvossI read through the javascript12:15
looltvoss: bad news, I can't get a GPS fix12:18
tvosslool, mind checking /data/misc12:18
tvosslool, are you outside?12:18
tvosslool, how would you know that you have a gps fix?12:19
tvosslool, just asking :)12:19
looltvoss: I usually get a GPS fix reliably when standing on my balcony for <1mn12:20
MirvI go to espoo today...12:20
loolI put the phone in a relatively open place12:20
loolit's a bit cloudy, but it's been worse12:20
tvosslool, okay, let me recheck12:21
looltvoss: oh wait12:23
looltvoss: stupid me12:23
looltvoss: I need to change the location-service flags in lxc-android-config12:23
tvosslool, ack12:24
looltvoss: do we still want the sleep 10?12:24
tvosslool, let's try without12:25
looltvoss: how do you start the gps provider?12:26
looltvoss: we need to add an upstart job for it12:26
tvosslool, I did not split it out, yet12:27
tvosslool, let's keep that for after this landing12:27
tvosslool, one by one :)12:27
looltvoss: ah then I'm confused; am I supposed to update the flags then?12:27
tvosslool, nope12:27
looltvoss: ok, then it doesn't work right now12:27
tvosslool, if you already have the gps provider in the config again12:27
loolI do12:27
ogra_=== IMAGE Krillin 14.09 #5 Promoted ===12:27
tvosslool, rechecking here12:27
ogra_sil2100, asac ^^12:28
tvosslool, could you check /data/misc, please?12:28
olliogra_, which image is that12:28
looltvoss: hmm something is wrong, I think I have the wrong lxc-android-config12:28
olli114?12:28
looltvoss: need to reinstall it12:28
ogra_olli, yep12:30
olliogra_, all tested and stuff?12:30
olliawesome12:30
ogra_yeah12:30
ollinice to be waking up to something like that12:30
ogra_and coordinated with victor and asac12:30
sil2100Yep12:30
ollithanks everyone12:30
ogra_114 is a beauty !12:30
sil2100olli: we'll have another promotion once the mako/flo bits are fixed12:31
* sil2100 is really happy about 114 too12:31
ollinice12:31
ogra_right, the hectic of krillin sadly broke the rest12:31
ogra_just one missing merge though12:31
ogra_(the the rrespective other device tarballs)12:31
looltvoss: everything works  \o/12:33
kgunnogra_: sil2100 we're ok now?12:33
tvosslool, same here :)12:34
looltvoss: webapps, web browser, osmtouch -- with gps fix12:34
tvosslool, yup12:34
* kgunn read a bunch of scroll back12:34
loolthat's on krillin12:34
ogra_kgunn, seems dednick has some improvement, but we went ahead with what we had12:34
kgunnogra_: yeah, was wondering if there was another hold up to get a more "professional" fix :)12:34
ogra_kgunn, so *we* are good, your team might still want to sort some code out later though12:34
looltvoss: building silo 4 to pick up silo 6's packages12:34
Mirvpromotion \o/12:34
ogra_:D12:34
tvosslool, just pointing out that I see some test flakiness12:34
looltvoss: ah hold on, some ftbfses there12:35
looltvoss: right12:35
tvosslool, yup12:35
tvosslool, on it12:35
loolok12:35
sergiusensMirv: sil2100 seb128 hey rtm silo 17 shouldn't be needed with what was landed yesterday in rtm silo 8; feel free to double check12:36
sergiusensbut if it's to address LP: #1378941 ... then that's already in12:36
ubot5Launchpad bug 1378941 in indicator-transfer (Ubuntu RTM) "Unity 8 crashes when downloading zip albums from 7digital" [Critical,Fix released] https://launchpad.net/bugs/137894112:36
Mirvseb128 can double-check and free the silo12:37
Mirv(or mark the line as "please remove")12:38
dbarthMirv: hey, is there a place where i can find the mediahub packages to revert to?12:48
dbarthlool: are there fixes you need applied to our packages?12:50
looldbarth: you mean web stack? nope12:51
looldbarth: FYI I'm hitting an unimplemented code path fairly often; I dont know whether that's planned for oxide, but it does trigger warnings regularly12:52
dbarthlool: which warnings?12:57
Mirvdbarth: I posted the instructions to the mailing list.12:59
Mirv(ubuntu-phone)12:59
looldbarth: I'm trying to grab them, sorry, had been distracted13:00
looldbarth: [1017/123311:ERROR:oxide_access_token_store.cc(30)] Not implemented reached in virtual void oxide::AccessTokenStore::LoadAccessTokens(const LoadAccessTokensCallbackType&)^M13:02
dbarthMirv: oops, seeing them now; thanks13:02
looldbarth: I'm getting this in webapps and webbrowser13:02
looldbarth: things seem to work though, I dont know what that implies13:02
dbarthlool: ok13:03
=== karni is now known as karni-lunch
seb128sergiusens, Mirv, thanks, silo cleaned13:33
Laneylool: turned out that it was because it was parsing /etc/dput.cf ...14:27
brendandpstolowski, if you're around, i'm trying to land silo 003 again, but it only seems to fix half the problem described in https://launchpad.net/bugs/138058814:30
ubot5Ubuntu bug 1380588 in unity-scopes-api (Ubuntu RTM) "Results blank after reboot when scope is signed in to OA" [Critical,In progress]14:30
brendandpstolowski, actually maybe i'm asking the wrong person - seems you aren't on the list of landers14:31
brendandthostr_, ^14:31
pstolowskibrendand, unfortunately marcus who created the fix isn't around anymore (he starts his travel to the sprint) and i'm not familiar enough with this area to look into it14:34
brendandpstolowski, yeah that's ok14:34
=== karni-lunch is now known as karni
asacogra_: sil2100: what is the version of promoted 114 image?14:51
sil2100asac: #5 in the 14.09 channel for krillin14:52
ogra_asac, what he said14:53
dbarthsil2100: that mako fix, is there a silo we can take it from?15:07
dbarthi would like to confirm that the regression i saw with OA trust prompts (on mako) is due to that15:08
sil2100dbarth: not really... as it's an issue with device and android bits missing15:15
sil2100dbarth: for now the only safe way is to just revert media-hub15:15
dbarthsil2100: right, i did that, but now i'm seeing regressions in trust prompts, ie none of the online accounts or trust store prompts seem to work properly15:22
dbarthanyway, i can wait or switch back to utopic on that device, that's ok15:23
pmcgowanrsalveti, any idea why dbarth is seeing that regression? ^^15:28
ogra_the online accounts regression ?15:28
pmcgowanogra_, yes15:29
dbarthon mako rtm (#96), the trust prompts for OA they suddenly start a whole OA "app"15:29
dbarthand i don't see prompts either for the location service15:29
ogra_tvoss, ^^^^ any idea ?15:29
ogra_location only prompts once per app15:30
ogra_if you ever allowed it it keeps that setting15:30
dbarthhmm, true; i should clear the DB15:30
ogra_rsalveti, ^^ stop using booleans !15:32
* rsalveti trying15:32
ogra_:)15:32
rsalvetifailed again15:32
rsalvetiwtf15:32
rsalvetisil2100: need your help :-)15:33
rsalvetihttps://ci-train.ubuntu.com/job/ubuntu-landing-008-2-publish/41/console15:33
tvossogra_, no idea :) fixed?15:37
ogra_lol15:37
ogra_TGIF15:37
dbarthtvoss: somehow15:37
dbarthtvoss: i see the prompts, once i wipe trust.db15:37
dbarthtvoss: but if i toggle permission from USS15:37
tvossdbarth, okay, that is expected15:37
dbarththe app still gets access, as the location service seems to cache the permission15:38
dbarthie, trust.db contains a series of 0, 1, 0, 1 when i toggle the switch15:38
dbarthbut ubuntu-location-service-trust-stored.log says that's a cached request15:39
tvossdbarth, ah, that's interesting. you only delete the most recent one I would guess15:39
dbarthi remove the trust.db file alltogether15:39
dbarthbut didn't restart the service15:39
dbarthif that forces it into a fallback mode (my db was killed, so i run on cache ?)15:39
Ursinhasil2100: I think a bug might have been introduced in citrain/publisher.py by r78015:39
Ursinhasil2100: https://ci-train.ubuntu.com/job/ubuntu-landing-008-2-publish/42/console15:40
Ursinhacitrain/publisher.py L246, silo_state.is_publishing is a property and it's being called15:41
bfillerrobru, sil2100: I need a silo for line 55 please15:44
Ursinhasil2100, robru: https://code.launchpad.net/~ursinha/cupstream2distro/fix-is-publishing-being-called/+merge/23873815:46
Ursinharidiculous fix, prepared that as it's probably easier to get the fix in production sooner via MP (automated ways, etc)15:47
ogra_sil2100, android landed, firing off a build15:53
kenvandinewoot15:53
nik90yay15:58
imgbot=== trainguards: RTM IMAGE 115 building (started: 20141017 16:00) ===15:59
sil2100Ursinha: hey ;)16:00
sil2100Ursinha: ah, crap!16:01
sil2100Right, damn, such a stupid mistake16:01
sil2100rsalveti: this will be fix as soon as it gets merged16:01
sil2100Should be any inute now16:01
sil2100*minute16:01
rsalvetisil2100: no worries, I decided to just go ahead and manually copy to the archive16:05
=== karni is now known as karni-eod
bfillersil2100: actually scratch last request, need a silo for line 48 which is the same request that has been there for some days16:11
rsalvetisil2100: I don't think appending ~rtm will solve the issue you described in the email16:12
rsalvetithe issue is one thing, identifying the issue is another different thing16:13
rsalvetithe issue can still happen16:13
elopioping kgunn: can you plesae take a look at https://bugs.launchpad.net/qtmir/+bug/1382414 ?16:13
ubot5Ubuntu bug 1382414 in QtMir "New qtmir makes UITK AP tests fail" [Undecided,New]16:13
kgunnelopio: ack, likely won't get much love until monday16:15
Ursinhasil2100: just to clarify, what I called ridiculous was having one MP for such a small change, not the problem itself :)16:16
elopiokgunn: yes, I supposed that :) I don't think bzoltan's planning a release today anyway. But maybe during the sprint we can talk about ways for mir to not break higher level tests.16:17
elopioIt would be perfect if we make the toolkit tests autopkgtests, so they run as a reverse dep when mir lands, but we are a little far from that.16:17
elopioso the alternative for now (I think) would be to run the toolkit tests as part of the mir release test plan. At least a subset.16:17
kgunnelopio: i would trade having to do that if others ran the unity8 AP test also :)16:19
elopiokgunn: the sdk does run unity8 tests. So who else would you like to run them? We can certainly add that to their test plan.16:25
brendandogra_, saw what you mean now16:25
ogra_brendand, cool16:26
brendandogra_, bug # yet?16:27
ogra_nope, didnt file it yet16:27
brendandogra_, usually when i reboot the phone i go and do something else - not looking at the screen :)16:28
brendandogra_, i'll file you a bug16:28
brendandogra_, or actually maybe rhuddie filed one since he mentioned seeing it16:29
ogra_right, thats why i asked :)16:29
sil2100bfiller: sure! Assigning16:37
bfillersil2100: thanks16:42
kgunn_elopio: is the uitk AP faililng on rtm or utopic ? or both ?16:58
kgunn_hard to keep up with image #'s16:58
elopiokgunn_: they are failing on their MPs, so I think on both.17:00
elopiobut haven't run the tests myself this week.17:00
kgunn_elopio: ta...hmm...ok, so very few things changed on qtmir -rtm17:00
kgunn_hmm....this looks like the only commit that might effect those tests17:02
kgunn_http://bazaar.launchpad.net/~mir-team/qtmir/rtm-14.09/revision/26817:02
elopiokgunn_: there was something from the qml cache that made all the other tests fail too, right? I think I heard about it, but I've lost touch with automation.17:04
elopioplars: ^ ?17:04
kgunn_i didn't catch all the details either17:05
plarselopio: rtm on mako fails to come up right now, is that what you're referring to?17:05
plarselopio: there's a new image building now that I think is supposed to fix it17:06
elopioplars: no, I'm wondering if you remember about a fix to make the autopilot tests pass after the qml cache was introduced.17:06
plarselopio: no, I'm not familiar with that, when was this?17:07
elopioI'm not sure. I'm having a brain overload.17:08
elopioricmm or brendand: I think I saw a silo for qml cache that broke autopilot tests. Do you know about it? Or am I in a mistake?17:09
kgunn_hmmm....so how the hell did this get into qtmir/rtm17:09
kgunn_https://code.launchpad.net/~ricmm/qtmir/clean-cache-on-failed/+merge/23807717:09
kgunn_it's not approved17:09
* kgunn_ is confused17:10
imgbot=== trainguards: RTM IMAGE 115 DONE (finished: 20141017 17:20) ===17:19
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/115.changes ===17:19
sil2100\o/17:20
sil2100Can we get anyone with a mako confirming if this works? ^17:20
nik90does this need QA to promote considering that its krillin counterpart was heavily tested?17:21
sil2100elopio: do you have a mako with ubuntu-rtm installed on it?17:21
sil2100nik90: we just need someone to do a quick dogfooding run, making sure it works and nothing is obviously busted17:21
sil2100So I would say around 15 minutes of play time on it17:21
nik90cool17:21
sil2100elopio: ^ :)17:25
* ogra_ only has an ubuntu mako :(17:26
elopiosil2100: I can flash it.17:36
elopioI'll just need some time to disassemble it because I think I've put the volume buttons backwards, and it's stuck on the previous wrong image.17:37
nik90 elopio how do you remove the volume buttons in the first place ;)17:42
nik90s/do/did17:42
elopionik90: first, you have to break your screen.17:43
nik90lol17:43
elopioI'm not sure what's wrong with my buttons, but it's now flahsing.17:49
elopiosil2100: image #97, is that right?17:49
sil2100hmmmm17:49
sil2100elopio: I think yes17:50
pmcgowansil2100, have we opened up landings yet?17:53
pmcgowanor is that pending 11517:53
bzoltanelopio:  correct, UITK release is not scheduled for today. My last tests are stil running anyway17:56
ogra_pmcgowan, we need to see that 115 at least boots17:57
pmcgowanogra_, I can update if you promise it does17:57
ogra_cant promise that ... rsalveti can :)17:58
kenvandineit boots on my krillin :)17:58
jhodappsil2100, I'd like to land rtm silo 16, can we do that yet?17:58
sil2100Once we get confirmation that 115 works, we open up the gates :)18:00
ogra_kenvandine, lol, how did you make the mako image boot on your krillin ?18:01
ogra_:)18:01
kenvandineogra_, i've got skillz :)18:02
ogra_LOL18:02
elopiofor now, it's just showing the google logo.18:04
elopiospinning ubuntu logo now...18:04
ogra_\o/18:04
elopioand the wizard18:05
ogra_thats enough ... :)18:05
ogra_right, session starts ... that was broken18:05
elopioand I fixed my volume buttons \o/18:06
elopiotomorrow I'll try to fix the roof myself.18:06
ogra_geez !18:07
kenvandine:)18:07
* ogra_ recommends buckets :)18:07
ogra_as a fallback18:07
kenvandineand towels18:07
ogra_towels ++18:08
elopio:)18:08
elopioI'll be prepared with a couple of band-aids.18:08
sil2100ogra_: I think this means we promote, right? :)18:20
sil2100ogra_: ...right? :)18:22
kenvandinesil2100, this is getting exciting!18:23
nik90sil2100, ogra_ : let's go :) ...18:25
* nik90 checks his phone for update18:25
* sil2100 looks at ogra_ 18:34
ogra_oops, sorry18:41
ogra_promotion running18:43
sil2100\o/18:43
sil2100Thank you everyone!18:43
kenvandinewoot18:44
kenvandineso landings are open?18:44
ogra_sil2100, did anyone check the emulator ?18:45
sil2100ugh18:45
sil2100No18:45
kenvandineoh my :-D18:45
=== sil2100 changed the topic of #ubuntu-ci-eng to: Need a silo? Ping train support: trainguards | Need help with something else? Ping vanguard: cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: robru broke 3 ribs
kenvandinewow... robru broke 3 ribs!18:46
ogra_yeah18:46
ogra_thats why he wont come :(18:46
kenvandinepoor robru!18:47
robrukenvandine: thanks. Zero stars, would not recommend18:50
cyphermoxyeah, dude, get better :)18:51
sil2100I go to the cinema now, be back later o/18:55
ogra_=== Image #5 promoted for mako (from 97) #4 for generic and generic_x86 (from 91) ===18:58
cwayneogra_: :D19:01
pmcgowanogra_, yay so are we landing again19:17
ricmmelopio: hey, have you actually confirmed this as breaking autopilot tests for UITK ?19:29
ricmmand by confirmed I mean tried the version after and before19:29
ricmmI thought the breakage was introduced with 15-rtm019:30
ricmmkgunn_: same question for you19:32
kenvandinehumm... how do we sync packages from rtm to utopic now?19:32
kenvandinewithout the ~rtm in the version?19:32
kenvandinerobru, ^^19:32
robrukenvandine: i don't think that's possible, the code was only ever written with utopic->rtm in mind. The default binary copy doesn't change versions.19:36
kenvandinei told it to rebuild19:36
kenvandineit now appends the ~rtm on rtm landings19:36
robrukenvandine: that is to say, I'm not aware of any code that will strip ~rtm from the version, only add it. sil2100 made some changes there recently19:37
dobeyrobru: oh, ouch! (just read about the ribs)19:38
ricmmbzoltan: are you there?19:39
robrudobey: thanks19:39
robrukenvandine: is it really a problem for the utopic version to say ~rtm in it? I think that's fine as it will indicate it's a sync from rtm19:39
kenvandinebfiller, have you synced anything from rtm to utopic since the ~rtm got added again?19:39
kenvandinei guess :)19:40
robrukenvandine: i recommend binary copies where possible, now that we super those19:40
robruSupport those19:40
ricmmkgunn_: elopio I'm only asking because the bug says that UITK tested ok with RTM 10619:42
ricmmwhich contains the MR you are pointing as culprit19:43
elopioricmm: bzoltan was doing the testing. And maybe kgunn_ got the wrong changelog. Next week we will have to dig deeper.19:45
ricmmI was trying to look at the uitk branches19:46
ricmmbut theres about 1000 of them, with staging and so on19:46
ricmmelopio: what branch exactly is failing and what landing does it refer to?19:46
ricmmI can maybe try it before monday19:46
ricmmif you are not going to19:46
rsalvetisil2100: ogra_: is mako ok again?19:48
rsalvetiwill flash19:48
bfillerkenvandine: there is a flag to disable that ~rtm thing I think19:50
bfillerkenvandine: or it might be disabled by default now19:50
kenvandineit was disabled by default19:50
kenvandinebut it just got switched again19:50
kenvandineand it says to get permission from the landing team to check it19:50
kenvandineso i'm just trying to get a feel for the best way to handle it now19:51
elopioricmm: I'm not going to work on it before next week.19:52
elopioricmm: here are the results by bzoltan: http://people.canonical.com/~bzoltan/UITK-AP-FAILURES-106-107/19:52
elopiohttps://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1381165 has a link to a list of failed MPs.19:52
ubot5Ubuntu bug 1381165 in Ubuntu UI Toolkit "A lot of AP tests randomly fail" [Critical,Confirmed]19:52
elopioI would say that bzoltan was running trunk. But I'm not sure about that.19:53
ogra_rsalveti, yeah20:55

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