/srv/irclogs.ubuntu.com/2015/02/18/#ubuntu-ci-eng.txt

imgbot=== IMAGE 103 building (started: 20150218-02:05) ===02:05
imgbot=== IMAGE RTM 239 building (started: 20150218-03:05) ===03:05
imgbot=== IMAGE 103 DONE (finished: 20150218-03:30) ===03:30
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/103.changes ===03:30
tedgtrainguards, Can I get a silo for line 51?03:40
robrutedg: ha! you just caught me on the way out for dinner. silo 11.03:41
tedgrobru, Awesome, thanks! :-)03:43
robrutedg: you're welcome03:45
imgbot=== IMAGE RTM 239 DONE (finished: 20150218-04:20) ===04:20
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/239.changes ===04:20
ToyKeeperHmm, that answers that question.04:23
Mirvmorning05:41
Mirvhmm, wtf happened to my qtdeclarative line on spreadsheet, and how does it seem bzoltan's line 40 has kind of assimilated it05:47
Mirvbzoltan_: could you look at line 40 and and least make it like you'd like it to be? the MP is about phablet-tools, yet the bug is about qtdeclarative and it has qtdeclarative as manually uploaded package05:49
bzoltan_Mirv:  geez... not again a CI sheet conflict05:49
Mirvbzoltan_: I haven't seen that, but is it something like not everything is shown to everyone, then they add a line, and they somehow get mixed up?05:51
MirvI can see sil2100 "reconfigured" my silo adding phablet-tools to it.. https://ci-train.ubuntu.com/job/prepare-silo/4142/console05:51
Mirvbut the bug link isn't from my line even05:51
Mirvyes it's qtdeclarative but not the bug my landing in silo 012 was supposed to be about :S05:51
bzoltan_Mirv:  I do not know. I deleted the crap05:52
bzoltan_Mirv:  I have not added those junk text there :)05:52
Mirvbzoltan_: this make me very trusting that the rest of the spreadsheet has not gone completely mixed :)05:53
Mirvbzoltan_: ok, you've your silo now reconfigured to have your actual landing, and I readded my own line05:54
robruMirv: bzoltan_ I've been seeing a lot of mixups like this lately, whenever it happens to you, please reload the sheet. Sometimes it goes away.05:55
Mirvrobru: it can't go away if a silo has already been reconfigured to have two landings mixed :)05:56
robruMirv: true05:56
Mirvgo Google!05:56
robruMirv: yeah i dunno how this is getting worse, replacing the spreadsheet is top priority05:57
oSoMoNogra_, hey, if/when you’re around, I need a packaging ack for https://ci-train.ubuntu.com/job/ubuntu-landing-025-2-publish/17/artifact/packaging_changes_webbrowser-app_0.23+15.04.20150217.1-0ubuntu1.diff06:52
oSoMoNtrainguards: good morning! I need a binary copy of oxide-qt 1.5.3-0ubuntu1 from https://launchpad.net/~phablet-team/+archive/ubuntu/ppa/+packages to silo 306:54
robruMirv: can you grab that? I'm afk06:55
Mirvrobru: sure06:58
MirvoSoMoN: sure06:58
* Mirv is very sure06:58
robruMirv: thanks ;-)06:58
MirvoSoMoN: I tried also on #ubuntu-devel but maybe we need ogra if no-one else volunteers06:58
MirvoSoMoN: we got it from mitya5707:01
=== oSoMoN_ is now known as oSoMoN
oSoMoNMirv, thanks!07:04
Mirvnow all I'd need is an archive admin to approve compiz-mate binary package addition, no luck yesterday or today so far07:04
bzoltan_Mirv:  was the rtm image 237 ditched or what?07:17
robruMirv: Hmmmmmmm silo 3 diff is empty, that's suspect.07:29
Mirvbzoltan_: I'm not sure, you mean in terms of verification? I think signoffing and landing is still ongoing today.07:31
Mirvrobru: maybe because it needs to diff around 2.5GB against another 2.5GB, something runs out?07:31
Mirvrobru: luckily not disk space though :)07:32
robruMirv: I should hope that debdiff tool doesn't explode just because the filesize07:33
Mirvrobru: no, it's not that, I've debdiffed oxide locally just fine07:33
robruMirv: I'm poking at it now...07:33
robruMirv: oh I see... one sec07:35
* ToyKeeper wonders when bfiller gets up... probably not for several more hours07:38
robruToyKeeper: gets up? hah! he probably just went to bed recently. it's not even midnight us west coast07:39
ToyKeeperProbably need to confirm if a silo can land even though the bugfix has an unfortunate side effect.07:39
ToyKeeper(in rtm-017, one of the bug fixes eliminates an accidental feature which allowed it to produce higher-quality photos)07:39
robruMirv: oh btw, what I told you before about needing FORCE_REBUILD and WATCH_ONLY to regenerate diffs is no longer true. WATCH_ONLY now regenerates diffs by itself, that seemed more sensible to me.07:41
Mirvrobru: right, that's great!07:44
MirvToyKeeper: the usual default is indeed that flash is used for focusing if when flash itself is turned off07:44
ToyKeeperMirv: But it no longer uses the flash for focusing after applying this bugfix.07:45
MirvToyKeeper: yes, I just mean that indeed that's wrong, the default should be flash used for focusing even if there wouldn't be a setting for controlling it07:46
Mirvor well, I have seen also phones that do this same thing.07:47
ToyKeeperAh, okay.  So it sounds like this is less a grey matter and more of a fail.07:47
Mirvyes it's a rather grey matter. some people prefer that they can actually make the phone not to use the flash (for example it's banned to use flash in museums)07:47
ToyKeeperOh, it definitely is better to have the option rather than letting the phone be too smart for its own good.  :)07:48
ToyKeeperBut I feel that way about pretty much any attempt at software being clever.07:49
bzoltan_Mirv:  I mean that the RTM #237 is not listed here -> http://people.canonical.com/~ogra/touch-image-stats/rtm/ But it was the latest proposed when I validated the UITK landing... and it brought a broken gallery what made my testing invalid. Not nice ...07:56
robruMirv: hah: https://ci-train.ubuntu.com/job/ubuntu-landing-003-1-build/lastSuccessfulBuild/artifact/full_oxide-qt.diff/*view*/ 366MB diff, got it working at least.08:01
Mirvrobru: now we just need to review it properly!08:08
Mirvbut yes, working = good08:08
robruMirv: good luck ;-)08:08
Mirvbzoltan_: that's probably just ogra's scripts not running or something, as it's missing 237+23808:09
ogra_well, there were most likely device tarball or custom tarball changes ... if there are no rootfs changes -> no changelog08:09
Mirvoh right, there were those08:10
seb128is anyone looking at u1 accounts being lost on rtm > 234 updates?08:10
ogra_seb128, it is most likely due to the server wanting to refresh the token ...08:10
ogra_your token gets invalid on the phone when that happens08:11
ogra_we need better user feedback for this08:11
seb128why is that happening only after an update?08:11
seb128ogra_, dbarth is saying something else on -touch08:12
ogra_dunno ... before the old account stayed around and people were wondering why app updates stopped workin08:12
seb128<dbarth> seb128: apparently because the apparmor extension is missing, and the u1 lib now expects it to be there08:12
ogra_how could that lib land without this in place ?08:12
ogra_this needs to be a dependency then08:13
seb128https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1392380/comments/1708:14
ubot5Launchpad bug 1392380 in signon (Ubuntu RTM) "OA gives out all tokens to any app" [Undecided,In progress]08:14
seb128so yeah08:14
seb128bug, not token from server issue08:14
bzoltan_ogra_: Mirv:  anyhow, there must be a gallery app change between 236-237 what introduced failing tests08:15
ogra_seb128, well, 239 has the fix then08:16
seb128my u1 account is not back though08:17
seb128dbarth, ^ do we need to add the account again anyway?08:18
bzoltan_ogra_: Mirv: can you guys confirm this gallery change?08:20
ogra_bzoltan_, i can confirm that no rootfs changes happened :)08:21
ogra_nothing else08:21
Mirvbzoltan_: ogra_: no, gallery is 2.9.1.1136 from end of January08:21
bzoltan_ogra_:  so you say that the 236 and 237 are identical? Because I did capture a gallery test regressions.08:22
ogra_no, i say that the rootfs hasnt changed08:22
ogra_iirc 237 had some fixed for factory mode or so ...08:22
ogra_*fixes08:23
ogra_in the device tarball08:23
ogra_and 238 was a new custom tarball ... no idea what changed there08:23
bzoltan_Mirv: Ok, the gallery did not change. What about the gallery tests?08:24
Mirvbzoltan_: the RTM branch of gallery is untouched08:24
Mirvbzoltan_: but, maybe the phablet-click-test-setup checks out trunk instead?08:25
bzoltan_Mirv:  something caused the gallery test failures from 236 to 23708:25
Mirvbzoltan_: oSoMoN fixed gallery-app test failures in _trunk_ 19 hours ago https://code.launchpad.net/~phablet-team/gallery-app/trunk08:25
Mirvif phablet-click-test-setup checks out trunk AP:s instead of rtm AP:s, that would explain it08:25
bzoltan_Mirv:  Yeps... that was it. 19 hours ... that is exactly between my reference  and silo testing08:26
Mirvbzoltan_: so it's not tests failing, it's wrong tests08:26
Mirvbzoltan_: but nothing in rootfs really changed in 237 and 23808:27
bzoltan_Mirv:  Clear.08:27
=== sil2100 changed the topic of #ubuntu-ci-eng to: Need a silo or CI Train support? ping trainguards | Need help with something else? ping cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: ubuntu-rtm landing gates now closed
bzoltan_brendand: jibel: Guys, I have marked the silo1 tested and pasted the test results to the usual cell in the sheet. The silo validation for UITK takes ages, like 12-14 hours a round. You do not need to run the test plan. All the tests are done. If you have questions please ping me _and_ kalikiana. I hope that this UITK fix can make it to the the w9 freeze.08:41
Mirvbzoltan_: we'll have a hangout in 45mins, after that we'll know more08:43
bzoltan_Mirv:  Cool :) please push the UITK :)08:44
jibelbzoltan_, that'll be short for this milestone. There are still huge updates in the queue, like calendar and camera08:45
jibelbzoltan_, but we'll do our best08:45
bzoltan_jibel: it is up to you guys. The cursors issue this UITK fixes seemed to be rather important08:49
seb128dbarth, so, should I add back my u1 account manually, or keep it in that state in case somebody wants to fix it and need a system to verify the fix on?08:49
brendandMirv, any idea why QLibrary.load() would fail?08:56
brendandMirv, the error looks like this - http://pastebin.ubuntu.com/10287481/08:58
Mirvbrendand: at least out of context that doesn't tell me anything.. it'd sound like it doesn't find a library or something?09:00
brendandMirv, yeah. i'm not really sure where it looks09:01
brendandMirv, the location is on both QT_PLUGIN_PATH and LD_LIBRARY_PATH09:02
dbarthseb128: you can add it back, we have a way to reproduce in a bug report09:15
seb128dbarth, thanks09:15
dbarthseb128: mardy is looking into this right now09:15
seb128great09:15
popeysil2100: jibel if we add calendar to dashboard, won't that need calendar to already be in the image?09:52
sil2100seb128: hey! Do you know if there's any progress made on the failing ubuntu-system-settings AP tests?09:52
davmor2popey: it will be in the next image unless things go very wrong09:52
jibelpopey, it should be on next image09:53
popeyok09:53
sil2100popey: as they mentioned, it should be in the next image so we should be safe to add it now09:53
popeyok09:53
jibeland if it is not and it fails, we'll know why :)09:53
popeyhah09:53
seb128sil2100, no, we have no clue what's the issue, we can't reproduce on devices and the issue on the ci run seems in qtfeedback09:53
sil2100seb128: the changes that are causing almost all tests to fail also landed on ubuntu-rtm yesterday and we would need those fixed before we can get an image promoted09:53
seb128that's what I understood from what Ken said the other day09:53
sil2100oh09:53
popeycihelp Hello! Can we please get calendar app autopilot tests added to the dashboards? (it was removed a while ago, but we're adding it back to the image)09:54
bzoltan_sil2100: jibel: I saw that we have time until 2pm UTC. Who to bribe to pull the UITK up in prioroty? It has a fix what effect _ALL_ text input in _ALL_ apps.10:08
sil2100bzoltan_: no worries, QA will sign-off your silo after silo 11 and calendar10:08
bzoltan_sil2100:  Okey...now all I need is an IBAN number and a sum :D10:09
=== iahmad__ is now known as iahmad
jibelsil2100, +1 for gallery app10:32
sil2100\o/10:33
sil2100Publishing10:33
jibelsil2100, you upload to the store as well?10:35
sil2100jibel: and what about the qtdeclarative5-ubuntu-ui-extras0.2 package in the end?10:35
jibelsil2100, it is wrong in vivid too. You have a click app that depends on an external lib that is not part of the framework but added manually to the seed10:35
sil2100jibel: hm, but I don't see it in ubuntu-rtm right now - will we need to land the camera-app silo first?10:36
sil2100rmadison says it's only in vivid currently10:36
jibelsil2100, it's in 17, bfiller said "No because gallery-app click package does not need ui-extras0.2 yet and we are not installing the gallery-app deb which has this dependency"10:37
jibelsil2100, I don't quite understand why the click package wouldn't need this lib10:38
jibelsil2100, the lib is not embedded in the click package, so if it is not installed on the system it'll use the wrong version10:39
sil2100Ah, hm10:39
sil2100Ok10:39
jibelsil2100, I don't know what in gallery app uses this lib and if it detects which version is available at runtime10:39
jibelsil2100, I think it's safer to wait for silo 17 to land too10:40
sil2100Not sure what to do in this case, as even though the .deb packages are basically just dummy ones, but this will mean I'll push a broken-dep package to the archive10:40
sil2100jibel: yeah10:40
sil2100Ok, let's just wait then :)10:40
sil2100Thanks!10:40
jibelsil2100, but IMO this lib should be a dependency of an ubuntu-sdk-lib-extras which would be a suggest of ubuntu-sdk-lib and -extras would be added to the seed. and if the version of the lib changes you bump the version of the framework10:41
jibelsil2100, probably cleaner than adding that lib manually to the seed. You cannot even track which click package depends on it, and that'll probably break stuff next time it's updated to a major version10:43
=== vrruiz_ is now known as rvr
psivaa_popey: I've added your request to our 'To do' lane10:54
psivaa_Doing this should not take that long but it could be a little while for us to get there10:54
psivaa_s/there/to it10:54
popeythanks psivaa_10:54
psivaa_np10:54
=== dpm_ is now known as dpm
=== marcusto_ is now known as marcustomlinson
=== _salem is now known as salem_
jibelcihelp: on http://rtm-dashboard.ci.ubuntu.com/smokeng/utopic/touch_stable/krillin/239:20150218:20150216-fe747ac/332/ 3 tests are failing because system-settle failed (abook, dialer and calc) Where do I find info why it failed? There is not much info in top-before and top-after log files11:28
sil2100jibel: ogra_ had a nice script to parse it for useful information11:29
jibelogra_, ^ do you mind sharing your script?11:30
ogra_paste.ubuntu.com/10289122/11:30
ogra_i havent used it in ages, not sure it still works11:31
jibelogra_, I'll try, thanks!11:31
vilajibel: pas mieux11:32
jibelsil2100, ogra_ I don't see anything interesting in topafter but it's likely the scoperunner crash that generated the load11:34
jibeldavmor2, did you notice any crash while testing the custom tarball?11:35
davmor2jibel: nope11:36
sil2100I go prepare lunch11:42
rvrpopey: Calendar app: text: "W"+ root.startDay.weekNumber()11:45
rvrpopey: "W" must be localized11:45
rvrpopey: Also, pot file needs update, "All Day" is not available in Launchpad for translations.11:46
=== MacSlow is now known as MacSlow|lunch
Mirvsil2100: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-005-1-build/112/console ...12:24
Mirvsil2100: I once ran build with watch_only quite quickly after uploading the final version, now it's like that..12:24
sil2100huh?12:25
Mirvsil2100: I guess just another way CI Train may "save" some wrong information and not clear that out12:25
Mirvsil2100: note how it checks two versions of the same package12:25
sil2100Mirv: yeah, probably try doing a normal non-watch_only build12:26
sil2100But I guess it's a bug indeed12:26
sil2100watch_only should not use any saved state for source packages12:26
Mirvsil2100: normal build same problem it seems https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-005-1-build/113/console12:26
sil2100huh12:27
sil2100Ok, now that's broken then12:27
sil2100Let me take a look in-between frying12:27
=== alan_g is now known as alan_g|lunch
sil2100hm12:33
sil2100Mirv: from the CI Train side everything looks ok, I wonder what the new build job does12:34
Mirvsil2100: the old version is not even shown at https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-005/+delete-packages anymore12:35
popeyrvr: can you file a bug pls?12:37
Mirvsil2100: maybe it's still something that will sort itself by time, ie. the LP query will return different results at some point.12:38
rvrpopey: Yes, we can12:38
popeythanks12:39
rvrpopey: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/142316012:43
ubot5Launchpad bug 1423160 in Ubuntu Calendar App ""All day" and "W" (for week) not translatable" [Undecided,New]12:43
popeythanks rvr12:43
Mirvsil2100: ok, it still failed I now did _both_ prepare-silo reconfig + tagged force_rebuild of both packages (even though they are manual uploads and not MP:s). either of them finally cleared the wrong info out.12:57
sil2100Mirv: geh, ok...13:00
=== alan_g|lunch is now known as alan_g
boikotrainguards: question: the silo request on row 56 does not change existing code, just remove some toos that were not being used for quite some time on history-service, do I need to put QA signoff as Required still?13:18
sil2100boiko: I would say it shouldn't require sign-off, since the diff indeed looks sane13:28
sil2100boiko: but shouldn't you also remove history-service-tools from debian/control?13:28
boikosil2100: well, that's the thing: on vivid we added new tools, I just don't want to backport them right now13:28
sil2100boiko: ok, yeah, but in ubuntu-rtm it would mean that we'll have an empty package basically, right?13:40
sil2100Not a super bad thing though13:40
boikosil2100: yep, at least until we backport the new tools (they help testing, as they populate the history database, etc)13:41
pete-woodstrainguards: hi, could I get vivid silo 011 reconfigured please? thanks!13:54
Mirvpete-woods: sure13:56
sil2100pete-woods: done13:56
sil2100Mirv: ^13:56
Mirvsil2100: hehe :)13:57
Mirvpete-woods: and thanks for the fix already in advance!13:57
sil2100boiko: ok, assigned the silo, but QA might want to re-discuss the requirement of sign-off13:57
boikosil2100: that's fine, I was just trying to leverage their work :)13:58
bfillerjibel, sil2100: gallery-app click package does not depend on ui-extras0.2 yet so that is not needed technically14:00
bfillerit will need it in the future but doesn't right now14:00
pete-woodsMirv: well, importantly this won't be truly fixed until the apps are updated to stop doing their own translations for infographics (see MR for music-app https://code.launchpad.net/~unity-team/music-app/infographics-translations/+merge/248251)14:00
bfillersil2100: kenvandine can ack the packaging changes in silo 18, he's aware of the situation14:02
kenvandinehey bfiller14:02
sil2100bfiller: ok... if a core-dev acks that then it's fine, but basically right now the deb will be uninstallable on ubuntu-rtm14:02
sil2100I know we don't use the .deb basically14:02
kenvandinesil2100, have you seen anything like this?  http://pastebin.ubuntu.com/10290989/14:02
sil2100But if something lands in the archive it should have archive-sufficient quality14:03
=== MacSlow|lunch is now known as MacSlow
bfillersil2100: yes that is true, but we don't use the deb at all. it's only there for convergence to install on desktop14:03
sil2100bfiller: I'll let kenvandine as the core-dev to decide ;)14:03
bfillersil2100: so lets sync ui-extras then from vivid at the same time14:03
sil2100bfiller: yeah, it's in another silo which seems to have some problems currently14:03
sil2100Otherwise I would just sign-off and land both14:04
bfillersil2100: we can move that into it's own silo so it can land independently14:04
sil2100bfiller: no worries, let's wait a bit on how things resolve and decide then if we need to hack around it14:04
kenvandinesil2100,  i'm fine acking that for rtm14:04
kenvandinewe aren't running desktops from rtm anyway14:05
bfillersil2100, kenvandine : ok thanks guys14:05
sil2100Ok then, let me publish it :)14:05
kenvandinethanks14:05
kenvandinesil2100, and look at that pastebin when you get a chance :)14:05
sil2100kenvandine: ok, looking now14:05
jibelbfiller, there is a fix for the camera, so it should land later today, and ui-extras0.2 too14:05
kenvandinethat's what we're getting from smoke tests14:05
kenvandinesil2100, which i've reproduced on my krillin running vivid locally14:06
sil2100kenvandine: hm, now that's something I never saw before14:06
kenvandinealso...14:06
sil2100kenvandine: it started happening after the u-s-s silo landed... was there anything risky in it?14:06
kenvandinethis started happening between image 96 and 9814:06
kenvandinewhich had a massive mir landing14:06
bfillerjibel: ok cool, thanks14:06
kenvandinesil2100, there was also a mir landing14:07
kenvandinethere was nothing risky in the silo14:07
kenvandinesil2100, in fact... the only change in that silo was adding some UI that is hidden14:07
sil2100kenvandine: but not in ubuntu-rtm - and we see the same failures in rtm with the latest image14:07
kenvandinewait... same thing in rtm?14:07
sil2100kenvandine: http://rtm-dashboard.ci.ubuntu.com/smokeng/utopic/touch_stable/krillin/239:20150218:20150216-fe747ac/332/ <- this is the latest result in rtm after landing of the u-s-s silo, no failures seen before this14:08
sil2100http://people.canonical.com/~lzemczak/landing-team/ubuntu-rtm/239.commitlog14:08
sil2100These are the changes14:08
kenvandinesil2100, so the same change landed in rtm, and the UI isn't hidden there14:08
sil2100This is why I started thinking that it's this landing that's responsible14:09
kenvandinesil2100, what image did it start happening in for rtm?14:09
sil2100WIth this one14:09
sil210023914:09
kenvandinethat is the latest right?14:09
sil2100http://rtm-dashboard.ci.ubuntu.com/smokeng/utopic/touch_stable/ <- all others have normal failure counts14:09
sil2100Yes :)14:09
kenvandinewell wtf@14:09
sil2100We would really like to have this resolved as it's blocking our promotion14:09
kenvandinesil2100, the change we landed in 239 also landed yesterday in vivid14:10
sil2100Since releasing OTA-1 with so many failures is really bad ;p14:10
kenvandinethis has been happening for over a week in vivid14:10
sil2100hmm14:10
sil2100Interesting14:10
bfillersil2100: I will push the gallery-app click to the store now, is that ok?14:10
kenvandinesil2100, and... the only change in the image that this was introduced in with vivid had landed in rtm a week before it landed in vivid14:11
seb128kenvandine, hey, getting anywhere with the u-s-s test issue?14:12
kenvandine #15 0xaf0763ce in QFeedbackHapticsEffect::QFeedbackHapticsEffect(QObject*) () from /usr/lib/arm-linux-gnueabihf/libQt5Feedback.so.514:12
kenvandinesame damn thing14:12
kenvandineseb128, that's what sil2100 and i are talking about14:13
kenvandineseb128, it just started happening in rtm smoke testing14:13
seb128kenvandine, weird14:13
kenvandinein image 23914:13
sil2100brb14:13
kenvandineseb128, and there are strange logs14:13
kenvandinehttp://pastebin.ubuntu.com/10290989/14:14
kenvandineseb128, ^^ thoughts?14:14
seb128kenvandine, not really, does it have to do with screencasting?14:14
seb128how is the screencasting working?14:15
kenvandineoh i wonder if that is what's causing that log14:15
kenvandinei don't know14:15
seb128can we enable it locally to see if we hit the same issue?14:15
kenvandinei have reproduced it locally14:16
kenvandineon my krillin with vivid14:16
kenvandineoh14:16
kenvandinethat can't be screencasting14:16
kenvandinei get that same log output locally14:16
seb128k14:16
kenvandine[1424235205.472568] <ERROR> mircommon: Caught exception at Mir/EGL driver boundary (in setSwapInterval): /build/buildd/mir-0.11.0+15.04.20150209.1/src/client/buffer_stream.cpp(283): Throw in function virtual void mir::client::BufferStream::request_and_wait_for_configure(MirSurfaceAttrib, int)14:16
kenvandineDynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt11logic_errorEEEE14:16
kenvandinethat part anyway14:17
seb128did mir change in rtm?!14:17
kenvandineseb128, and at the same time, there's a seg fault from uss that seems to be triggered by haptic feedback14:17
kenvandineseb128, i don't think so14:17
kenvandinenot in image 23914:17
seb128weird14:17
kenvandineseb128, but... there was a mir landing in the first vivid image that had this problem14:18
seb128doesn't explain why rtm get the same issue without a mir landing14:18
kenvandine qtdeclarative5-ubuntu-ui-toolkit-plugin changed in image 23614:18
kenvandineseb128, the good news is this crash really happens at the very beginning of the test14:20
kenvandineeverytime14:20
kenvandineand we aren't seeing this crash manually testing14:20
kenvandineso it must be something to do with the autopilot tests14:21
kenvandineand i've ruled out infrastructure by testing locally14:21
kenvandinei wonder if we're the only ones seeing this because we don't use upstart-app-launch14:22
kenvandineseb128, https://errors.ubuntu.com/problem/b4ceece27f0ccfe9753e940695015237461b390814:35
seb128kenvandine, not very useful, why isn't retracing working?14:35
bfillerpopey: can your review/ack new gallery I just uploaded to store?14:36
kenvandineseb128, that's what i was going to ask you :)14:36
seb128bdmurray, ^ can you help there?14:36
popeybfiller: done14:37
kenvandinealso... all 3 instances of it where run by autopilot14:38
kenvandineseb128, https://errors.ubuntu.com/problem/f1aceaefc06bcc522f22df201625eb2d111929fb14:39
kenvandinethat one has a retrace14:39
sil2100Publishing o/14:40
seb128kenvandine, right, who is working on the feedback plugin?14:40
kenvandinethat's from qt14:40
sil2100bfiller: anyway, can you please upload the new gallery-app to the store? :)14:41
kenvandineseb128, i'd think that would affect all kinds of stuff14:41
kenvandinewe don't do anything directly there14:41
kenvandinejust the uitk14:41
kenvandineseb128, i created bug 142320514:42
ubot5bug 1423205 in ubuntu-system-settings (Ubuntu) "/usr/bin/system-settings:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:core::dbus::Bus::Bus" [Undecided,New] https://launchpad.net/bugs/142320514:42
bfillersil2100: done, popey just approved it14:43
sil2100Excellent14:43
bfillersil2100: can I get a silo for line 58 on vivid, it's the camera-app fix need to land it in vivid first then will sync to rtm14:44
sil2100Sure, on it14:44
bfillerjibel: ^^^ the camera-app is fixed, just doing the vivid landing first then will update the rm silo14:44
bfillerrtm silo14:44
om26erkenvandine, Hi!14:46
om26erkenvandine, I am trying out silo 14. If the device does not discover the bluetooth name of the headset, it shows its MAC address, is it supposed to keep showing that until I connect to the headset ?14:47
kenvandineas long as it doesn't detect a name14:48
kenvandineit should14:48
jibelbfiller, OK, rhuddie ^ can you reverify the camera after silo 3?14:48
om26erkenvandine, how long does it take to detect the name generally ?14:48
kenvandineom26er, it might never14:48
jibelrhuddie, when it's in the silo of course :)14:48
kenvandinethat was part of the problem14:48
kenvandineit would display an empty name14:48
kenvandines/part//14:48
rhuddiejibel, sure. i just finished silo 3.14:49
om26erkenvandine, I think we need to add a testcase to the testplan for this bug fix.14:49
kenvandineom26er, so you have a device that doesn't get a name?14:49
bfillerrhuddie: I'll ping you soon when it's in the rtm silo14:49
om26erkenvandine, it showed its MAC address14:49
rhuddiebfiller, thanks.14:49
kenvandineom26er, to properly test this specific case, the tester needs a device that wouldn't show a name14:49
om26erhmmm, don't have that.14:50
kenvandineom26er, i don't have a device that doesn't show a name14:50
om26erkenvandine, let me clear there are three cases ? 1. where name is shown. 2. only MAC address, 3. No nothing and in that case we want to show "..." ?14:51
kenvandineom26er, for case 3 we want to show the address14:51
kenvandineom26er, it should only show the address when there is no name detected14:52
kenvandineom26er, i don't have any devices that don't show a name14:52
kenvandinefor example14:52
kenvandineom26er, so showing the address shouldn't be common, i'd hope14:53
om26erI tried it in my car it showed the MAC address, the name only appeared when I connected to it.14:53
kenvandineom26er, cool, i think that's what we want14:53
kenvandineom26er, but there are some devices that'll never get a name14:53
kenvandineso we'll keep showing the address14:54
kenvandineom26er, but to test that you need a device that doesn't get the name14:54
kenvandinenot sure we want to require everyone that tests this to have such a device14:54
om26erheh, I'll just approve it after some more testing.14:55
kenvandineom26er, thx... not sure how to test it14:56
kenvandinewe tested it for regressions14:56
kenvandinewell, pmcgowan did, not sure if he had a device that didn't detect the name or not14:56
kenvandinei tested it in vivid, all my devices still show the name14:57
pmcgowankenvandine, om26er  my device initially shows the address, then when connnected switches to the name14:58
kenvandinepmcgowan, and is that the same behavior as before?14:59
pmcgowankenvandine, before the field was blank the the first page, now it shows the address14:59
kenvandinepmcgowan, perfect!15:00
=== plars changed the topic of #ubuntu-ci-eng to: Need a silo or CI Train support? ping trainguards | Need help with something else? ping plars | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: ubuntu-rtm landing gates now closed
kenvandineso you have a device that reproduced the bug :)15:00
kenvandinepmcgowan, i tried everything in my house that has bluetooth... they all show a name before connecting15:00
pmcgowanyeah my headset showed the issue, whereas my car showed the name15:01
pmcgowanprobably a bt version thingy15:01
pmcgowansil2100, jibel  any chance we will get all the queued silos landed?15:02
sil2100pmcgowan: yes, although we might still be blocked on the failing autopilot tests for ubuntu-system-settings anyway15:03
sil2100pmcgowan: since currently we have almost all u-s-s tests failing15:03
om26erkenvandine, looking at the diff, previously if device was not paired you appended "..." now you are doing that for the opposite. Intentional ?15:03
jibelpmcgowan, all the critical fixes will land (9, 14, calendar and camera are under verification)15:03
sil2100kenvandine is looking into that15:03
sil2100pmcgowan: btw. did you hear anything about us not to include calendar-app?15:03
ogra_hmm15:04
* ogra_ wonders why rmadison gives him 503 errors15:04
jibelpmcgowan, we'll maybe have time to land silo 1, depending how it goes with silos under testing.15:04
pmcgowanjibel, silo 0 is also a customer report fix15:05
pmcgowanand silo 20 just looks like great fixes15:05
pmcgowanbut gotta stop sometime15:06
sil2100pmcgowan: but 0 doesn't seem to look ready15:06
jibelpmcgowan, but it is not ready for QA. last comment from rsalveti is "Not yet to be validated, WIP (had tested as yes by accident)."15:06
pmcgowanok15:06
rsalvetipmcgowan: jibel: yeah, we found one issue with silo 0, working on the fix15:06
rsalvetiso not completely ready yet15:06
kenvandineom26er, indeed that does look opposite... cyphermox ^^15:07
kenvandineom26er, good eye...15:07
pmcgowansil2100, I did not hear anything about calendar app15:08
sil2100pmcgowan: since I was wondering how to include it and cwayne mentioned something about Joe saying not to add it yet15:08
kenvandinecyphermox, before you only appended "..." if it wasn't paired, now you're only appending it if it is paired15:08
sil2100But I wonder what that means15:08
pmcgowanlet me check15:08
cyphermoxkenvandine: indeed, it's a logic error15:09
kenvandinecyphermox, can you fix that up quickly?15:09
pmcgowansil2100, last email I have on this joe just says keep him posted15:09
kenvandinewe really want to land that today15:09
kenvandineom26er, i'll rebuild that silo as soon as cyphermox fixes that15:10
kenvandineom26er, thanks for catching that!15:10
om26erkenvandine, ok sure ;-)15:10
cyphermoxkenvandine: pushed15:10
kenvandinecyphermox, thx!15:10
kenvandinecyphermox, i'll fix it for trunk15:11
cyphermoxk15:11
jibelpmcgowan, this is what we found with the calendar app so far: bug 1423185, bug 1423191, bug 1423209, bug 1362781, bug 134783615:11
ubot5bug 1423185 in Ubuntu Calendar App "Calendar app crash" [Undecided,Confirmed] https://launchpad.net/bugs/142318515:11
ubot5bug 1423191 in Ubuntu Calendar App "Spinner displayed above "No future events" in Agenda" [Undecided,Confirmed] https://launchpad.net/bugs/142319115:11
ubot5bug 1418992 in Ubuntu Calendar App "duplicate for #1423209 Calendar events slow to appear or never appear on app startup" [High,Confirmed] https://launchpad.net/bugs/141899215:11
ubot5bug 1362781 in qtorganizer5-eds (Ubuntu RTM) "After date recurrence end is not functioning." [High,In progress] https://launchpad.net/bugs/136278115:11
ubot5bug 1347836 in Ubuntu Calendar App "Events saved to birthdays calendar don't appear in timeline" [High,In progress] https://launchpad.net/bugs/134783615:11
cwaynepmcgowan: sil2100: just got a hard -1 on adding calendar15:11
pmcgowancwayne, ok15:11
sil2100cwayne: oh? What's up?15:11
pmcgowanall those bugs15:11
pmcgowanjibel, thanks15:11
sil2100jibel: thanks!15:12
jibelpmcgowan, I don't see it in the list but event syncs doesn't work reliably15:12
pmcgowanjibel, how so?15:13
jibelpmcgowan, someone in the team reported that this morning during our standup, I'll find the bug15:13
alan_gplars: Are there problems on mir-mediumtests-runner-mako? Just had this twice "Rebooting the phone will take approximately 30 seconds to settle/Build timed out (after 60 minutes). Marking the build as failed."15:16
plarsalan_g: not that I've heard of, but I'm just coming on. Can you point me at the job?15:16
alan_ghttps://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner-mako/4328/console (and 4389)15:17
cwaynesil2100: it's a bit too risky to add a new app this late in the game15:17
kenvandinecyphermox, mind an ack? https://code.launchpad.net/~ken-vandine/ubuntu-system-settings/address-not-name-rtm-logic-error/+merge/25015215:19
plarsalan_g: on a standup right now, give me just a bit and I'll take a look15:19
jibelbfiller, any ETA for the update of the camera app in RTM?15:19
alan_gplars: ok15:19
cyphermoxkenvandine: thar.15:19
kenvandinecyphermox, thx15:20
bfillerjibel: within 30 minutes, landing in vivid currently15:20
jibelbfiller, thanks15:20
bfillersil2100: mind publishing ubuntu silo 27 for camera-app15:29
om26erbzoltan_, Hi!15:30
om26erbzoltan_, I can't select text in unity' searchbar with silo1, the actionbox takes over the selector.15:31
om26ermore like the handlers hide15:32
jhodappsil2100, can I get a silo for line 59 please15:35
om26erkalikiana, ^15:37
bdmurrayseb128, kenvandine: this is the log file portition for the retrace attempt - https://pastebin.canonical.com/125821/15:40
bdmurraypitti might have more information about why retraces fail like that15:41
kenvandinebdmurray, thx for looking15:41
kenvandinei found a retrace15:41
seb128bdmurray, thanks15:42
bdmurraykenvandine: where?15:42
kenvandinehttps://errors.ubuntu.com/problem/f1aceaefc06bcc522f22df201625eb2d111929fb15:42
jhodappcyphermox, can I get a silo for line 59 please?15:44
cyphermoxjhodapp: sure15:45
jhodappcyphermox, looks like i jsut got on, thanks anyway15:45
jhodappsil2100, thanks man!15:45
bfillerrhuddie: here is the update click to test for silo 17: https://jenkins.qa.ubuntu.com/job/generic-click-builder-vivid-armhf/342/artifact/output/com.ubuntu.camera_3.0.0.514_armhf.click15:45
rhuddiebfiller, jibel, thanks. I'll start testing15:46
kenvandinesil2100,  you can rest easier... the always awesome jgdx has a fix for the smoke test failures!15:47
kenvandineand it's just in the autopilot tests15:47
kenvandinenothing wrong with settings itself15:47
sil2100Oh OOH!15:47
sil2100:D15:47
kenvandineit actually removes one test :/15:48
kenvandinebut that one test blows the entire suite15:48
kenvandinewe're not 100% sure why yet... but something to do with the session bus15:49
kenvandinesil2100, we're still investigating a proper fix that wouldn't make us remove that test15:52
sil2100jibel: ^15:54
sil2100kenvandine: what test needs removing to fix the suite?15:54
kenvandinesil2100, it's the ConnectivityMixin class that's causing the problems, which is needed by test_sim_unlock15:58
sil2100jibel: ^ do you it is acceptable to temporarily get rid of the test for this release to make all the other tests working again?15:59
kenvandinesil2100, jibel: and the problem with the test has nothing to do with a feature regression...15:59
kenvandineit's just problems with the session bus15:59
kenvandineand the uitk using the session bus to get the vibrate settings16:00
kenvandineom26er, silo 14 is built again16:01
om26erkenvandine, thanks, will test that in a bit16:01
kenvandine-            if (device->isPaired())16:01
kenvandine9+            if (!device->isPaired())16:01
kenvandineom26er, the only diff16:01
om26eryeah I saw that.16:01
kenvandineom26er, thx16:01
sil2100kenvandine: anyway, I'd like QA to decide if we can go with that, but seeing how things are going I suppose that's our only choice16:02
om26erkenvandine, approved.16:02
sil2100If we intend to get an image ready by the end of the UTC day16:02
kenvandineom26er, thx!16:02
sil2100kenvandine: ouch...16:06
sil2100kenvandine: I can't publish silo 14 as there was a release in the meantime16:06
sil2100So we might need to rebuild the silo ;/16:06
kenvandinewhat?16:06
kenvandinei just rebuilt it16:06
kenvandineoh16:06
kenvandinei already published it :)16:06
kenvandinesil2100, sorry... that broke you :)16:07
sil2100Ahah16:07
sil2100:D16:07
kenvandinesil2100, i'll prepare a silo dropping that test, in case we want to land that16:07
sil2100Right, I always forget you publish your own silos :D16:07
sil2100kenvandine: yes, please16:07
kgunnsil2100: hey so your mail, are you saying gate is closed even for things that were ready tues morning...but in the qa test queue ?16:08
bzoltan_om26er:  if you have any problems or question related to the silo1,  please feel free to reach out :)16:09
sil2100kgunn: the gates are closed for new things, but not all silos prepared before the deadline will make it as it depends on QA capabilities ;)16:09
om26erbzoltan_, I did already :)16:09
sil2100kgunn: the highest priority are silos with critical or factory fixes16:10
kgunngot it...16:10
sil2100Others will land if QA is able to sign-off16:10
om26erbzoltan_, I can't select text in unity' searchbar with silo1, the actionbox takes over the selector.16:10
kgunnours is under qa test atm16:10
om26erbzoltan_, http://i.imgur.com/xse3evb.png16:10
kenvandinesil2100, we're going to hold off proposing that for trunk though, so vivid smoke testing will remain broken for now16:12
kenvandinewhile we find a proper fix16:12
kenvandinethat way we don't forget to fix it :)16:12
jibelkenvandine, sil2100 do we know exactly why the tests are failing?16:13
sil2100kenvandine: hm, ok, makes sense, even though I think it would be best if this gets fixed ASAP anyway since for quality we need to make sure that all automated tests work as they should16:13
kenvandinesil2100, yes... jgdx is working on it now16:15
kenvandinejibel, a test in our security panel starts a session bus16:16
kenvandinejibel, but now the uitk is needing the session bus so it gets started already16:16
kenvandinewe're getting conflicting session buses16:16
kenvandinewe think16:16
kenvandinejibel, so removing that ConnectivityMixin class we have, prevents that from happening16:16
kenvandinejibel, once it blew up, everything after it fails16:17
kenvandinewe only need to remove it from the one test16:17
jibelkenvandine, OK, can you update the silo?16:17
kenvandinejibel, i just created a silo with it16:18
kenvandinejibel, we're leaving it broken in vivid for now16:18
kenvandineto keep the pressure on a proper fix16:18
sil2100kenvandine: remember that we first need the other u-s-s silo to merge-and-clean fully16:18
kenvandinesil2100, yes...16:18
kenvandinenot building until then16:18
bzoltan_kalikiana: ping16:18
sil2100Excellent :)16:18
jibelkenvandine, fine, it's better than being completely blind16:18
kalikianabzoltan_: pong16:19
kenvandinejibel, right... we know it isn't a real failure, just causing all hell to blow up in the test :)16:19
bzoltan_kalikiana:  om26er sees this http://i.imgur.com/xse3evb.png16:19
bzoltan_om26er:  what version of the UITK you have on the device?16:19
kalikianabzoltan_: hmmm the handlers are missing?16:20
bzoltan_kalikiana: yes indeed16:20
om26erbzoltan_, 1.1.1298+15.04.20150218~rtm-0ubuntu116:20
kalikianaom26er: how did you select that text?16:20
om26erkalikiana, double tap16:21
bfillerkenvandine: any way to speed up landing camera-app which is in proposed? http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu&q=camera16:25
bfilleritching to rebuild sync silo16:25
kalikianaom26er: hmm can repro. and it's indeed the change to blame… no idea, though, what is happening, never seen that16:25
kenvandinebfiller, no... i don't think so16:25
bfillerkenvandine: like watching paint dry16:26
kenvandinebfiller, it usually takes about an hour16:26
kenvandineyeah16:26
bfillerok16:26
kenvandinebfiller, why aren't you on the slopes?16:27
kenvandineif it's because of  camera-app, i can help :)16:27
bfillerkenvandine: going this afternoon :)16:27
plarsalan_g: Looks like it was a weird fluke with that device, but the device seems fine now. I've restarted the job and I'll continue to monitor it16:28
alan_gplars: thanks16:30
kalikianaom26er: bzoltan_ I'll need to look into what unity is doing there. it has a custom clear button for some reason, but that doesn't easily explain this funny bug.16:30
om26erkalikiana, ok, i'll fail the silo for now.16:31
bzoltan_om26er: please hold a bit16:33
om26erbzoltan_, ok, moved back.16:35
sil2100davmor2: you signing-off location-service?16:37
sil2100Are we ok with getting a risky component like that in this milestone?16:38
jibelsil2100, it's in OTA1 priorities16:39
sil2100It was? hmmm16:40
davmor2sil2100: factory bug for battery drain aiui jibel okayed it16:40
sil2100I missed it completely16:40
sil2100jibel, davmor2: hm, the spreadsheet doesn't mention it as being reported by BQ/CKT16:41
davmor2sil2100: the battery drain general bug is though and this is a sub branch from that16:42
rhuddiebfiller, is there an update required on the rtm silo for the camera-app fix?16:55
bfillerrhuddie: we should rebuild the camera-app deb once it lands in vivid but stuck in proposed16:56
jhodappsil2100, not sure what happened here, any insight? https://ci-train.ubuntu.com/job/ubuntu-landing-028-1-build/23/console16:56
bfillerrhuddie: since we don't use the deb it can probably land as is if all the testing done16:56
bfillerrhuddie: I just need to upload the click you tested to the store16:57
jhodappsil2100, actually nevermind, the more detailed logs for each ARCH point out what's wrong16:57
sil2100jhodapp: it seems the packages failed to build in the PPA16:57
jhodappsil2100, yeah, missing build dep16:58
rhuddiebfiller, this click is giving me a problem loading the app16:58
bzoltan_om26er:  I pull off that MR from the landing silo and leave the oneliner to fix the other bug. If you culd wait a half an hour16:58
bfillerrhuddie: what do you mean?16:58
om26erbzoltan_, sure thing.16:59
rhuddiebfiller, well, I've installed it with the silo updates, when I launch it, I see the camera screen load briefly and then it disappears16:59
bzoltan_om26er:  at least we ship two bugfixes with this round16:59
bfillerrhuddie: I'm not seeing that, anything in the log? ~/.cache/upstart/application-click-com.ubuntu.camera_<version>.log17:00
plarsalan_g: it's looking like my retry is going to suffer the same fate - I think it could be your change that's killing it17:01
plarsalan_g: it's on a different device this time, and it was fine after the base install, but not after installing your update and rebooting17:02
alan_gplars: I'll take another look at it17:02
kenvandinebfiller, i feel your pain, i'm watching paint dry too.. with settings17:04
* kenvandine twiddles thumbs17:04
bfillerrhuddie: I'm seeing the issue, checking the problem17:04
rhuddiebfiller, this is my log: http://pastebin.ubuntu.com/10293406/17:05
bfillerKaleo: the click for camera-app that was built by jenkins has some issues, getting undefined symbols17:09
bfillerKaleo: see rhuddie log above, I'm seeing the same17:09
bfillerKaleo: did something change in qtubuntu-camera in vivid that is needed now in RTM?17:10
Kaleobfiller, dunno of that, but we changed only one line since you last built a click17:31
Kaleobfiller, checking17:31
bfillerKaleo: I just rebuilt the click, trying that now.17:31
Kaleobfiller, it looks nothing like any change that may have been made to any of the code17:32
Kaleobfiller, it looks more like something in the build env that has changed17:32
Kaleobfiller, it's the first time we actually use the camera click pkg produced by jenkins no?17:33
Kaleobfiller, usually we build it ourselves IIRC17:33
Kaleobfiller, both for testing and publishing17:33
bfillerKaleo: we always use jenkins, ok here is a new one I built with jenkins seems to work http://people.canonical.com/~bfiller/com.ubuntu.camera_3.0.0.515_armhf.click17:34
bfillerKaleo: please verify to make sure that has nerochiaro's change and that it's working correctly17:34
Kaleobfiller, you built that one *with* jenkins?17:35
bfillerKaleo: yes, but did it manually and didn't take the one jenkins built via CI17:35
Kaleobfiller, I see17:35
bfillernot sure what the difference is but the app launches now :)17:35
bfillerrhuddie: http://people.canonical.com/~bfiller/com.ubuntu.camera_3.0.0.515_armhf.click17:35
Kaleobfiller, ok17:35
mzanettitrainguards: can someone please rebuild qtsystems in silo0 for me?17:38
robrumzanetti: do you not have permission?17:39
mzanettirobru: afaik I can't no, because it's not added via the spreadsheet but uploaded manually17:39
robrumzanetti: oh, hrm.17:39
mzanettiI might be wrong...17:39
robrumzanetti: so what, you need a no-change rebuild? you don't have a change to apply to it?17:39
mzanettiI pushed to the branch17:39
mzanettioh, I see17:40
mzanettione sec :)17:40
mzanettirobru: lp:~mzanetti/ubuntu/vivid/qtsystems-opensource-src/inputinfo17:40
robrumzanetti: oh ok, yeah I can upload that, one sec.17:41
mzanettithanks17:41
bzoltan_om26er:  the silo1 is ready .. I ripped off the cursor "fix"17:41
om26erbzoltan_, thanks for that, I'll repick it after a few minutes. In a meeting right now.17:42
nerochiarobfiller: Kaleo: i tested the image you linked and it seems to have my change and be working ok17:42
bzoltan_om26er:  OK, thanks for your patinece17:42
Kaleonerochiaro, by image you mean click?17:43
nerochiaroKaleo: sorry yes17:43
Kaleobfiller, nerochiaro: I have tested the manually built click 515 and it works too17:43
kenvandinesil2100, is there an excuses page for rtm?17:44
kenvandinesil2100, it's taking unusually long for settings to make it to release17:44
sil2100kenvandine: yeah, one moment17:44
sil2100ugh17:44
sil2100Wait, wtf, it's gone17:44
robrumzanetti: what do you want in the changelog? eg what did you change?17:45
sil2100aaaha17:45
sil2100nvm17:45
sil2100kenvandine: http://people.canonical.com/~ubuntu-archive/proposed-migration/ubuntu-rtm/14.09_update_excuses.html17:45
sil2100hmm17:45
kenvandinesil2100, hmmm settings isn't on that17:45
sil2100it's outdated17:45
kenvandineoh... indeed17:45
kenvandineis something not running?17:45
sil2100cjwatson: are there any known problems with 14.09 migration right now?17:46
sil2100slangasek: ^ ?17:46
robrumzanetti: nm, got your commit message17:47
slangaseksil2100: I've just committed a merge of some changes from cjwatson to proposed-migration, could be related17:48
cjwatsonsil2100: Heh, somebody merged my branches but one of them was deployed slightly differently live, so conflict17:48
cjwatsonI'll fix17:48
slangasekoops17:48
kenvandine:)17:48
slangasek"deployed slightly differently live"?17:48
kenvandinecjwatson, thanks!17:48
cjwatsonI deployed an earlier version of the output-prefix stuff because it was urgent for 14.09-factory17:48
kenvandinesil2100, i've been anxiously watching it so i could build that silo for you :)17:48
robrumzanetti: ok, new upload building, should be good to go17:49
* cjwatson replaces with the committed version17:49
cjwatsonsil2100: should work next time, thanks17:49
cjwatsonslangasek: thanks for the merges17:50
sil2100kenvandine: ;)17:50
slangasekcjwatson: sure thing17:50
sil2100Thanks for fixing!17:50
cjwatsonI guess I'd better run them by hand to catch up17:50
sil2100kenvandine: we'll spin a new image as soon as the current u-s-s migration finishes17:50
kenvandinecjwatson, that would be appreciated17:50
sil2100kenvandine: we can include the autopilot fixes later17:50
kenvandinesil2100, sure17:51
sil2100(as those don't require testing by QA anyway)17:51
kenvandinesil2100, ah... can you change that on the spreadsheet then?17:51
kenvandinei put required17:51
sil2100Sure17:52
kenvandinesil2100, thx17:52
cjwatsoneek, this is crashing hard17:52
* cjwatson disables archive-reports while he debugs17:52
rhuddiebfiller, Kaleo, thanks. confirm this version is now working and I get video thumbnail. One bug I've noticed is that the new photo-roll Edit option is enabled for videos, as well as photos17:52
bfillerrhuddie: that is indeed a bug17:54
Kaleobfiller, shall we disable editing? :)17:54
bfillerKaleo: if we don't seed qtdeclarative5-ubuntu-ui-extras0.2 then it will be disabled17:54
Kaleobfiller, right17:54
Kaleobfiller, is it seeded in vivid?17:55
Kaleobfiller, it's not seeded anywhere atm right?17:55
bfillerKaleo: it's seeded in vivid but not in rtm17:55
Kaleobfiller, so we need to fix the bug regardless17:55
bfillerKaleo: lets just fix it, should be simple17:56
Kaleobfiller, ugo said it's prob easy17:56
bfillerwe do the same already in gallery-app17:56
Kaleobfiller, good, was gonna asxk17:56
cjwatsonsil2100,kenvandine: should be happier now17:56
Kaleo-x17:56
Kaleorhuddie, fixing now, should be a one liner :)17:57
sil2100cjwatson: yaay, thanks ;)17:57
=== alan_g is now known as alan_g|EOD
cjwatsonsil2100: note it's now http://people.canonical.com/~ubuntu-archive/proposed-migration/ubuntu-rtm/14.09/update_excuses.html, sorry for the rearrangements - I'll put symlinks or redirects or something in place in a bit17:57
cjwatsonanother reason I want to do a couple of runs by hand17:57
rhuddieKaleo, thanks. I'm going to be eod soon, so somebody else will pick this one up again17:58
Kaleorhuddie, understood, thanks17:58
Kaleorhuddie, do you know who?17:58
rhuddieKaleo, not yet. I'll update the card on the trello board with status. depends on how soon the next regression run starts.18:01
Kaleorhuddie, any idea when that might be?18:01
Kaleorhuddie, I mean, are we talking minutes hours or days?18:01
rhuddieKaleo, well i believe new build should be within 2 hours18:02
Kaleorhuddie, ah ok18:02
=== boiko_ is now known as boiko
kenvandinecjwatson, thanks18:06
kenvandinesil2100, settings is in release now and i started building silo 11 for the test fix18:07
om26erbzoltan_, how can i verify fix for #1395118 ?18:18
bzoltan_om26er:  there is a demo code in the bug report18:19
om26erbzoltan_, if i put that into a .qml how can i launch it ?18:20
bzoltan_om26er:  just open the Ubuntu SDK, create a simple UI template app and copy that code over the main.qml18:21
sil2100kenvandine: thanks!18:30
sil2100Ok, let me check proposed and build a new image18:30
sil2100kenvandine: ok, so we have gallery-app stuck in -proposed because of missing qtdeclarative5-ubuntu-ui-extras0.2 , but we have a click for that anyway18:31
kenvandineyeah18:31
imgbot=== IMAGE RTM 240 building (started: 20150218-18:50) ===18:50
pmcgowanboiko, sil2100 are we able to land silo 15? that has the last critical fixes18:58
sil2100pmcgowan: too late18:58
pmcgowansil2100, those are factory fixes, so maybe not18:58
sil2100pmcgowan: the silo is still not set as ready...18:59
boikopmcgowan: testing it18:59
sil2100pmcgowan: and we really need time to test the image, I already kicked off the first promotion candidate18:59
pmcgowansil2100, I understand but won't matter if factory doesnt accept it19:00
pmcgowanjohn-mcaleely, ^^ what do you think19:00
pmcgowansil2100, we can start testing then consider poking that one silo in19:00
sil2100hm, we can get a new one re-spinned later I guess19:00
pmcgowansil2100, remember that was our plan to consider factory fixes late19:01
john-mcaleelysil2100, delay gets my vote, or land it late after QA with some retesting of that area?19:01
sil2100I'm a bit worried with the tight timeline, but yeah19:01
john-mcaleelypmcgowan, ^ as we discussed, I htink19:02
pmcgowanagreed, lets get it ready for QA then decide19:02
john-mcaleelyyeah, nothing to be done until that state is reached19:02
sil2100Since it's ofono-related then I would actually wait with testing until it lands19:02
sil2100As it would require retesting a lot of things anyway19:03
john-mcaleelymakes sense19:04
pmcgowanright agreed19:04
sil2100boiko: how does it look so far? You think it will be ready for sign-off in the nearest hours?19:04
sil2100I'll have to disconnect in a few, but I'll get back in around 2 hours in case an image needs to be built19:05
sil2100ToyKeeper: hey! Just so you know, if you see silo 15 as ready for sign-off please take care of it with priority ;)19:07
sil2100robru: ^ and if you could publish it with priority as well19:07
robrusil2100: sure thing19:07
sil2100Thanks :)19:07
ToyKeepersil2100: Does that mean 240 isn't the promotion candidate, but 241 is?19:07
boikosil2100: yep, it is looking good so far, should be ready for signoff pretty soon19:08
sil2100ToyKeeper: yeah, basically 241 will be the image we'd like to release19:08
sil2100kenvandine: ^ looks like your u-s-s autopilot fixes will still land in the promotion candidate ;)19:09
rsalvetitriggering a new vivid for the new pulseaudio19:13
kenvandineRan 121 tests in 1441.927s19:13
kenvandineOK19:13
kenvandinesil2100, ^^19:13
sil2100\o/19:14
sil2100Ok, need to drop off now, see you in a few hours19:15
kenvandinesil2100, should i publish that?19:15
sil2100kenvandine: hm, not sure if the rootfs for 240 already finished19:15
imgbot=== IMAGE 104 building (started: 20150218-19:15) ===19:15
sil2100kenvandine: maybe wait a few and then publish ;)19:15
kenvandinesil2100, a "few"19:15
robrukenvandine: rtm 11 doesn't need qa?19:15
kenvandinehow long is that?19:15
kenvandinerobru, no... autopilot only19:16
kenvandinefixes the smoke tests19:16
robrukenvandine: cool19:16
sil2100robru: no, it's just an autopilot change, but kenvandine will publish it if anything19:16
robrusil2100: k19:16
sil2100kenvandine: maybe in like 30 mins or so?19:16
kenvandinesure19:16
sil2100Thanks guys ;)19:16
kenvandinesil2100, how can i tell if it's safe?19:17
kenvandinesil2100, have a good one!19:17
sil2100kenvandine: hmm... there's a way of checking if the rootfs built but I never remember the links for that ;p19:17
sil2100See you in a bit o/19:17
ToyKeeperD'oh, too late.19:22
ToyKeeperrobru, boiko: I can't test silo rtm-015.  The plan is to use 240 as the candidate and take rtm-015 a little slower.19:24
ToyKeeperIt kinda requires specific test lab hardware and 4G, neither of which is available on this continent.19:25
robruToyKeeper: hmmm19:25
robruToyKeeper: ok well do what you can. if you can only test 240 then so be it. when the europeans wake up they can test 241 then.19:26
=== plars changed the topic of #ubuntu-ci-eng to: Need a silo or CI Train support? ping trainguards | Need help with something else? ping cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: ubuntu-rtm landing gates now closed
=== fginther changed the topic of #ubuntu-ci-eng to: Need a silo or CI Train support? ping trainguards | Need help with something else? ping fginther | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: ubuntu-rtm landing gates now closed
boikoToyKeeper: so, bug 1421177 is marked as duplicate of another bug by john-mcaleely19:58
ubot5Error: Launchpad bug 1421177 could not be found19:58
boikojohn-mcaleely: can you confirm it is really just a duplicate?19:59
john-mcaleelyboiko, looking20:00
john-mcaleelyboiko, I went on the basis of the commenst in #18 & 19 on that bug20:02
john-mcaleelyit seems that several bugs have poor repros (we lack the equipment), and an engineering call that they may have related fixes20:02
boikojohn-mcaleely: the bug description is very confusing, but re-reading it I think it is correct, unless the reporter says it is not20:03
john-mcaleelyboiko, so my biggest concern would be regressions, rather than confirming those branches fix things20:03
john-mcaleelyboiko, we will not hear from the reporter - they were onsite for one day, and will not go back20:04
boikojohn-mcaleely: so, the branch really fixes 141629220:04
john-mcaleelyboiko, again, we've never well reproduced that, so it's a judgement call, I think20:05
boikojohn-mcaleely: the chances of regressions are very low20:05
imgbot=== IMAGE RTM 240 DONE (finished: 20150218-20:05) ===20:05
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/240.changes ===20:05
john-mcaleelyboiko, then I prefer to say we tried to fix it, and did make an improvement20:05
boikojohn-mcaleely: and as I said before, 1416292 is really fixed20:05
john-mcaleelyand therefore land '1520:05
john-mcaleelyexcellent20:05
boikojohn-mcaleely: also, with the stuff that already landed on silo 11,  call accepting/hanging up handling was improved a lot20:06
john-mcaleelyboiko, sounds good20:06
boikoToyKeeper: so, I think testing the other bugs is enough in this case20:07
john-mcaleelyI think that is the best we can do20:08
boikoToyKeeper: also, 1422401 was partially fixed with a fix in ofono that was landed on silo 11, so if you try to reproduce the problem without silo 15, you might not succeed, the telephony-service side of the fix just cover extra failure possibilities20:08
* john-mcaleely eod20:09
=== salem_ is now known as _salem
robruToyKeeper: well there's that ^20:18
ToyKeeperHmm, silo rtm-11 didn't actually land in image 240 though, no?20:31
ToyKeeperIt was approved after 240 started building.20:31
kenvandineToyKeeper, no it didn't20:31
kenvandineToyKeeper, sil2100 wanted it to go in 24120:32
ToyKeeperOkay.  I'll try to avoid telephony tests on 240, since they'll be obsoleted by 241 anyway.20:32
kenvandinetelephony?  rtm 11 was settings autopilot fixes20:33
ToyKeeperOkay, looks like there were two different silo 11s then.  :)20:33
kenvandineah :)20:33
kenvandinertm 11 with settings fixes the smoke test failures20:33
kenvandineautopilot test changes only20:33
ToyKeeperRegardless, image 241 should have some new telephony fixes.20:33
kenvandineToyKeeper, so then the previous silo 11 should be in 24020:34
boikoToyKeeper: flashing 240 here, I can tell if the fixes are there in a minute20:44
ToyKeeperboiko: I just had two silo 11s mixed up; wasn't aware there were two.20:44
boikoToyKeeper: ah ok :)20:45
plarspopey: so did I hear correctly that calendar is back?20:48
imgbot=== IMAGE 104 DONE (finished: 20150218-20:50) ===20:50
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/104.changes ===20:50
kgunntrainguard i can give up vivid silo 1321:32
kgunntrainguards i can give up vivid silo 1321:32
robrukgunn: sure21:32
robrucihelp s-jenkins is having some trouble: https://jenkins.qa.ubuntu.com/job/cu2d-choo-choo-autolanding/146/console seems intermittent, I've had some success with retries, but not always22:33
fgintherrobru, looking22:34
=== fginther changed the topic of #ubuntu-ci-eng to: Need a silo or CI Train support? ping trainguards | Need help with something else? ping cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: ubuntu-rtm landing gates now closed
robrufginther: thanks22:34
sil2100o/22:36
sil2100Hey, did silo 15 land?22:36
robrusil2100: no, apparently ToyKeeper isn't equipped to qa it.22:37
sil2100Oh shit22:37
robrufginther: http://s-jenkins.ubuntu-ci:8080/job/cu2d-choo-choo-ci/ this is the one where the retry worked. the -autolanding one seems just dead22:37
ToyKeepersil2100: Even so, I was asked not to, so people in .eu can do it in the morning.22:38
robrufginther: same traceback as far as i can tell22:38
fgintherrobru, there's an issue with a subset of the builder nodes, trying to track it down22:38
sil2100ToyKeeper: oh, who asked that?22:38
robruToyKeeper: whoa whoa, I didn't ask you not to, I just suggested that .eu people could if you couldn't.22:38
ToyKeepersil2100: One of the bugs in 15 can only be tested in the test lab, too.22:38
ToyKeeperOh, jibel asked me not to.22:38
sil2100If that's the overall decision then ok, but now I'm really worried about time22:38
robruToyKeeper: oh ok cool ;-)22:38
sil2100ToyKeeper: ok, then I trust that jibel knows best what resources QA has22:39
sil2100ToyKeeper: I suppose you could do sanity testing on #240 at least for krillin22:39
ToyKeeperAlready doing that, and then on to regression testing for it...  just not the telephony parts.22:40
sil2100This way at least we'll know if images aren't completely broken22:40
sil2100Excellent22:40
sil2100Ok then, so it means I won't be needed22:41
sil2100See you tomorrow everyone o/22:41
robrufginther: ah, it merged now, thanks23:03
fgintherrobru, I found a corrupted project that appears to be the culprit. I'm now looking for the same problem on other nodes.23:06
robrufginther: good work!23:06
fgintherrobru, but things should be working for those jobs now23:06
=== _salem is now known as salem_

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