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

imgbot=== trainguards: IMAGE 293 building (started: 20141020 02:05) ===02:04
imgbot=== trainguards: RTM IMAGE 118 building (started: 20141020 03:05) ===03:04
=== karni-eod is now known as karni
imgbot=== trainguards: IMAGE 293 DONE (finished: 20141020 03:55) ===03:54
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/293.changes ===03:54
imgbot=== trainguards: RTM IMAGE 118 DONE (finished: 20141020 04:20) ===04:19
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/118.changes ===04:19
ricmmbzoltan: so only 107+ ? 106 and 105 clean?12:08
ricmmbzoltan: basically just want to know if 105 is broken, and if 107 is broken for you then try to roll back to qtdeclarative5-qtmir-plugin to 0.4.3+14.10.20141013-0ubuntu112:09
bzoltanricmm:  yes, up until 106 it was OK and from 107 the UITK AP tests are broken12:10
ricmmok12:10
ricmmin that case its the desktop file reader changes12:10
bzoltanricmm:  I have not yet tried to roll back12:10
bzoltanricmm: do you know who yo talk for the fix?12:11
ricmmbzoltan: dandrader, gerry, kgunn12:12
ricmmbut first do confirm with a rollback of qtmir12:12
ricmmjust to make sure the pinpointed version is correct12:12
bzoltanricmm: OK, so it is 0.4.312:13
bzoltanricmm:  is it a trival downgrade?12:13
ricmmbzoltan: apt-get install qtdeclarative5-qtmir-plugin=0.4.3+14.10.20141013-0ubuntu112:14
bzoltanricmm: cool, thank you ... doing it right now12:15
Saviqdavmor2, bug #138327712:34
ubot5bug 1383277 in unity8 (Ubuntu) "Power dialog sometimes shown on resume" [Undecided,New] https://launchpad.net/bugs/138327712:34
popeyooh, i have been seeing that too12:35
Mirvbfiller: I published the rtm-002 now.12:35
bfillerMirv: thanks, would be great if we could respin a mako image with that12:36
Mirvbfiller: I'll ping og_ra when it has migrated to release pocket12:37
Mirvbfiller: I wonder if we should try to get it to utopic too? I'm not sure if those ubuntu-phone thread repliers are using rtm or utopic12:38
bfillerMirv: we should probably get it to ubuntu as well, I think the people were using rtm but we should to be safe12:39
popeySaviq: davmor2 bug 138327912:39
ubot5bug 1383279 in unity8 (Ubuntu) "power button events queued, should probably be dropped" [Undecided,New] https://launchpad.net/bugs/138327912:39
Saviqpopey, a12:39
Saviqh12:39
Saviqpopey, reassigned to u-s-c12:40
Mirvbfiller: ^ that 001 will have it, kicked build button.12:40
bfillerMirv: thanks12:46
bfillerMirv: could you create silos for line 56 and 57 when you have a chance?12:46
Mirvogra_: bill requested ^ above at least mako rtm image build, could you arrange it? the sim unlock problem seen on the mailing list would be now fixed.12:55
ogra_i cant do a Mako only build12:56
ogra_but i can indeed trigger an RTM image build12:56
Mirvogra_: yeah, that's what I thought. I guess that's important enough bug that it'd be nice to have a new image sooner.12:57
Mirvhmm, I guess sil2100 is still stuck somewhere in Frankfurt or so :(12:58
ogra_right, no issue with that12:58
ogra_yup, i just saw his mail ... i think his new filght is in 2-3h12:58
ogra_... "I'm stuck here until the flight at 17:00 UTC+2" ...12:59
ogra_even more12:59
Mirvhe didn't mail me, but I heard yesterday evening12:59
Mirvthat's terrible12:59
* ogra_ is on the right MLs :) 12:59
Mirvogra_: argh, not again... "aren't you on the xyz mailing list"13:00
ogra_obviously LH screwed up his re-booking13:00
MirvI wonder if I should be on some more lists..13:00
ogra_Mirv, thats the internal foundations list ... i was on that team and didnt unsubscribe when i changed :)13:00
Mirvhehe, right13:00
Saviqjdstrand, hey, could we get your feedback on bug #1383086 please (also, is there a project we could add a task for to request security feedback?)13:03
ubot5bug 1383086 in unity8 (Ubuntu) "rebooting defeats the screen lock timeout" [Undecided,New] https://launchpad.net/bugs/138308613:03
kenvandinedoes anyone know why some autopkgtests aren't running?13:37
kenvandinei have ubuntu-system-settings in proposed and excuses says there is a test running13:37
kenvandinebut it isn't... last run was a week ago13:37
pete-woodstrainguards: if I want to change my mind about the target of my landing (I want to do utopic, rather than rtm), what's the right way to do this?13:44
Mirvpete-woods: you tell the line number and we'll change it :)14:10
Mirvor I will, robru being at his home timezone and sil2100 stuck on Frankfurt airport...14:10
Mirvpete-woods: so, I'd free up the rtm silo and assign utopic one instead14:10
kenvandineMirv, do you know why we have a bunch of packages stuck in proposed?14:11
kenvandineMirv, excuses says "test running"14:11
kenvandinebut they aren't running :)14:12
Mirvkenvandine: in rtm or utopic?14:12
kenvandineutopic14:12
Mirvoh..14:12
kenvandinewe have packages stuck migrating since friday14:12
Mirvthe answer to your question is "no" (do I know). we should probably ping pitti or someone else.14:14
cjwatsonask on #ubuntu-release about such things.14:18
pete-woodsMirv: yes, that would be awesome :)14:19
=== renato is now known as Guest73089
popey[D/query balloons14:22
popeyoops14:22
SaviqMirv, could we please have a silo for line 42 then, cleaned the utopic-targeted silo ↑14:36
brendandmarcustomlinson, hey14:57
marcustomlinsonbrendand: hey14:58
brendandmarcustomlinson, can we sit for a few minutes and look at your silo?14:58
marcustomlinsonbrendand: yeah ok14:58
brendandmarcustomlinson, dallas right?14:58
marcustomlinsonbrendand: yep14:58
SaviqMirv, http://www.markshuttleworth.com/archives/142515:01
AlbertAtrainguards: line 28 (rtm landing-001) is ready for QA but it's not showing up in the trello queue any ideas?15:02
Mirvpete-woods: the line number, please? :)15:13
MirvSaviq: on time, great!!15:14
Mirvcjwatson: is vivid open yet? ;)15:14
pete-woodsMirv: line 6215:14
Mirvpete-woods: oh right it didn't even have an assigned silo. ok then, 016.15:15
pete-woodsMirv: sorry, that's a new line. the original one is 4915:18
Mirvpete-woods: thanks, freed the silo15:19
Mirv(the line 49)15:20
bzoltanogra_: sir, where are you?15:20
MirvSaviq: rtm-01515:20
ogra_bzoltan, hmm, i thinnk its is called ballromm B15:20
cjwatsonMirv: no :)15:21
popeydavmor2: bug 138334315:24
ubot5bug 1383343 in unity8 (Ubuntu) "Application icons take a long time to load on slow network" [Undecided,New] https://launchpad.net/bugs/138334315:24
popeydunno if we have one already filed for that, seems we should15:24
davmor2popey: confirmed15:26
popeydavmor2: ta15:33
=== Guest73089 is now known as renatu
brendandbzoltan, silo 13 isn't going to land this week you know16:25
=== mihir_ is now known as mihir
=== chihchun is now known as chihchun_afk
robruMirv: are you at the sprint?17:10
robruI'm around for any landing needs anybody might have17:12
rsalvetidavmor2: I got a silo that's ready for qa to sign it off, but it seems the spreadsheet is not showing that17:32
rsalvetirtm silo 1417:32
rsalvetiSaviq: hey, we want to land https://code.launchpad.net/~mfrey/unity8/lock-fix/+merge/23891817:45
=== chihchun_afk is now known as chihchun
rsalvetiSaviq: don't think we're landing more stuff into utopic anymore, so how to proceed with that landing?17:45
Saviqrsalveti, I'm releasing trunk into rtm17:45
Saviqrsalveti, I've a silo already, will take that in17:45
rsalvetiSaviq: awesome17:46
robrursalveti: fixed spreadsheet status of row 4817:47
rsalvetirobru: thanks!17:47
robruthere it is ;-) you're welcome!17:48
brendandAlbertA, which bug is silo 17 meant to fix?17:48
brendandAlbertA, i don't see one mentioned in the changelog17:48
AlbertAbrendand: https://bugs.launchpad.net/media-hub/+bug/137831117:49
ubot5Ubuntu bug 1378311 in qtubuntu-media "EndOfStream event not received when QML Video component is destroyed" [Critical,New]17:49
brendandAlbertA, that's not going to land this week though17:50
AlbertAbrendand: I believe it was indirectly associated with a bug that was tagged 10-2318:00
AlbertAbrendand: but let me check...18:00
Mirvrobru: yes!18:07
robruMirv: mmmm, how was the flight? /me is super jealous i didn't get to go18:07
Mirvrobru: yes, it's nice to have you around, since I'm walking around so much that my response time can vary.18:08
Mirvrobru: 1h late (+1.5h US customs queueing), but not too bad especially given how Lukasz is doing.18:08
MirvI was here at 10pm, which was ok.18:08
robruyeah I saw lukasz' email, that's just brutal18:09
ogra_something he cal tell his kids about :)18:11
ogra_*can18:11
brendandbzoltan, ping18:12
brendandogra_, what happened?18:12
ogra_brendand,18:13
ogra_oops18:13
ogra_brendand, his original flight was overbooked and they screwed up the new booking18:13
ogra_he should be in the air now (finally)18:13
robruogra_: landings are open, right? I can publish that? ^18:16
ogra_robru, i donkt think landings are open, no18:17
robruhm, rsalveti published himself ;-)18:17
ogra_but thats the sim lock fix, that has been discussed before ...18:17
rsalvetiyeah18:18
ogra_(talking about rtm-008 and rtm-006)18:18
ogra_not sure about the mess rsalveti made with rtm-00218:18
ogra_:P18:18
ogra_:)18:18
rsalvetiit is ricmm's fault18:18
ogra_as usual !!18:18
ogra_robru, we actually planned to build an image once the 006 and 008 packages landed commpletely18:19
robruogra_: 6 and 8 aren't even started to publish yet, are they being reviewed still?18:20
ogra_hmm, dunno, i thought Mirv had handled them this morning already18:20
ogra_though i'm not sure if anything is allowed to land without QA signing off ... brendand ^^ ?18:21
robruogra_: unless they landed already and there's already two new landings in those silos? ;-)18:21
ogra_magically with the same packages ? :)18:22
Mirvogra_: didn't sil write on Friday "This also means we will be unblocking landings through the CI Train now."?18:22
brendandogra_, no18:22
Mirvogra_: yes I published the mako sim unlock silo18:22
ogra_Mirv, well, i think olli still only wanted landings for the critical bugfixes18:22
robruyeah I read something about how landings were unblocked but since it's final freeze it's basically only critical fixes anyway18:22
ogra_Mirv, and i think every landing needs QA signoff at this point in the release18:22
olliMirv, ogra_ is right18:23
ollii.e. if on the list, good to land18:23
Mirvogra_: yes, only rtm14 critical of course18:23
olliif not, then escalation to product team18:23
ogra_olli, modulo QA signoff indeed :)18:23
ollifor exception18:23
ogra_sine we want to keep brendand and davmor2 busy ;)18:23
Mirvboth today's fixes so far were for 2014-10-23 critical ones18:23
ogra_*since18:23
Mirvogra_: right, so QA signoff simply to every landing..18:24
ogra_yeah18:24
Mirvricmm: that means I'm changing your "turn off backlight" silo to also requiring signoff18:24
ogra_Qa might decide the landing is trivial enough to just let it through, but we should get their comment at least18:24
Mirvand ken's system-settings and pete-woods's silo18:24
ogra_Mirv, a bit late :P18:24
Mirvoh...18:25
ogra_(given it is already migrating)18:25
ricmm:)18:25
Mirvright :)18:25
olliMirv, checking the tags only is not sufficient18:25
ollias anyone can set the tags and sometimes they get set by accident18:25
Mirvand Saviq's unity8 landing18:26
ollithe list from my mail is the authoritive source18:26
ogra_well, only landing team should set them ... (though indeed everyone can set them, the landing team simply needs to check twice)18:26
Mirvolli: right.. so the 10/16 email. check.18:26
olliMirv, 10/23 ;)18:27
Mirvolli: yes, 10/23 email sent on 10/16 :)18:27
ollihah18:27
olliI can see now how this gets confusing18:27
MirvSaviq: so, I can immediately see your unity8 landing has bugs listed not on the List, so they should be escalated if wanted in18:28
rsalvetibut we're not just accepting MRs for the bugs from that email18:30
rsalvetiafaik we're back in the game and landing criticals18:30
rsalvetieven if not for this deadline18:30
davmor2ogra_: I'm so going to slap you into the middle of next month18:31
Mirvrsalveti: reading olli above it sounds like only bugs from the e-mail, or would need contacting the product team18:31
rsalvetidoesn't make sense, we had that for one week only, for the purpose of that milestone18:31
rsalvetiolli: isn't that the case?18:31
ogra_rsalveti, as i understood we only land what has been approved by olli, pmcgowan or vicotr ... and then only after QA signed it off18:32
rsalvetias we're fixing the other critical bugs, and we want to land them18:32
rsalvetiogra_: I thought that was only for the previous milestone18:32
ollirsalveti, only what's on the list for 10/2318:32
ogra_(heh, vicotr ... victors evil russian brother)18:32
rsalvetiolli: why that?18:32
rsalvetiwhy did we decide to push the same requirements for 23?18:32
ollirsalveti, ideally, we shouldn't fix bugs that aren't on the list, unless the list is wrong or there is a good opportunity18:33
rsalvetiolli: well, we have people enough to fix some other criticals18:33
rsalvetisame that happened last week18:33
ogra_rsalveti, the bugs simply need to be sent to either of these three and be added to the list18:33
Mirvyes, that's what Saviq said too, they have more people than bugs on the list18:33
rsalvetiwe're just flushing them now18:33
rsalvetiogra_: right, I don't understand why we need that18:33
Mirvit does make sense to fix later critical bugs earlier18:33
rsalvetiwe have the rtm14 bug list18:33
rsalvetiexactly18:33
ollirsalveti, the intention is to reduce churn & regression risk18:33
rsalvetiif it's on the rtm14 critical list, let's land it18:34
ogra_rsalveti, because they want to asses the risk for their product18:34
rsalvetiolli: but them we'll never fix every bug18:34
rsalvetiit's just a waste of time18:34
rsalvetiwe should land every critical we have now18:34
rsalvetias before18:34
rsalvetianytime18:34
nik90olli: is the rtm14 critical list public? Since I need to check if some alarm bugs are on that list which would affect user experience.18:34
rsalvetiwe can't land on utopic, can't land criticals out of that list18:34
* ogra_ doesnt care either way, i just know what was requested18:34
rsalvetiwill just take vacations18:34
ogra_in any case everything going into RTM needs QA signoff ... regardless of the list18:35
Mirvnik90: https://bugs.launchpad.net/bugs/+bugs?field.tag=rtm1418:35
ollirsalveti, let's chat in the break18:35
rsalvetiolli: sure18:35
ollirsalveti, vacation or improve test coverage or ...18:35
rsalvetibut I'm in favor of always landing critical fixes, sooner the better18:35
ogra_olli, there are a good bunch of bugs that wont affect krillin but mako ... which we definitely want tto have fixed18:35
ollirsalveti, I'd be with you if the overall number of bugs would go down18:36
nik90Mirv: and If I need to request a bug to be on that list, do I ask olli and victorp?18:36
rsalvetiolli: but that's because we still have bugs18:36
rsalvetiignoring that is just ignoring the reality that we have more bugs18:36
Mirvnik90: so basically any bug that both has the tag "rtm14" and is Critical. then we have an these "touch-2014-10-23" milestones additionally, and this List we're talking about is about those subsets of the whole list18:36
rsalvetithe bug number will still increase for a while18:36
rsalvetiuntil it's stable18:36
rsalvetiwe now have way more people using the product18:36
rsalvetiexpect more bugs18:36
nik90Mirv: ok18:36
Mirvogra_: what was the policy on adding 'rtm14' tag itself?18:37
ogra_uh, i forgot18:37
bzoltanbrendand: pong18:37
Mirvyeah, me too :P18:37
ogra_heh18:37
ogra_sil might know18:37
rsalvetiI just think we'll never ship if we keep this process as is18:37
rsalvetibut anyway, will complain in the corridor18:38
olli:)18:38
Mirvnik90: well, for now contact me or sil2100 when you've a bug that is critical (that part you can set yourself in your own projects) and that would also like to have the 'rtm14' tag.18:38
bzoltanbrendand:  Is it because of the UITK or is there a generic freeze?18:38
nik90Mirv: ack18:38
olliMirv, rtm14 is for you to express that this is relevant for the product18:38
rsalvetiwe're only landing ones that already has a deadline, just not for 2318:38
Mirvnik90: ^ ok there you go, you can add rtm14 for your own project when you think it should be in the radar as a critical bug18:38
Mirvolli: thanks.18:39
bzoltanelopio:  the AP failures are same with the   qtdeclarative5-qtmir-plugin:armhf                    0.4.4+14.10.20141013-0ubuntu118:39
rsalvetipostponing something that was originally for 30 just because we can't include it for 23 makes no sense18:39
rsalvetimade sense last week because of the reason of the deadline18:39
pmcgowanrsalveti, you can, if its rtm and crit18:39
rsalvetipmcgowan: olli said I can only land stuff on the 23 list18:40
pmcgowanok go yell at him then :)18:40
elopiobzoltan: do you mean, the same +70 errors?18:40
MirvI think that was the plan :)18:40
rsalvetipmcgowan: that's what I'm doing here18:40
rsalveti:-)18:40
ollipmcgowan, hey...18:40
brendandbzoltan, the landings are restricted to ollis list18:41
bzoltanelopio:  yes18:41
pmcgowanheh olli's list18:41
bzoltanelopio:  I have flashed the 118 image and downgraded that package.18:41
bzoltanbrendand:  Well, obviously  I am not happy for it. But can not do much I guess. I hope that the V queue will soon open and I can start landing there.18:44
ogra_Mirv, so what about the SIM lock stuff ? i cant see it on the dashbaodr19:20
ogra_wow, what a typo19:20
ogra_Mirv, i would actually like to trigger an image build ( rsalveti wants one too) ... but i cant seem to find the SIM lock issue landing anywhere19:21
ogra_ah, found it ... line 39 ... and it actually landed19:23
* ogra_ triggers a build 19:23
ogra_imgbot, stunt19:23
* imgbot rolls on its back and purrs19:23
ogra_good :)19:23
ollilol19:24
cjwatsonbzoltan1: Friday, hopefully19:25
bzoltan1cjwatson:  Friday is good, thanks19:26
cjwatsonnot promising but we've managed to be up and running within a day of release before ...19:26
bzoltan1sure, I totally understand19:27
imgbot=== trainguards: RTM IMAGE 119 building (started: 20141020 19:30) ===19:29
Mirvogra_: yes, thanks!19:32
SaviqMirv, there actually *is* a DO_NOT_ADD_RTM option ;)19:33
MirvSaviq: oh, right, it is there!19:34
ogra_WHY_DO_ALL_OPTIONS_SCREAM ?19:34
Saviqogra_, BECAUSE_THEYRE_IMPORTANT19:34
ogra_AH_THAT_MAKES_SENSE_THEN19:35
robrubzoltan: row 70 is missing something20:27
Mirvrobru: oops :) I added it20:27
Mirvwe're rapidly trying to get the MR in there. sorry for setting it as "Ready"20:28
Mirvthe battle for working wifi20:28
robruMirv: heh, no worries.20:31
bzoltanrobru: Mirv: ready :)20:32
robrubzoltan: Mirv utopic 1420:33
Mirvbzoltan: building https://ci-train.ubuntu.com/job/ubuntu-landing-014-1-build/81/console20:37
Mirvzbenjamin: conflicts20:38
imgbot=== trainguards: RTM IMAGE 119 DONE (finished: 20141020 20:40) ===20:39
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/119.changes ===20:39
ogra_wow20:39
robrupete-woods: ^ I'm afraid to publish anything as I've been out for 2 weeks. what's up with silo 16?20:39
ogra_that was really fast !20:39
robruhm20:40
davmor2ogra_: that just means it didn't work and we now all have broken images right?20:40
ogra_davmor2, well, blame rsalveti :P20:40
davmor2rsalveti: it's all you fault!!!!20:41
kenvandinedavmor2, why can't it ever be your fault? :-p20:41
robruwtfqueuebot20:42
davmor2kenvandine: it is but most that I let stuff through that was broken by the devs :P20:42
Mirvoh, not again, the 1min repeat queuebot thing20:42
ogra_it *relly* wants to publish that :)20:42
ogra_*really20:42
kenvandinereally20:42
robrubut but!20:42
robruI remember the cause of that issue and the spreadsheet doesn't look like it has that problem right now!20:42
Mirvit became fun when it was repeating three different landings every minute20:42
pete-woodsrobru: I think it's ready (I mean I've tested it). but I don't know the rules about publishing..20:44
robrupete-woods: is it a critical bugfix? utopic is in final freeze ;-)20:44
pete-woodsrobru: it is, yes20:45
robrupete-woods: ok20:45
ricmm:)20:46
ricmms'il vous plait20:46
robruricmm: rtm 220:47
ricmmrobru: thanks20:47
robruricmm: you're welcome20:47
davmor2ogra_, rsalveti: why is this image never seeming to finish flashing?20:57
davmor2ogra_, rsalveti: nevermind it just finished but my god that took a while :)20:58
rsalvetidavmor2: hahah20:58
rsalvetiI might be able to flash it tomorrow, will take a while to download it20:58
rsalvetireally slow20:58
cwaynedavmor2, got time for a custom tarball test tomorrow?  only critical bug fixes I swear :)21:00
robrusomebody who knows stuff let me know if it's actually ok to publish silo rtm 1421:00
davmor2cwayne: Where's my fitbit damn you ?  possibly depends when21:00
robruor not21:00
Mirvrobru: yes, I just published it. so it is on the 10/23 List (on the mailing list), ie ok.21:01
robruah ok, thanks Mirv21:01
Mirv"10/23 iteration planning"21:01
cwaynedavmor2, its in my room21:01
cwaynei dont have a charger for it though :/ but i do have the dongle to sync it21:02
balloonsogra_, https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/138347921:05
ubot5Ubuntu bug 1383479 in ubuntu-touch-meta (Ubuntu) "Remove autopilot from touch images" [Undecided,New]21:05
ogra_olli, pmcgowan ^^^ we need to talk about this one21:05
olliogra_, ack, not sure I fully grasp the implications21:08
pmcgowanogra_, yeah, this week or next?21:19
pmcgowanballoons, ^^?21:21
pmcgowanogra_, balloons although if it has a small footprint I suppose there is not so much urgency?21:26
ogra_pmcgowan, it has a giant dependency chain21:33
ogra_(it will remove quite a bit of python packages)21:33
pmcgowanthat sounds good21:33
pmcgowanso we should do next two weeks21:34
ogra_pmcgowan, but there is some risk in it, if people dont use out tools for testing but directly call autopilot for example21:34
ogra_so we should do it early to asess possible fallout21:34
pmcgowanogra_, who might do that?21:34
pmcgowanok21:34
ogra_pmcgowan, well, i know that the unity8 team calls AP directly during developemnt21:34
ogra_(eaiser than always calling pahblet-test-run if you develop )21:35
pmcgowanogra_, so maybe an email to the list to prep folks21:35
balloonspmcgowan, thanks for commenting on it. Sorry, I was offline and missed the discussion21:54
balloonsogra_, pmcgowan, the potential issues also arise from people depending on autopilot or a dependency without declaring it. It's unlikely but possible21:54
=== chihchun is now known as chihchun_afk

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