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

Wellarkrobru: thanks!00:02
ToyKeeperalecu: Is silo 8 fixed now?00:10
alecuToyKeeper: yes, we added a fix, and we added some workarounds to the test plan to account for a misterious bug where the dash remains fixed and untappable until you switch apps.00:11
alecuToyKeeper: tedg suspects that bug is in Unity, and will look at it tomorrow with tvoss00:12
ToyKeeperalecu: Flashing now for testing...  could take a while to finish though.00:15
alecuthanks!00:16
ToyKeeper(faster if none of the features work in the stock image...  longer if they work but changed, since I need to test before and after)00:16
alecuwill join the family for dinner and will check here afterwards00:16
ToyKeeperI'm a little distracted today too; just have tonight to finish house repairs before the new floor goes in tomorrow morning.00:17
alecuToyKeeper: keep in mind that this feature is hidden for normal users; only QA people wishing to test purchases in staging end up running this script and following these steps00:18
ToyKeeperHmm.00:18
alecuToyKeeper: also, it's the first time we are asking QA people to take a look at this00:18
ToyKeeperIn that case, perhaps I can skip the "before" phase.00:19
alecugreat00:19
alecusorry this is so late in the cycle, but we've been blocked by dash-as-app landing in order for the final installation step is completed after the purchase.00:20
ToyKeeperI think pretty much everyone is behind where they'd like to be.  There's just too much to do.  :)00:20
alecuindeed :-00:21
alecu)00:21
ToyKeeperalecu: It mostly looks good so far, but the default page to add a card isn't working.  Probably because the card details field is partly hidden and it's not obvious what the expected data is:  http://toykeeper.net/tmp/phablet/2014-08-07/add-cc-doesnt-fit.png01:56
alecuToyKeeper: those are awesome news!01:58
ToyKeeper... and the OSK starts in a mode which doesn't allow entering the correct data.  Like, there's no way to enter a space or a slash.01:58
alecuToyKeeper: the page to enter card details is a webpage straight out of our servers, and it's very far away from what we are changing in this branch01:59
alecuToyKeeper: in fact, let's open a bug with that screenshot in Software center agent01:59
ToyKeeperalecu: ... and after entering bad data on the legacy interface, it fails back to the new UI with no link back to the legacy UI.02:00
ToyKeeperBut again, server-side.02:00
ToyKeeperThe client looks fine.02:00
alecuyay!02:01
ToyKeeper(aside from issues noted in the test plan, which I assume we're not blocking over)02:01
alecusure02:01
alecuToyKeeper: thanks a lot for staying so late. Hope you can finish with your house repairs :-)02:02
ToyKeeperIt's not late for me...  I'm just working 15+ hours between Canonical and the house repairs.  I'll be back again later tonight.02:03
robruToyKeeper, thanks!02:03
imgbot=== trainguard: IMAGE 178 building (started: 20140808 02:05) ===02:05
robruinfinity, stgraber: anybody around? need a core dev ack on a new binary package https://ci-train.ubuntu.com/job/landing-008-2-publish/lastSuccessfulBuild/artifact/packaging_changes_pay-service_2.0.0+14.10.20140807.1-0ubuntu1.diff02:05
ToyKeeperEr, did we just miss getting silo 8 into image 178?02:05
alecuI'm very happy anyway :-)02:05
robruToyKeeper, yep02:06
ToyKeeperSigh.02:06
robruToyKeeper, it wasn't a close miss. between the core dev ack + proposed migration it'll probably be 2-3 hours before it's actually in the archive.02:06
ToyKeeperIt took a while to get the environment changes to stick, since I don't have phablet-shell set up and it doesn't work via adb shell.02:06
alecuToyKeeper: we can add some instructions to run over plain adb shell02:09
alecuToyKeeper: "su -l phablet" should be enough02:09
Wellarkso quiet..02:51
imgbot=== trainguard: IMAGE 178 DONE (finished: 20140808 03:40) ===03:40
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/178.changes ===03:40
Mirvhello04:04
cjwatsonMorning.  How are we looking for a promotion?06:59
cjwatsonThe bug list doesn't look immediately promising for that :-(07:01
ToyKeeperDrat, it doesn't want to let me mount /android/system as read-write.07:06
cjwatsonLoop-mount on RO base?07:06
ToyKeeperYes, I think so.  I'm looking for the image file.07:07
Mirvno progress seems to be yet done on the date/time picker or the camera launch (popup notifications)07:10
Mirvmusic app was confirmed to be fixed as it passed 100% on #17707:10
Saviqcihelp, hey, our qmluitests job started timing out after yesterday's jenkins reboot (??) http://s-jenkins.ubuntu-ci:8080/job/unity-phablet-qmluitests-utopic/814/console07:11
Saviqa complete run before took under an hour, now it times out after 3h07:11
Saviqalways after the actual tests complete, last step seems to be generating coverage report07:12
Mirv#178 would be the bestest ever if it weren't for those two blockers07:13
Mirvmako pass rate 99.0%07:13
Saviqwe'll get there :)07:24
tvosstrainguards: can I get a silo for line 31?08:03
sil2100tvoss: hi! Let me try08:06
tvosssil2100, thank you08:06
ogra_wow, looks like traincon actually helped :)08:06
sil2100tvoss: how's silo 004 going? :)08:08
sil2100Ah, ok, so the hot-fix landed in the meantime08:09
ogra_camera app crashes though :/08:09
sil2100So the only blocker left for us is the date-time picker...08:09
sil2100ogra_: on start?08:09
ogra_no on the smoketest page08:09
ogra_surely unrelated to the location stuff08:10
ogra_but due to that we didnt have any results for it for the last uploads it had08:10
sil2100It works fine on my device, so I wouldn't consider it a blocker, as it probably crashed on shutdown08:11
ogra_oh, i didnt talk about it being a blocker :)08:11
ogra_just another thing we have to look at now08:11
sil2100zsombi: hi! Soooo...! Any luck with the date-time picker?08:11
sil2100zsombi: it's basically our last blocker (I hope)08:12
zsombisil2100: I made a small JS workaround for it, as it did not work in C++.... it ended up that Qt Compositor changes screwed it up08:12
sil2100ogra_: right... let's see if it happens on the next smoketesting08:12
ogra_yup08:12
sil2100zsombi: yeah, we saw Mirv bi-secting it to QtCompositor - so do you think we can land the JS workaround today? We would be super happy08:13
zsombisil2100: so, all we can do in the toolkit is to provide this workaround which apps shoudl use till we get the Qt Compositor fixed08:13
=== sil2100 changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | CI Train support: trainguards | Vanguard (general help): cihelp | CI Train Status: #157 promoted | CI Train Dashboard: http://bit.ly/1mDv1FS | Known issues: Forceful TRAINCON-0! Please work together on getting all blockers resolved.
zsombisil2100: that wouldn't be the only thing we must do: apps must use the PickerPanelWorkaround.openDatePicker() in order to get it working08:14
sil2100zsombi: ah, ok, so like a new component will have to be used instead now by applications? i.e. the calendar app will have to be modified as well?08:14
zsombisil2100: yes, until we get the causing bug fixed, then they can go back to PickerPanel08:14
zsombisil2100: replacing the component "PickerPanel" with the workaround woudl break the API08:14
tvosssil2100, still exhibiting the issues, but the immediate user facing problems are fixed by whitelisting the camera app and osmtouch08:14
ogra_tvoss, trust-stored-skeleton also has a bunch of crashes during testing, did anyone ping you about that already ?08:15
tvossogra_, nope08:15
sil2100zsombi: works for me! If you and Zoltan could prepare a landing for the PickerPanelWorkaround addition we would drive that, and then ask someone from the calendar-app developers to use the new component08:15
zsombisil2100: ai sire!08:16
ogra_tvoss, at the bottom of http://ci.ubuntu.com/smokeng/utopic/touch/mako/178:20140808:20140805.2/9562/default/ and http://ci.ubuntu.com/smokeng/utopic/touch/mako/178:20140808:20140805.2/9562/webbrowser_app/ if you want to look at them later08:16
sil2100zsombi: thanks in overall!08:16
* sil2100 smells promotion today08:16
tvosszsombi, do we have a theory why qtcomp influences the date-time picker. I have difficulties understanding why qtcomp would influence in-app rendering08:17
sil2100davmor2: ready your dogfooding skills, those will be needed soon!08:17
tvossogra_, thanks, do we have retraces available for the crash files?08:17
zsombitvoss: not much, but all we know was that it got broken after that fix08:18
ogra_tvoss, i dont think so ... psivaa-afk-bbl could tell you i guess08:18
=== psivaa-afk-bbl is now known as psivaa
zsombitvoss: what it looks from our side is that it behaves like the Singleton would have been created with a different root context08:18
zsombitvoss: despite it gets created with the same QML engine08:18
zsombitvoss: the Singleton (PickerPanel) does not get anything from the other root context08:19
tvosszsombi, sure, but that's not influenced by qtcomp. Are you sure that the setup is not racy, and that no change to qt/qml landed at the same time?08:19
zsombitvoss: any context property that it gets defined there08:19
psivaatvoss: ogra_: we only have this at the moment, if that helps: https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/677/artifact/clientlogs/webbrowser_app/_usr_bin_trust-stored-skeleton.32011.crash/*view*/08:20
zsombitvoss: there was no other change in between those two releases that would have affected it...08:20
psivaaotherwise this file has to be processed manually i guess08:20
ogra_yeah, thought so08:20
Mirvtvoss: it works by downgrading platform-api, unity8 and by switching from qtmir to qtubuntu+unity-mir. so, no other Qt/QML changes.08:21
Mirvthat is, doing those downgrades on #158 image to the versions that were on #15708:23
tvossMirv, so I would suspect the issue in qtmir then, in its implementation of the qpa08:26
tvossMirv, zsombi do you guys have time on your hands to look into the issue?08:26
zsombitvoss: greyback promised to look deeper into this08:27
tvosszsombi, ack08:27
Mirvtvoss: indeed greyback will be looking from the QPA side of things. I was thinking that I'd try to find time to just hack randomly on the calendar's QML although I believe zsombi would have better success rate :) but he's doing the SDK workaround.08:31
=== vrruiz_ is now known as rvr
psivaaSaviq: re: your unity-phablet-qmluitests-utopic timing out.. have been digging a *bit.. could not find a reason/solution. will have to wait for either retoaded or fginther08:56
Saviqpsivaa, ok thanks, same happened in http://s-jenkins.ubuntu-ci:8080/job/ubuntu-settings-components-qmltests-utopic/ FWIW08:57
psivaaSaviq: yea, the same slave08:58
tvosssil2100, could you reconfigure silo 4, please?09:04
sil2100ACK09:08
sil2100tvoss: done09:10
tvosssil2100, thank you09:10
sil2100yw!09:10
tvosshmmm, jenkins is a bit slow today, have been waiting for a vote for +1 hour now: https://code.launchpad.net/~marcustomlinson/process-cpp/set_mask_on_restore/+merge/23005909:15
tvosscihelp, could someone help me in understanding the build timeout here: https://jenkins.qa.ubuntu.com/job/location-service-utopic-amd64-ci/163/console09:29
psivaatvoss: we see this timing out in some other jobs too.. waiting for retoad to see what caused it09:42
tvosspsivaa, something is indeed weird: https://jenkins.qa.ubuntu.com/job/process-cpp-utopic-armhf-ci/11/console09:50
sil2100I need to AFK for a moment, brb09:59
popeyooh, bug!. making note to file this - have two events at the same time, dismiss first, can't dismiss second...10:01
popeyphone unusable10:01
brendandare there any silos that need testing?10:22
ogra_Saviq, the new UI !!!!!!10:23
ogra_so sexy !!!!!!!!10:23
* ogra_ just upgraded to 178 and is super impressed10:24
brendandogra_, you mean the indicator?10:25
brendandSaviq, url-dispatcher broke again10:25
ogra_brendand, nope, unity810:25
brendandogra_, what - you mean the loading bar? and the dots?10:26
ogra_yeah :)10:26
brendandi think the dots should remain static when swiping10:27
ogra_yeah, true10:28
ogra_file a bug :)10:28
cjwatsonsil2100: Was there ever a decision on where the target series would go in the spreadsheet?10:29
nik90brendand: what changed with the indicator?10:33
Mirvthe dots are nice I agree10:34
Saviqbrendand, ogra_, they can't stay static10:38
Saviqas the bar in which they are in can move around10:38
ogra_yeah, what i thought ... would be nicer though10:38
ogra_it feels like the icon drawing slowness got a bit worse though10:38
ogra_(in the app scope)10:39
ogra_(when scrolling)10:39
Saviqogra_, [the dots] that was the initial plan, but when we started thinking of all the corner cases, it was safer to make as it is, until we decide on a more static place to put them on at least10:39
ogra_yeah, no biggie10:39
brendandnik90, sim details are shown10:40
nik90brendand: ah yes that10:40
=== tvoss is now known as tvoss|errands
MirvI'll try out zsombi's UITK branch and try to modify calendar to use it10:45
alf_cihelp: Hi! http://s-jenkins.ubuntu-ci:8080/job/mir-team-mir-development-branch-utopic-amd64-ci/871/console is stuck (been building for 3h40m now), can you please check what the problem is?10:46
sil2100cjwatson: there will be an additional column, but we didn't yet decide on the position11:03
sil2100cjwatson: I'll experiment as we already have, so to say, 'too many columns'11:04
sil2100Mirv: thanks!11:05
sil2100Mirv, bzoltan: is there a branch ready somewhere? Or a landing prepared?11:05
Mirvsil2100: https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/pickerpanel-workaround/+merge/230075 - from sdk channel I read that it's not being prepared so far, only kept as a backup solution in case the QPA side fix isn't found or such. but given timeline, maybe a landing should be already prepared for that.11:07
sil2100Yeah, so I would opt for the workaround, as to get a promotable image today still we would have to build an image in like at max 2 hours11:09
piiramarsil2100: landing item "tone generator support on dialer and telephony-service" (row 22 in the spreadsheet) would need one more test plan https://wiki.ubuntu.com/Process/Merges/TestPlans/tone-generator . can you add that?11:10
Mirvsil2100: I think we could even add a landing line plus kick a build without waiting for Zoltan?11:10
piiramarboiko requested it11:10
Mirvin case it takes time11:10
Mirvpiiramar: adding11:11
piiramarMirv: thanks11:11
Mirvolepa hyvä11:11
piiramarkiitos11:11
sil2100piiramar: done11:13
piiramarthanks11:13
sil2100Mirv: yeah, would make sense, but first make sure bzoltan is aware of that since I'm not completely aware of their workflow (i.e. staging etc.)11:14
sil2100So that we make sure it's in staging as well11:14
=== MacSlow is now known as MacSlow|lunch
davmor2sil2100: so I don't see anything that isn't already known in 17811:29
davmor2sil2100: oh except the twitter password in accounts I must bug that before I head off :)11:36
popeydavmor2: seen the issue where if you have two alarms at the same time it blocks pin unlock, you have to reboot phone?11:40
sil2100;)11:40
davmor2sil2100: https://bugs.launchpad.net/account-plugins/+bug/1354402 not a blocker just annoying :)11:41
ubot5Ubuntu bug 1354402 in Online Accounts: Account plugins "Online accounts twitter password keyboard doesn't stop up unless the field is long pressed" [Undecided,New]11:41
davmor2oSoMoN: ^ that one might be of interest to you11:41
davmor2popey: I haven't but I don't often have 2 alarms going off, did you file a bug for it in the meantime I'll try and reproduce it11:42
popeyno, will do11:43
=== tvoss|errands is now known as tvoss
bzoltansil2100:  what Mirv said is correct. I am preparing that MR and land it on the staging when we decide to go with the workaround11:48
=== lool- is now known as lool
davmor2popey: confirmed it so just need a bug11:50
rsalvetisil2100: the hot fix is not to make it promotable though11:51
rsalvetisil2100: as it has the camera-app version hardcoded in it, is just to unblock other stuff11:52
rsalvetisil2100: so the location-service trust-helper changes are still blocking promotion, until silo 4 lands11:53
tvossrsalveti, why wouldn't we promote with the hotfix in?11:53
rsalvetitvoss: because as soon we update camera-app or osmtouch (from app store, for example), it will be broken again11:54
rsalvetiunless we don't care about osmtouch11:54
rsalvetinot sure if camera-app could be updated via store though11:54
popeydavmor2: bug 135440611:54
ubot5bug 1354406 in indicator-datetime (Ubuntu) "2nd of 2 alarms at same time is unclickable" [Undecided,New] https://launchpad.net/bugs/135440611:54
tvossrsalveti, so your proposal then is to extend the hotfix to arbitrary versions in case silo 4 does not fix the issue?11:55
rsalvetitvoss: if you want a promotable image, yes11:55
rsalvetior a revert, as we discussed yesterday11:56
rsalvetibut I thought silo 4 would land today11:56
rsalvetiis it still in progress?11:56
tvossrsalveti, dednick is on it, I rebuilt it an hour ago, will test it now11:56
rsalvetigreat11:57
rsalvetisil2100: which other issue is blocking promotion?11:57
davmor2Right guys I'm off have a great weekend catch you all Monday, sil2100 I won't be around for the  morning meeting so I'll catch up on irc at 11:00 :)11:58
=== nik90 is now known as nik90|Lunch
oSoMoNsil2100, hey, can we have a silo for line 32 ?12:03
=== alan_g is now known as alan_g|lunch
ogra_rsalveti, time/date picker issues iirc12:04
sil2100tvoss, rsalveti: so, to get things straight... the current hot-fix for the camera-app only work for the current camera-app?12:06
sil2100And it will be broken again if we release a new version of camera?12:06
bzoltansil2100:  we have the workaround branches for the UITK and for the Calendar ready if you guys want it12:06
popeydavmor2: have a great weekend.12:07
sil2100bzoltan: do you know how the real fix is going?12:07
sil2100davmor2: see you next week!12:07
bzoltansil2100: I do not.12:07
pmcgowansil2100, gerry knows why it broke and is working on it12:07
bzoltansil2100:  and that is not coming from the SDK team for sure.12:07
rsalvetisil2100: basically, yes12:08
sil2100greyback: hi, how far are you with the real fix for the date-time picker?12:08
rsalvetihm, booted 178 on flo and got a black screen in unity812:08
bzoltansil2100: pmcgowan: just give me the signal if you decide to go with the workaround.12:08
Mirvbzoltan: sil2100: FYI I didn't get the workaround working yet at least, please advise if I'm doing something wrong https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1351024/comments/2012:08
ubot5Ubuntu bug 1351024 in Ubuntu UI Toolkit "Date & Time picker is not working on device." [Critical,In progress]12:08
greybacksil2100: I have a preliminary fix: https://code.launchpad.net/~gerboland/qtubuntu/fix_1351024/+merge/230094 but it needs careful review & testing12:08
rsalvetiunity8-dash crashed12:09
bzoltanMirv:  you need this on the calendar app https://code.launchpad.net/~bzoltan/ubuntu-calendar-app/lp_1351024_workaround/+merge/23009512:09
cjwatsonForking RTM12:09
rsalvetitogether with maliit-server and system-settings12:09
pmcgowandoooh12:09
Mirvbzoltan: looks identical to mine http://bazaar.launchpad.net/~timo-jyrinki/ubuntu-calendar-app/use_pickerpanelworkaround_lp1351024/revision/38712:09
pmcgowancjwatson, good luck!12:09
cjwatson(don't panic, there'll be an e-mail a bit later with more details and why this isn't a problem for anyone yet)12:09
alecu(collective sigh of relief)12:10
sil2100cjwatson: \o/12:12
rsalvetisil2100: Saviq: just got on flo https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/135441212:12
ubot5Error: ubuntu bug 1354412 not found12:12
rsalvetinow public https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/135441212:12
sil2100Mirv: you sure it does not work?12:13
cjwatsonThis has been a bit of an exercise in how much time we can spend polishing a single extremely complicated run-rarely launchpadlib script12:13
pmcgowangreyback, do you recommend we go with the sdk and app side workaround or await your review and test?12:14
pmcgowantvoss, any testing get done on silo 14?12:15
Mirvsil2100: well, it doesn't work for me, other eyeballs on the branches and testing would be welcome12:15
greybackpmcgowan: my fix is more correct, I think it would be better to get it in12:15
tvosspmcgowan, have to check with charles, he worked on it yesterday12:15
pmcgowangreyback, ok lets focus there bzoltan Mirv12:15
sil2100greyback: excellent12:16
Mirvyay for greyback's fix12:16
greybackI'm running UITK AP tests now12:16
bzoltangreyback: I love you man... I was feeling bad about our solution12:16
=== nik90|Lunch is now known as nik90
greybackbzoltan: yeah I didn't like it so much :)12:17
bzoltangreyback:  tell me if you need any help :)12:17
greybackbzoltan: when CI has the package built, I'd appreciate testers12:18
* sil2100 gets his device ready12:25
=== MacSlow|lunch is now known as MacSlow
=== greyback is now known as greyback|lunch
cjwatsonrestarting branching script, we found a mistake just in the nick of time :)12:33
Mirvbzoltan: sil2100: greyback|lunch: working! "Tested with a local build, works with this branch! (ie. similar to #157)"12:35
Mirv(added a comment to greyback's branch)12:35
sil2100Mirv: with greyback|lunch's lunch? :)12:35
sil2100*branch12:35
Mirvsil2100: indeed12:35
Mirvbut was CI broken btw? and does anyone want my hand-build .deb:s to install?12:39
MirvI'd add a line for qtubuntu already (doing)12:39
sil2100Mirv: if you could upload those somewhere then it would save me some time12:40
tvosspmcgowan, so silo 14 fixes the issue that we see in the indicator <-> location service communication. However, charles encountered issue in the indicator backend <-> frontend configuration12:40
pmcgowantvoss, thanks for update, so still diddling that silo?12:41
Saviqrsalveti, can you grep ~/.cache/upstart/unity8-dash.log* for "what", the abort message?12:41
charlespmcgowan, tvoss: yes, it looks like it might be the same issue as https://bugs.launchpad.net/indicator-network/+bug/1336715 in indicator-network <-> the ui toolkit switches12:41
ubot5Ubuntu bug 1336715 in Unity 8 "switch-items in indicators sometimes get out of sync" [Critical,Confirmed]12:41
tvosspmcgowan, I'm torn, it fixes known issues, but not the whole story. With that, we might want to keep the silo until after traincon and land, then12:42
tvosscharles, pmcgowan makes sense?12:42
charlespmcgowan, tvoss, so that still leaves an asterisk next to kenvandine's u-s-s GPS changes, but IMO doesn't block silo 01412:42
rsalvetiSaviq: hm, sorry, flashed it again, will try to reproduce and see if I can get that to you12:42
charlestvoss, yes, that's fine12:43
pmcgowancharles, but we could enable at that point yes?12:43
pmcgowanmodulo the bug above12:43
charlespmcgowan, yes, IMO that's the way to go12:43
pmcgowan+112:43
Mirvhttp://people.canonical.com/~tjyrinki/datepicker/qtubuntu-android_0.60+14.10.20140728+fix1351024-0ubuntu1_armhf.deb12:43
Saviqrsalveti, thanks12:43
tvosscharles, pmcgowan I will take care of getting it in then, likely Monday though12:43
Mirvand building in silo 01512:43
charlespmcgowan, tvoss I'll be looking into the UI issue, if I can find the cause before silo 014 lands I'll coordinate with tvoss to see about sandwiching the fix in12:43
sil2100Mirv: \o/12:43
sil2100Mirv: thanks12:43
Mirvyw12:44
Mirvsil2100: doh, what was the most modern way to do the -gles part, or still a manual upload?12:44
=== josepht changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | CI Train support: trainguards | Vanguard (general help): josepht | CI Train Status: #157 promoted | CI Train Dashboard: http://bit.ly/1mDv1FS | Known issues: Forceful TRAINCON-0! Please work together on getting all blockers resolved.
sil2100Mirv: rsalveti and Saviq know more, but now they do it through MRs, changing the watch file to fetch the non-gles tarball from the silo you're building in12:46
sil2100Mirv: best if you check some examples in qtmir, since it had some recent uploads to the gles branch12:46
SaviqMirv, something along those lines is needed https://code.launchpad.net/~saviq/qtmir/gles-sync-20140716/+merge/22700012:46
SaviqMirv, needs a dch -v $non-gles-version and an update to the watch file to point at the correct silo12:47
Mirvsil2100: Saviq: ok, trying12:47
rsalvetiSaviq: got it again, let me get that for you12:48
* sil2100 is trying out greyback|lunch's fix12:48
rsalvetiSaviq: http://paste.ubuntu.com/7988563/12:49
Saviqrsalveti, interesting, unity8.log ?12:49
rsalvetiSaviq: http://paste.ubuntu.com/7988571/12:49
Saviqrsalveti, *interesting*12:50
pmcgowanMirv, I am not seeing it fixed here with that deb12:50
Saviqrsalveti, dash is basically saying it can't connect to unity8, which seems to be happily running12:51
sil2100Mirv, greyback|lunch: confirming it fixed here on my device12:51
Saviqrsalveti, like some env isn't set up properly12:51
pmcgowanwhat did I do wrong12:51
sil2100pmcgowan: how come? What do you see?12:51
Saviqrsalveti, can you please upload those to the bug and confirm it12:51
pmcgowansame nothing pops up12:51
rsalvetiSaviq: done12:51
sil2100pmcgowan: since the date-time picker will appear below the keyboard if you have it visible, so you have to dismiss the keyboard first12:51
jgdxcihelp: seems building of uss is broken? https://jenkins.qa.ubuntu.com/job/ubuntu-system-settings-ci/1173/12:52
MirvSaviq: trying with that https://code.launchpad.net/~timo-jyrinki/qtubuntu/gles-sync-20140808/+merge/23010112:52
sil2100pmcgowan: did you reboot after installing the package?12:52
pmcgowansil2100, ahh, forgot about tht other bug12:52
pmcgowanonce sec12:52
pmcgowanyep its there12:52
Mirvpmcgowan: it gets fixed only to the state it was at #15712:52
pmcgowanyeah12:52
sil2100At least it's usable now12:52
pmcgowanso works12:52
Mirvbug #1338956 is that other problem12:53
ubot5bug 1338956 in Ubuntu Calendar App "Date/time changer hidden when textfields have focus" [High,In progress] https://launchpad.net/bugs/133895612:53
sil2100We need to make sure now nothing else is b0rken, but so far things look good12:53
josephtjgdx: let me try re-running that job, we had to restart jenkins yesterday as well as genie the jenkins-slave this job ran on.12:55
jgdxjosepht, that's great. Thanks. My sbuild is broken locally for uss, probably not related though.12:56
rsalvetiSaviq: any other info?12:56
Saviqrsalveti, don't think so, you get that on first flo boot after flashing? wiped?12:56
tvossrsalveti, silo 4 fixes the issue for me. Could you give it a spin?12:57
tvossdednick, ^12:57
sil2100\o/12:58
tvosssil2100, ^12:58
sil2100Then there's a possibility that we won't have to rely on any workarounds/hot-fixes if we'll be able to get both landed12:58
rsalvetitvoss: did you also revert your location-service changes on that silo?12:58
dednicktvoss: woop12:58
tvosssil2100, silo 4 actually reverts the location service hotfix12:59
tvossrsalveti, yup12:59
rsalvetiSaviq: yes, bootstrap on flo, first boot12:59
rsalvetitvoss: sure12:59
sil2100It makes me smile then12:59
tvosssil2100, please give it a spin, too12:59
* Mirv is foreseeing a promotion today12:59
popeyuhoh12:59
sil2100tvoss: will do!12:59
rsalvetitvoss: missing qtmir-gles in there12:59
Mirv...and then popey found a Bug? ;)12:59
tvossrsalveti, yup, taking care of that now13:00
rsalvetigreat13:00
popeyheh13:00
sil2100popey: NO13:00
* popey puts the phone down13:00
sil2100We say NO to bugs13:00
sil2100Bad popey!13:00
Saviqrsalveti, really weird, as the dash should only start after unity8 started, so it should've set up the environment properly ;/13:03
tvossSaviq, greyback|lunch https://code.launchpad.net/~thomas-voss/qtmir/sync-20140808/+merge/23010313:04
* Mirv tries to guess the magic order/way of building the silo with twin package13:04
tvossMirv, first with ignore twin packages, grab version, propose mp, take mp and add to silo13:04
tvosssil2100, could you reconfigure 4, please?13:05
Mirvtvoss: sounds like I'm guessing ok, but I also pre-guessed the version and proposed MP, I'll just do the build after this ignore twin packges single package build finishes. thanks!13:05
sil2100tvoss: sure13:05
tvosssil2100, thanks13:05
sil2100Done13:07
SaviqMirv, yup, pre-guessing version works, too ;)13:07
Saviqtvoss, ACK13:07
tvossSaviq, just need to rebuild the gles twin, correct?13:08
Saviqtvoss, yup, you don't want to rebuild non-gles as it would get a different version again13:08
tvossSaviq, yup13:08
tvosssil2100, rsalveti building13:09
=== alan_g|lunch is now known as alan_g
sil2100tvoss: installed your silo as well, now I will perform some tests on it to see if all is ok13:14
sil2100And I guess we'll land both silos (4 and 15)13:15
brendandsil2100, i think there's a functional bug in gallery app caught by the autopilot tests13:16
brendandsil2100, basically you can see the shell from behind the image13:16
sil2100brendand: is it something serious? What do you mean it can be seen?13:16
brendandsil2100, not sure if the corresponding AP test actually fails, i need to look closer13:16
brendandsil2100, more details soon13:16
brendandsil2100, just a heads up that it could be a promotion blocker13:17
sil2100brendand: ok, give me a sign as well if it's serious or not, since small visual glitches shouldn't block us from promoting13:17
brendandsil2100, well okay13:17
alecuhi trainguards! may I ask you what's needed for silo-008?13:23
sil2100alecu: hi! It seems Robert wasn't able to review the changes for that, so now I'll publish it once we build a new image - so in around 1-2 hours13:24
alecugreat, thanks!13:24
=== greyback|lunch is now known as greyback
rsalvetisil2100: we need QA to sign silo 413:26
sil2100rsalveti: theoretically we do not need to, but on the other hand it would be good to double-check nothing is broken13:28
sil2100brendand: can you install silo 4?13:28
rsalvetisil2100: the reason for QA is that we're now finally using trust-store for camera13:28
rsalvetisil2100: so while this is fixing a bug, it's also adding a feature13:28
rsalvetithat was supposed to be validated before, but which wasn't13:29
rsalvetiand that's how we got the bug in first place :-)13:29
sil2100Right ;) So in theory it was supposed to be already QA signed-off13:29
sil2100Anyway, +1 on that in overall13:29
brendandsil2100, yes!13:29
sil2100brendand: are you busy now? We would need this really since we want to land it ASAP ;)13:29
brendandsil2100, om26er is around now as well, but i can certainly give a second pair of eyes13:30
sil2100om26er: pong!13:30
brendandsil2100, it fixes the camera issue?13:30
sil2100brendand: yes13:31
om26ersil2100, don't you mean ping ?13:31
om26er;)13:31
sil2100om26er: ;)13:31
brendandsil2100, i'm on it13:31
sil2100om26er: ok, so brendand is doing the sign-off of silo 4 already, so I guess 2 people on one silo might be a bit too much13:32
Mirvsil2100: landing-015 just finished the qtubuntu part, should QA be testing that too at the same time?13:32
sil2100Mirv: not sure if QA needs to test that, would be enough if the lander tests it13:33
sil2100Mirv: as it's an isolated bugfix for a blocker13:33
rsalvetibrendand: so please test camera-app and osmtouch13:34
Mirvsil2100: ok, if you think so. I was just thinking that any QPA plugin changes may not be as isolated as one would initially think.13:36
brendandrsalveti, with camera app the dialog appears13:41
rsalvetigreat13:42
brendandrsalveti, interesting that the ap tests can pass with that there13:42
Saviqretoad, hey, psivaa directed me at you with some weird behaviour of http://s-jenkins.ubuntu-ci:8080/job/unity-phablet-qmluitests-utopic/ and http://s-jenkins.ubuntu-ci:8080/job/ubuntu-settings-components-qmltests-utopic/13:46
rsalvetibrendand: even before accepting it on the first time?13:47
Saviqretoad, after a restart (?) yesterday, the jobs started timing out (3h for unity, 1h for u-s-c), when normal run takes under an hour for unity, and much less for u-s-c13:47
retoadSaviq, /me looks13:47
brendandrsalveti, you ran them right?13:47
Saviqretoad, the jobs get stuck on generating coverage info13:47
rsalvetibrendand: autopilot? not yet13:47
* Mirv lets device run UITK+U8+calendar AP:s with updated qtubuntu13:47
rsalvetibut I'd imagine that this might break autopilot tests for camera13:47
Saviqretoad, like this one is currently stuck there http://s-jenkins.ubuntu-ci:8080/job/unity-phablet-qmluitests-utopic/826/console13:47
* sil2100 runs calendar app with both silos enabled13:48
sil2100(the AP tests)13:48
brendandrsalveti, i thought tvoss solution was to whitelist camera-app so no dialog is needed?13:48
rsalvetibrendand: silo 4 is the real fix, no whitelist13:48
brendandrsalveti, or is a dialog still needed even with whitelisting?13:48
rsalvetithat's why you got a dialog during first time13:49
sil2100brendand: yeah, it's a full fix now, so the dialog is now visible again13:49
retoadSaviq, ack, will poke to see if I can find anything13:49
rsalvetijust wonder if the dialog could break autopilot on our CI13:49
Saviqretoad, thanks13:49
brendandsil2100, hey wait a minute - camera_app passed this morning ???13:50
brendandsil2100, weird13:50
sil2100brendand: yes, as it had the whitelisting hot-fix in it13:50
sil2100brendand: silo 4 removes that hot-fix and fixes the issue the right way13:50
brendandsil2100, i'm going to check it now but i don't think that will work with autopilot13:51
brendandsil2100, and is the 'right' fix really to always have a dialog asking for location?13:51
cjwatsonInitial RTM copies all done; the derived distros publisher is going to be a bit busy for a while13:51
sil2100brendand: shouldn't it only show it once and then remember? It's not like that?13:52
brendandsil2100, i didn't get that far13:52
brendandsil2100, still the AP tests will probably be broken by it13:52
brendandsil2100, so they might need to be updated to dismiss the dialog13:52
sil2100I hope the lander ran the camera-app tests ;)13:53
tvossbrendand, the user's answer is remembered13:54
rsalveticjwatson: nice13:55
rsalvetitvoss: but what will happen with the autopilot tests during first run?13:55
tvossrsalveti, we will either have to set an env variable to force a testing mode, or preseed the trust database13:55
sil2100We need to poke jhodapp most probably13:55
jhodappsil2100, what's up?13:56
brendandsil2100, should we land this when it's going to re-break the autopilot tests?13:57
brendandsil2100, although i haven't *confirmed* that it does13:57
rsalvetitvoss: right13:57
Mirvsil2100: silo 015 ready for landing build wise. note that I need to shift to EODish mode now, but I'll be checking in.13:57
Mirvgreyback: ^ silo 15 is ready with your branch13:58
tvossrsalveti, but right now, the ap tests don't check for location anyway, and the camera will eventually start (the dialog times out)13:58
rsalveticool, let's try and hope for the best13:58
tvossrsalveti, there is a crash of the trust-stored-skeleton under ap that I'm investigating, too13:58
rsalvetitvoss: oh, ok, would that block the landing?13:59
tvossrsalveti, TRUST_STORE_PERMISSION_MANAGER_IS_RUNNING_UNDER_TESTING is your friend13:59
tvossrsalveti, nope, the ap tests pass all fine13:59
tvossbrendand, TRUST_STORE_PERMISSION_MANAGER_IS_RUNNING_UNDER_TESTING13:59
greybackMirv: thanks. dandrader wants me to change the code, so I'll need a rebuild shortly13:59
rsalvetigreat13:59
tvossrsalveti, set it to 113:59
Mirvgreyback: ok.13:59
kalikianajosepht: can you help rsalveti and I here; getting a strange failure at https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-mako/3207/console where it says "E: Unable to locate package ubuntu-push-notifications-autopilot" the package was intentionally removed from the build and won't exist, but it keeps looking for it for some reason14:00
* brendand hands tvoss the 'longest environment variable name ever award'14:00
rsalvetilol14:00
sil2100brendand, tvoss: so, the camera-app tests should normally pass? Is this variable set during our smoketesting?14:00
brendandsil2100, i don't think so14:00
brendandsil2100, someone probably has to update camera-app14:00
* Mirv pre-bumped the gles branch version number so that it's suitable for rebuild14:01
sil2100greyback: code change? :<14:01
greybacksil2100: just cleaning up, nothing major14:01
sil2100Still, we'll have to re-test it14:01
brendandsil2100, ah tvoss just mentiond the dialog times out14:01
brendandsil2100, that would be okay then14:02
greybacksil2100: prefer I hold off?14:02
greybackand do it later?14:02
brendandsil2100, the problem before was that the window was disappearing14:02
brendandsil2100, so this should be ok14:02
josephtkalikiana: looking14:02
sil2100greyback: how long would the refactor and rebuild take?14:02
greybacksil2100: refactor done, I just need to push.14:03
kalikianajosepht: thx14:03
sil2100greyback: ok, then let's do it14:03
greybacksil2100: ok, pushing14:03
brendandtvoss, when are you planning the fix the fact that the dialog uses the click package name14:03
brendand?14:03
sil2100greyback: once we rebuild the package I'll re-run calendar-app tests14:03
greybacksil2100: ack14:03
sil2100We need to have this silo tested ASAP14:03
brendandsil2100, silo 4?14:04
Kaleosil2100, the calendar thing was the last thing holding us back in TRAINCON?14:04
sil2100brendand: silo 4 is being tested by you, I'm talking about silo 1514:04
brendandsil2100, who's handling silo 15?14:05
sil2100brendand: the lander, but I'm helping out as well14:05
sil2100brendand: e.g. greyback14:05
brendandsil2100, what about from the QA side?14:05
sil2100brendand: theoretically we don't need a QA sign-off for that14:05
brendandsil2100, ok14:05
sil2100But most probably it would be simply faster if someone from QA could help in testing this silo14:06
sil2100om26er: are you busy right now?14:06
brendandsil2100, as soon as these camera tests finish i'll do it - or get om26er on it14:06
sil2100brendand: anyway, we need to wait for the silo 15 to rebuild now anyway14:06
om26ersil2100, not really.14:07
sil2100greyback: did you press rebuild already, or can I do it?14:07
greybacksil2100: I didn't, please do14:07
sil2100om26er: so, once silo 15 rebuilds we would appreciate help in testing it14:08
kalikianajosepht: any ideas? basically we don't want ap for this package, only unit tests - we may add them later but not for the moment14:08
josephtkalikiana: that packages was passed as a parameter to the build job, I can re-run without that package if you'd like14:08
om26ersil2100, ok14:08
kalikianajosepht: if you can remove the parameter, that'd be great!14:08
greybacksil2100: the MR was approved, so we hould be good to go14:20
sil2100Great, waiting for the builds to finish14:21
brendandtvoss, sorry - even though there is a timeout it still prevents AP tests from passing14:26
brendandtvoss, rsalveti - someone will have to fix the AP tests14:26
brendandtvoss, let me try that env variable. what was it again :) ?14:26
rsalvetibrendand: who can work on that?14:27
rsalvetiprobably setting up the env var for now14:27
brendandyeah just setting the env variable works. should be an easy fix. somebody just has to do it14:28
brendandi *suppose* i could :)14:28
popeyhm, screen never goes off, on my flo14:28
rsalvetibrendand: that would be even better14:28
rsalvetipopey: nice14:28
popeyrsalveti: wanna bug filed?14:29
rsalvetiprobably an issue with unity8 + system-compositor14:29
Wellarkstill on TRAINCON-0 ?14:29
Wellarksilo 1 has to wait then14:29
rsalvetipopey: can you run powerd-cli list?14:29
rsalvetiWellark: unfortunately, yes14:29
* Wellark checks the remaining blockers..14:30
popeyrsalveti:   Name: com.canonical.Unity.Screen, Owner: :1.19, State: 114:30
rsalvetiWellark: unless you require QA to signs it off for you14:30
rsalvetipopey: right, then the issue is that for some reason system-compositor + unity8 is not timing out14:30
popeyrsalveti: bug against unity8?14:30
rsalvetipopey: yeah, and system-compositor14:30
popeykk14:31
Wellarkrsalveti: the fixes in silo 1 are minor. no need waste QA power to it at this point14:32
rsalvetipopey: thanks14:32
rsalvetiWellark: got it14:32
WellarkI'm sure they have more important stuff to sign off atm14:32
popeynp14:33
brendandrsalveti, the hardest part is using this environment variable without causing a pep8 error :)14:34
josephtkalikiana: building now14:34
rsalvetibrendand: right14:34
brendandrsalveti, otherwise - MP imminent14:34
sil2100om26er: hi!14:36
sil2100om26er: could you test the packages in silo 15?14:36
om26ersil2100, hello14:36
sil2100om26er: they're built now14:36
om26ersil2100, no test plan ?14:36
sil2100om26er: I'll be now building the -gles counterparts, but those are unrelated to what needs testing on the phone14:36
om26ersil2100, did anyone else test it ? like the developers ?14:36
sil2100om26er: the developers, me and Mirv did some basic testing, but not sure about any official test plan14:37
sil2100greyback: do you have a test plan for qtubuntu?14:37
sil2100(like, written somewhere?)14:38
greybacksil2100: I'm not aware of one.14:38
om26ersil2100, who is the owner of the project ?14:38
sil2100om26er: it should be greyback and ricmm in overall14:39
om26ersil2100, without the testplan I can only test the bug fix. Who is going to take the blame if things break ;-)14:40
kalikianajosepht: awesome! thanks a lot14:40
sil2100I was sure we had a test plan for this14:40
* sil2100 looks for it14:40
sil2100om26er: ok, I see it never had any test plan, just 'exploratory testing'14:42
sil2100A bit worrying for a component that touches so many things14:43
greybackom26er: I can tell you the biggest risk is the input handing change, so please make sure that what you tap actually reacts, and not the thing above/below it14:44
greybackom26er: also make sure the application is filling the screen correctly14:44
om26ergreyback, ok, But I think we should have a testplan for this to test most basic and important things and reliabilities.14:46
greybackom26er: I'm not objecting to that. We just haven't written one14:46
brendandrsalveti, providing this gets landed before, silo004 has my ack: https://code.launchpad.net/~brendan-donegan/camera-app/longest_variable_name_evar_fixes_autopilot_tests/+merge/23012214:47
brendandrsalveti, do i need to update the spreadsheet?14:47
kenvandineare there jenkins problems right now?  All the settings CI jobs are failing, with build time outs14:47
rsalvetibrendand: can we put this in the same silo?14:48
brendandrsalveti, i guess so. i thought click apps were pulled from the store though14:48
sil2100rsalveti, brendand: is camera-app still released through the train? It's a click package now, right?14:48
rsalvetibrendand: indeed14:48
rsalvetiwho can approve/merge and upload that then?14:49
brendandrsalveti, try Kaleo14:49
=== gatox is now known as gatox_lunch
sil2100rsalveti: wait14:49
sil2100rsalveti, brendand: add it to the silo14:49
sil2100rsalveti, brendand: I see Bill and oSoMoN still release the debs before pushing it to the store14:50
rsalvetioh, indeed14:50
rsalvetithen add to the silo14:50
sil2100So we should use the train not to break their workflow14:50
sil2100brendand: is the branch ready for releasing? I'll add it if it is14:50
brendandsil2100, someone needs to review and approve my branch14:51
tvossrsalveti, brendand anything I can help with?14:53
brendandtvoss, review a camera-app branch?14:53
tvossbrendand, shoot14:54
brendandhttps://code.launchpad.net/~brendan-donegan/camera-app/longest_variable_name_evar_fixes_autopilot_tests/+merge/23012214:54
tvossbrendand, mind filing a bug to remove that "hack" with preseeding the database?14:55
brendandtvoss, ? you mean in the test - or in camera-app - or another component14:55
tvossbrendand,  in the test14:56
tvossbrendand, but already approved your branch14:56
brendandtvoss, why not let's do that now? show me the code14:56
tvossbrendand, no code, yet. Have to think throught it, first14:56
brendandtvoss, ok14:56
plarssil2100: I'm not going to be able to make the meeting in an hour, anything urgent for me?14:56
tvossbrendand, it's on my plate anyway, so feel free to file a bug or not14:57
brendandtvoss, i'll file a bug then14:57
tvossbrendand, thanks14:57
sil2100plars: I think we're fine, we'll kick a new image in like an hour probably anyway...14:57
plarssil2100: from our end, balloons was able to get the reminders tests working, so I ran those against the latest image, 18 new passes :)14:58
retoadSaviq, I wasn't able to find anything in the last build and it timed out before I could finish poking around. The VM reset itself and another job kicked off so I am tracking through that one now.14:58
sil2100plars: passes! I like the sound of that ;)14:58
Saviqretoad, ok thanks14:58
plarssil2100: I can make them fail if you like14:58
sil2100plars: those run as autopkgtests?14:58
Saviqretoad, it's kind-of weird as it started happening just after jenkins was stopped14:58
plarssil2100: no14:58
sil2100plars: oh oooh noooo!14:59
Saviqretoad, the jobs before were completing fine14:59
kenvandineretoad, are there jenkins issues?  all my system-settings CI builds are tailing with timeouts14:59
plarssil2100: the autopkgtest stuff still doesn't work. We'll need to spend some more time on that14:59
kenvandineBuild timed out (after 120 minutes). Marking the build as failed.14:59
kenvandinejava.lang.InterruptedException14:59
kenvandineretoad, is that related to what you were talking about?14:59
retoadSaviq, it is indeed weird.14:59
brendandtvoss, https://bugs.launchpad.net/camera-app/+bug/135449115:00
sil2100plars: ok, then it seems balloons liked the idea of working-around it by adding dependencies through the testconfig? ;)15:00
ubot5Ubuntu bug 1354491 in camera-app "autopilot tests need to preseed the trust store" [Undecided,New]15:00
retoadkenvandine, I have no idea what the issue is at the moment.15:00
balloonssil2100, indeed.. the autopkgtest route was being more painful15:00
kenvandineretoad, but there is an issue?  it's not specific to my stuff right?15:00
balloonswe still need to finish it, but for now reminders needed to get running15:00
retoadkenvandine, yes there does appear to be an issue.15:01
kenvandineok, i'll stop spinning my wheels then and let the experts figure it out :)15:01
kenvandineretoad, thanks!15:01
balloonsplars, I see those tests were skipped, that explains the quick runtimes. Need to push a new version of reminders to the store which should let all those run15:05
balloonsstore is slightly old15:05
KaleoI don't see any update on https://bugs.launchpad.net/camera-app/+bug/1353956 (nor on https://bugs.launchpad.net/qtmir/+bug/1352977), I trust it's being worked on though?15:08
ubot5Ubuntu bug 1353956 in camera-app "Camera takes a long time to launch (30+ seconds) and disappears from view" [Critical,Confirmed]15:08
ubot5Ubuntu bug 1352977 in QtMir "Creating a prompt session for an app without a surface does not show the prompt" [Critical,In progress]15:08
sil2100Kaleo: it's being tested by QA right now15:08
Kaleosil2100, cool15:09
sil2100Kaleo: actually, it has been tested more or less, with an additional fix finishing right now15:09
Kaleosil2100, great15:09
sil2100greyback: btw. could you top-approve the qtmir branch from dednick ?15:09
Kaleosil2100, so that was the last blocker to exiting TRAINCON?15:09
brendandrsalveti, should i expect osmtouch to get the location eventually?15:09
sil2100Kaleo: there's the date-time picker that's also tested right now15:09
Kaleoyes15:09
brendandrsalveti, it's not working atm is it?15:10
greybacksil2100: done15:10
sil2100greyback: thanks :)15:10
dednicksil2100, greyback: need the unity8 branch MR'd as well.15:12
sil2100Indeed15:13
greybackdednick: have people functional tested it from the silo?15:14
sil2100The packages are built already, so once someone approves the merge and we get a +1 from brendand15:14
greybackdednick: I'm reviewing it now code-wise anyway15:14
dednickgreyback: yeah. tvoss has tested against the bug.15:15
* sil2100 thinks some things are happening a bit out-of-order15:15
sil2100Usually I prefer when the merge is already approved before we test the silo and sign it off ;)15:15
brendandsil2100, +1 from me - do i need to put that in the spreadsheet?15:16
sil2100\o/ Yeah15:16
Mirv\o/15:16
om26ersil2100, can you change the status of 'testing pass' to yes15:18
ogra_so where is the image !15:18
om26ersil2100, I will then approve it. seems to work fine for me.15:18
sil2100om26er: \o/15:18
sil2100om26er: done15:18
sil2100om26er, brendand: thanks guys!15:18
greybackwoo!15:21
sil2100greyback: so, how's the review? ;)15:22
greybackom26er: sil2100: brendand thank you for your help15:22
greybacksil2100: I'll need time, it's not a small change15:22
* greyback feels like the bottleneck15:22
sil2100om26er: switch qa-sign-off to yes once you have a moment ;)15:22
om26ersil2100, yes in a few, testing one last thing.15:23
=== om26er is now known as om26er|dinner
sil2100\o/15:30
sil2100PUBLISHING!15:30
popeyʘ‿ಠ15:32
sil2100Now just the review from greyback, no pressure o/15:32
greyback:P15:32
greybacksil2100: if dednick's stuff has been functional reviewed by someone else, I'm happy to approve that MR15:37
rsalvetioh15:37
rsalvetibrendand: yeah, that bad behavior is known :-)15:38
rsalvetisorry, was on a call15:38
sil2100greyback: I think tvoss did a functional review ;)15:38
greybacksil2100: very well, marking approved15:38
rsalvetigetting closer to a promotable image15:38
sil2100greyback, tvoss, dednick: thanks guys for all the hard work, silo 4 is now landing as well15:41
sil2100Once those migrate, and it will take a while, we'll have an image kicked15:42
pmcgowanyay15:42
greybackcool15:42
sil2100I would still consider promoting an image today, so when the image gets built we'll ask ToyKeeper or om26er|dinner to perform promotion dogfooding15:42
rsalvetiyeah15:43
retoadSaviq, how long does the coverage generation usually take? In the current job I am monitoring http://s-jenkins.ubuntu-ci:8080/job/unity-phablet-qmluitests-utopic/828/console it has gotten to that point. I see the process on the slave node and the empty file that is created for the output but nothing ever makes it into the file. At this point it looks like it has nothing to do with the jenkins server but something to do with gcov15:46
retoadr (which is the same issue we're seeing on other slave nodes; gcovr hanging forever).15:46
=== gatox_lunch is now known as gatox
Saviqretoad, it should be seconds15:46
Saviqretoad, so it does indeed suggest gcovr is b0rked15:46
Saviqretoad, let me try around her15:46
retoadSaviq, I will try running ti by hand to see what it spits out15:46
retoadSaviq, the command works whe run from the CLI (not tested within the chroot environment though).15:52
retoadSaviq, doesn't seem to be that gcovr is borked. Works well when called directory from the CLI. Also works when called through cmake (as the job does) when using a .cmake file that includes the full system path (again, not chrooted) to the build.15:59
camakojosepht, we still in TRAINCON-0? (Sorry, was travelling, and trying to catch up on email).16:01
ogra_yes16:02
ogra_travel more ... then we'll be out16:02
Saviqretoad, wonder what is causing it to hang in jenkins then... lack of tty or something?16:02
retoadSaviq, no idea atm, am running same tests in chrooted environment now16:02
=== josepht changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | CI Train support: trainguards | Vanguard (general help): cihelp | CI Train Status: #157 promoted | CI Train Dashboard: http://bit.ly/1mDv1FS | Known issues: Forceful TRAINCON-0! Please work together on getting all blockers resolved.
retoadSaviq, and it appears that gcovr hangs when being run from within the chrooted environment. Digging deeper the version of gcovr being run within the chrooted environment (v3.1)  is different that what is installed on the host system (v2.4 r2774) so it is possible that gcovr is b0rked.16:17
popeyballoons: might need you a bit later to upload camera-app as sil2100 has some fixes landing16:17
balloonssure, just ping16:17
popeyta16:18
plarsballoons: ah, ok. Why would they show up as passed then?16:20
elopiook, we have screenshots of the makos!16:20
plarselopio: nice!16:20
elopioit's still a little hard to see them, but I'm seeing one.16:20
balloonsplars, the dashboard showed everything correctly. Anyway, we pushed the updated version, so the next run will reflect everything16:23
plarsballoons: ok, great16:23
=== om26er|dinner is now known as om26er
om26ersil2100, which image needs testing16:25
Saviqsil2100, ugh, what's that https://ci-train.ubuntu.com/job/landing-011-1-build/150/console ?16:25
sil2100om26er: none yet ;) But 179 will need testing once it's built!16:26
sil2100Saviq: it means that someone released something to distro and didn't merge it into trunk yet16:27
Saviqsil2100, huhuh16:27
sil2100Saviq: ah16:27
sil2100Saviq: we're releasing unity8 right now16:27
Saviqsil2100, ah that thing, need to wait for it to migrate then16:27
sil2100Saviq: it was part of the location-service qtmir bug16:27
sil2100Yeah...16:27
sil2100Might take some moments ;/16:28
Saviqsil2100, that's ok, just didn't know what's happening16:28
=== dpm is now known as dpm-afk
* sil2100 gives autopkgtests on unity8 an evil eye16:46
greybacksil2100: could we get silo2 included?16:49
sil2100greyback: where?16:52
greybacksil2100: well, could it be landed, or you prefer wait until traincon lifts?16:52
sil2100I would prefer not including anything new before we get this image16:53
sil2100\o/16:53
greybacksil2100: ok16:53
sil2100Ok, let me merge and clean this silo, wait a bit and then build a new image16:53
Wellarkumm.. what is going on here...16:53
Wellarkhttps://jenkins.qa.ubuntu.com/job/indicator-network-utopic-amd64-ci/31/console16:53
sil2100robru: if anything I'm still around so I'll kick a new image once it's possible16:53
WellarkBuild timed out (after 120 minutes). Marking the build as failed.16:53
robrusil2100, ok16:53
sil2100(we need to make sure that all components are really in)16:53
pmcgowanWellark, that may be the gcovr issue the guys have been looking into17:03
infinityrobru: Did you get your ACKs sorted yesterday?  I was off and nowhere near a computer.17:04
robruinfinity, no, looks like it still needs it: https://ci-train.ubuntu.com/job/landing-008-2-publish/71/artifact/packaging_changes_pay-service_2.0.0+14.10.20140807.1-0ubuntu1.diff17:05
Wellarkpmcgowan: ok. yes, gcovr that gets stuck17:06
Wellarkso it's a known issue17:06
Wellarkand more importantly, it's not my fault17:06
Wellark;)17:06
infinityrobru: Looking.17:06
robruinfinity, thanks17:06
infinityrobru: Looks reasonable.17:08
robruinfinity, thanks17:08
=== alan_g is now known as alan_g|EOW
sil2100(we need to make sure that all components are really in)17:17
sil2100ugh, wrong window17:17
rsalvetisil2100: did someone upload the camera-app click to the store?17:19
sil2100balloons: could you build an upload the new camera-app?17:19
sil2100balloons: popey should still be around to review it17:19
balloonsaye aye17:19
sil2100balloons: thanks!17:19
=== nik90 is now known as nik90|Dinner
robrusil2100, looks like everything is in. are we just waiting for the new camera-app click then?17:24
sil2100robru: yes, let's wait for that for a little bit and then kick a new image17:24
robrusil2100, ok, sounds good17:24
sil2100balloons: give us a sign once it's there :)17:25
popeysil2100: i am17:27
balloonsgonna be a bit on the build, things are queued17:28
popeyk, no worries, I'll keep checking in17:29
=== boiko_ is now known as boiko
=== ricmm is now known as ricmm_
=== ricmm_ is now known as ricmm
sil2100Just hope it won't take much longer17:47
=== om26er_ is now known as om26er
sil2100balloons: still building?17:53
sil2100Damn, this takes forever18:08
sil2100balloons: it looks as if we're missing free executors on http://s-jenkins.ubuntu-ci:8080/job/generic-click-builder-utopic-armhf/18:10
nik90|Dinnersil2100: you are looking to send that happy email that we are out of TRAINCON, arent you :P18:12
ogra_we all do18:12
sil2100Yes :|18:12
sil2100And things are getting in my way!18:12
Wellarksorry, could not resist: https://i.imgflip.com/ayxp5.jpg18:12
Wellark<318:12
nik90|Dinnerlol18:13
=== nik90|Dinner is now known as nik90
Wellarksil2100: you have our full support. just keep cool and things will work out in the end :)18:13
=== Ursinha is now known as Ursinha-afk
balloonssil2100, yes it's backed up18:15
sil2100hahah ;)18:15
* nik90 imagines sil2100 as Gru with us as the minions (Despicable Me)18:16
* ogra_ goes afk for a while again ... looks like this will take longer18:16
sil2100hm, ok18:17
sil2100ogra_: before you go18:17
sil2100ogra_: I'm thinking about kicking an image right now - camera-app tests will fail, but the app will work fine18:17
sil2100And we know they pass because we ran the tests ourselves even18:17
sil2100ogra_: what do you think?18:18
pmcgowansil2100, why will they fail if you ran them ok?18:19
sil2100pmcgowan: an environment variable needs to be set, that's what the new camera-app basically does18:19
sil2100It sets a test environment variable which is required to skip one dialog at start18:20
sil2100WIthout it the tests fail, but we ran them with the branch already18:20
pmcgowanseems worth building and blessing to me18:20
pmcgowanunless its easy to add something to make them pass18:20
sil2100We just have to release the new click package, btu this seems to be stuck now18:21
sil2100And I don't see any merit in waiting just for a test fix (if we know the tests are passing currently)18:21
pmcgowansil2100, so new camera click package has the fix bit its not available?18:21
pmcgowanwhy is the click stuck? sil210018:22
pmcgowansorry to rehash what you probably discussed18:22
sil2100pmcgowan: exactly, the camera click package that adds setting this env variable at beginning of a test is still building - seems like there are no available executors right now18:22
sil2100balloons mentioned something there's a lot of other things queued up18:22
pmcgowandamn that murphy18:23
kenvandinepmcgowan, murphy has been around all week18:23
kenvandinesil2100, if there is still that problem of gcov hanging the builds in CI, we can probably go through and kill a bunch that we know won't finish18:24
kenvandinelike i think there are 4 jobs running for settings now18:25
sil2100kenvandine: could you poke some people about that?18:25
kenvandineand they just keep timing out after 2 hours18:25
sil2100plars: hi, maybe you could help us out?18:25
kenvandinei think retoad is looking into the hang18:25
plarssil2100: I'll try, what's up?18:25
kenvandinebut i can kill all the settings jobs now18:25
kenvandineshould free some up18:25
sil2100plars: we need a way to get  http://s-jenkins.ubuntu-ci:8080/job/camera-app-ci/251/console finishing18:25
sil2100plars: it seems that it can't do the last step because of not enough executors...18:26
kenvandinesil2100, i kill the 3 settings jobs18:27
kenvandine+ed18:27
retoadkenvandine, am looking to some degree. One problem I have found is that gcovr seems to be having problems. v3.1 just hangs and never returns results.18:27
kenvandinesil2100, i killed everything i feel comfortable killing, hopefully that will free up some and reduce the queue a bit18:30
kenvandinei know they will just hang for 2 hours18:30
sil2100kenvandine: thanks!18:30
plarssil2100: it looks like one of them is offline, but I'm not sure why. I haven't played with the claxeda pbuilders any18:30
kdubhttps://jenkins.qa.ubuntu.com/job/mir-mediumtests-builder-utopic-armhf/184/console18:30
kenvandineretoad, any idea who to talk to about gcovr?18:30
plarssil2100: let me dig at it a bit more18:30
kdub^^is that message an out-of-space on jenkins message?18:31
retoadkenvandine, specifically no. I did mention it to Saviq earlier though18:31
plarsretoad: or is this the same thing you are looking at?18:31
plarsretoad: looks like you disabled the cyclops-node12 one18:31
retoadplars, I have been poking at quite a few things. cyclops-node13 was almost out of space earlier so I cleared that one up and yes, am working on node12 now.18:32
retoadplars, one thing that I have noted is that gcovr (v3.1) in the chrooted environment of all the pbuilder tests just hangs and never returns results.18:33
retoadwhich, in turn, leads to test failures.18:33
plarsretoad: this is on the calxeda pbuilders?18:34
retoadplars, calxeda, genie, kinnara, the VMs on naartjie18:34
retoadetc ...18:34
plarssil2100: unless what retoad is talking about it will block them, it looks like it's just really busy right now18:34
plarsretoad: where did the update come from?18:34
retoadplars, idk, haven't tried to dig through any of the code.18:35
plarsretoad: I mean, did someone tell it to use that version, or was it just automatically pulled in because there was a new package?18:35
retoadplars, I know on the VMs v2.4 is installed on the systems but the chrooted env doesn't use the systems version18:36
robrusil2100, i have some spare cycles, anything I can do to help?18:36
retoadplars, on the calxeda nodes it isn't even installed at the system level so it must be told to install it somewhere.18:36
tvosssil2100, around?18:51
pmcgowanhe may have just left18:53
pmcgowanwe were debating the merits of waiting for the camera with the test fix or just making an image18:53
pmcgowansince there seems to be builder contention18:53
pmcgowantvoss, robru ^^18:54
robrupmcgowan, it seems like a reasonable plan to me. if we know the app is working but just the test itself will fail, why not build an image?18:54
tvosspmcgowan, are you referring to the trust fixes?18:54
pmcgowanrobru, right that was sil2100 proposal/question18:54
pmcgowantvoss, yes18:55
robrupmcgowan, should we do it?18:55
pmcgowanright now the AP will fail but we know why and its fixed18:55
pmcgowanhey I want off of traincon18:55
robrupmcgowan, ok I'm gonna trigger it18:56
pmcgowanrobru, check http://s-jenkins.ubuntu-ci:8080/job/camera-app-ci/251/console18:56
pmcgowanto see if its moving?18:56
robrupmcgowan, i'm having trouble getting on the vpn, can you pastebin that for me?18:56
tvosspmcgowan, would we promote that image?18:57
pmcgowanrobru, http://pastebin.ubuntu.com/7991081/18:57
pmcgowanstill working it seems18:57
pmcgowantvoss, yes aiui18:57
robrupmcgowan, does it seem like it'll finish soon?18:57
robrui'm not sure how long that job takes18:57
kenvandinei'd love to get off traincon-0!18:57
pmcgowanrobru, I dunno where it was at earlier18:57
robrueither do i18:58
tvosspmcgowan, then we should wait for the fix. Otherwise, people using that promoted image and updating the camera app would suffer from the trust prompting issue18:58
pmcgowantvoss, I thought the fix was only for the env var for tests?18:58
tvosspmcgowan, oh ... not sure, I thought both landed together in one silo18:58
tvossrsalveti, can you shed some light here18:58
tvoss^18:58
pmcgowan<sil2100> pmcgowan: exactly, the camera click package that adds setting this env variable at beginning of a test is still building - seems like there are no available executors right now18:59
pmcgowan<sil2100> We just have to release the new click package, btu this seems to be stuck now18:59
pmcgowan And I don't see any merit in waiting just for a test fix (if we know the tests are passing currently)18:59
pmcgowantvoss, and I am unclear if the job will hang because of the other issue with gcovr19:00
tvosspmcgowan, okay, then I'm +1 on building an image19:00
pmcgowanolli, rsalveti robru ok ?^^19:01
robrupmcgowan, ok, i'll do it19:01
robrutvoss, yeah, the *silo* landed, just the camera click-app isn't in the store yet19:02
tvossrobru, okay19:03
pmcgowanthat job indicates its like 90% done if that progress can be trusted19:03
robrupmcgowan, ok I kicked a build. worst case, the next image built by cron (~8hrs) will have the click app.19:04
robruToyKeeper, when you get online, image 179 should be ready for you to dogfood, it's a promotion candidate ;-)19:05
sil2100o/19:08
sil2100robru: thanks :)19:08
sil2100I'm still around, but AFKish19:08
robrusil2100, if you're AFK are you really around? if you don't respond to messages, can you even be said to really exist? ;-)19:08
sil2100I... I..!19:09
imgbot=== trainguard: IMAGE 179 building (started: 20140808 19:10) ===19:09
ToyKeeperThat explains a lot...  I was wondering how I had missed the bot's pings about it.19:10
pmcgowanrobru, that job actually finished but it failed the final step19:12
robrupmcgowan, erk19:13
pmcgowanrobru, it confuses me though19:13
pmcgowanseems to say it published19:13
robruToyKeeper, oh, are you up early? I wasn't expecting you till later. maybe I'm time-confused.19:13
pmcgowananyone can look at http://s-jenkins.ubuntu-ci:8080/job/camera-app-ci/251/console to see whats up19:14
ToyKeeperrobru: I just have weird hours.19:15
popeyrobru: pmcgowan the next image wont have camera app unless someone (balloons) uploads it to the store and someone else (me) approves it...19:16
pmcgowanpopey, hey I just work here19:17
balloonslol19:17
robrupopey, yeah, the idea seems to be that the updated camera app just had AP fixes, nothing user-visible.19:17
popeyok19:17
pmcgowanbut the one from the silo we need19:17
balloonspopey, sil2100 camera app is STILL waiting believe it or not19:17
robrupopey, so we're hoping in theory that image 179 is promotable despite camera-app AP failures.19:17
pmcgowanpopey, balloons I think we may need to upload a new camera19:17
popeywe cant till the click builds19:18
pmcgowanas the silo landing was the deb to the archive right?19:18
balloonswe could build the click locally, that's the only other option.. or punt some jobs19:18
pmcgowanok I dont know then if the previous one made it through19:18
pmcgowanpopey, balloons if you didnt upload that means no one did?19:18
robrupmcgowan, yes the silo landing was just debs to the archive.19:18
popeynobody has yet19:19
popeylast camera update in the store was 2 days back iirc19:19
pmcgowanwell then19:19
pmcgowancrap19:19
popeyhttp://s-jenkins.ubuntu-ci:8080/job/camera-app-click/ being the thing we're waiting on19:20
pmcgowanpopey, what I dont know is whether the diff between 108 and 109 there is just the testing fix19:21
pmcgowansil2100, ?^19:21
pmcgowanpopey, in which case the 108 package would be good enough19:22
popeythat and a couple of translations19:22
popeythe store has r34219:22
balloonsmight free up soonish.. 4 nodes are being used by unity8 and they are in the results part19:23
sil2100We kicked an image now anyway, so the camera-app fails will be failing for this image on smoketesting19:24
sil2100But the application itself is completely fine19:24
pmcgowansil2100, the one from the store?19:24
sil2100pmcgowan: the one that's in the store right now19:24
pmcgowanok great19:24
sil2100pmcgowan: it's just a matter of tests being broken - broken in a known way, so no worries here19:25
pmcgowanpopey, balloons seems we are good, but will want that next one loaded when its done19:25
popeyk19:25
sil2100Can't wait for the image to finish building19:26
popeysil2100: we expecting to dogfood this image and hope to promote?19:27
sil2100popey: yes19:27
sil2100popey: as it has all the fixes we want (only missing the click camera-app with the AP test fix)19:28
balloonscamera app is building now :-)19:28
popeyis ToyKeeper lined up to dogfood?19:30
sil2100popey: she got pinged by me and robru19:30
popeyk19:30
sil2100Can't wait!19:30
popeyETA 20:40 UTC ish?19:31
=== cprov changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | CI Train support: trainguards | Vanguard (general help): cprov | CI Train Status: #157 promoted | CI Train Dashboard: http://bit.ly/1mDv1FS | Known issues: Forceful TRAINCON-0! Please work together on getting all blockers resolved.
robrupopey, i don't have a UTC clock handy, but I'd expect the image to finish building within an hour19:37
ToyKeeperI'll try to get back ASAP, anyway...  hopefully around the time the build finishes.19:43
popeyrobru:  date -u19:43
robrupopey, what, you mean i have to open a terminal?? ;-)19:43
popeyno19:43
popey /exec -o date -u19:44
popeyFri Aug  8 19:44:04 UTC 201419:44
robru(alternate response) popey, I'm flattered but I'm in a relationship already.19:44
popeygood, it was "minus you"19:44
robruoh ok19:44
robruFri Aug  8 19:45:04 UTC 201419:45
robruoh look at that19:45
popey\o/19:45
robruDesktop19:45
robruDocuments19:45
robruDownloads19:45
robrumissed-#ubuntu-ci-eng.txt19:45
robrumissed-#ubuntu-touch.txt19:45
robruMusic19:45
robrupbuilder19:45
robruPictures19:45
robruProjects19:45
robruPublic19:45
robrusemordnilap.py19:45
robrusrc19:45
robruTemplates19:45
robrutodo.txt19:45
popeyhahah19:45
popeythat was brave, could have gone badly wrong there19:45
popey.19:45
popey..19:45
popeygoat_porn19:45
robruyeah pwd would have been smarter than ls. wasn't sure what the active directory was19:46
robrupopey, no the goat porn is on my other laptop, so it wasn't that brave19:46
balloonspopey, https://myapps.developer.ubuntu.com/dev/click-apps/506/changerequest/19:54
balloonscamera app is uploaded19:54
popeyapproved19:55
popeyso it could sneak into this build...19:55
racarrrobru: You asked about https://bugs.launchpad.net/ubuntu/+source/android/+bug/1351097 so maybe you are tasked with chasing it down? I don't know. Just wanted to let you know I've posted a patch19:57
ubot5Ubuntu bug 1351097 in unity8 (Ubuntu) "[emulator] bottom edge swipe broken" [Undecided,Confirmed]19:57
robruracarr, oh thanks19:57
robrusil2100, still around? ^19:57
alecuhi trainguards! any ETA for landing of silo 008? (pay-service)19:58
alecuwill that come after next image is built?19:58
robrualecu, yeah I can probably kick that now, we should be far enough into the build that it's safe to publish19:58
=== Ursinha-afk is now known as Ursinha
alecugreat!20:00
sil2100robru: yeah, around20:02
sil2100robru: what's up?20:02
robrusil2100, racarr mentioned having a workaround for that bottom-edge-swipe-emulator issue20:03
sil2100racarr: excellent \o/20:03
sil2100racarr: thanks!20:03
sil2100As per discussions with olli we decided to whitelist this issue for this particular promotion20:03
robruracarr, can you take your pastebin and submit a branch for that?20:03
sil2100But it would stay as a blocker for the other20:03
* rsalveti back20:04
robrubrb, lunch20:05
rsalvetiI'll check his workaround and push it if it works properly20:06
rsalvetiseems we're still waiting for the new image to show up20:07
* sil2100 pokes imgbot with a stick20:13
racarrsil2100: To ubuntu/android?20:19
racarras distro patch20:20
racarrhmm20:26
racarrubuntu/android has many less distro patches than apt-get source android20:26
rsalvetiracarr: I can take care of that package patch once I'm done with my tests20:28
racarrrsalveti: Sounds good :) lemme know if there are any problems20:28
rsalvetiracarr: sure20:29
rsalvetithanks20:29
sil2100racarr: yeah, best to consult with rsalveti ;)20:33
sil2100It's taking a bit longish to get this image built20:41
imgbot=== trainguard: IMAGE 179 DONE (finished: 20140808 20:45) ===20:44
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/179.changes ===20:45
robruwoop woop!20:45
popeywoop woop!20:45
sil2100\o/20:45
ToyKeeperThat was only 5 minutes late.20:45
sil2100ToyKeeper: can we ask you for dogfooding #179 promotion-wise?20:45
ToyKeepersil2100: Already flashing it.20:45
sil2100ToyKeeper: thank you :)20:45
ToyKeeperCancelled my other plans.20:46
* olli crosses fingers20:46
popeyawww, camera didnt make it20:46
sil2100popey: sadly20:46
robruhmmmm, is there a delay before it becomes available for krillin? usually I can flash as soon as the bot pings but just now i got 178...20:46
robrunm20:48
rsalvetirobru: ping janimo20:56
robrursalveti, nah it was just like a 1m delay, it's fine20:56
rsalvetioh, great, maybe he's already automatically importing everything20:56
robruToyKeeper, popey: erk, uh, flashing 179 and then updating camera-app seems broken. like camera-app won't launch21:07
sil2100Impossible21:08
sil2100Blasphemy21:08
ToyKeeperIs that a blocker for the image, or just a broken app update that needs to be fixed?21:10
sil2100I don't know21:11
sil2100Depends if it's confirmed to be broken for others21:11
rsalvetiwe tested the silo for sure21:12
sergiusensrobru: camera from click?21:12
sil2100Yes, and it shouldn't be broken as there is no logical reason for it to be broken21:12
sil2100If, of course, we didn't pull in some other changes along with the AP fix21:12
sergiusenssil2100: there is a reason for it to be broken if abi or api was broken and the click framework wasn't bumped21:12
sil2100sergiusens: it was not21:13
sergiusensthen it should be good21:13
sil2100sergiusens: we didn't land anything that should have broken ABI, there were no UITK or similar uploads... all changes were purely from the backend21:13
* sergiusens flashes21:13
ToyKeeperWell, "settings -> accounts -> back" still crashes and leaves the settings app unresponsive.21:15
sil2100ToyKeeper: that's a known bug, but not marked as a blocker21:15
sil2100ToyKeeper: it's on the 'visible issues' page though21:15
popeyfyi camera opens with 179 _without_ updating camera from store21:17
* popey updates the app21:17
popeyconfirmed it fails to launch after updating21:19
sergiusenspopey: upstart logs for camera say anything?21:19
popeyapparmor denials21:19
rsalvetidid the trust-store dialog worked at least?21:19
popey[Fri Aug  8 22:16:56 2014] type=1400 audit(1407532617.491:129): apparmor="DENIED" operation="open" profile="com.ubuntu.camera_camera_3.0.0.342" name="/dev/fb0" pid=4707 comm="camera-app" requested_mask="rw" denied_mask="rw" fsuid=32011 ouid=021:19
rsalvetidownloading and will test21:19
sergiusensugh21:20
sil2100wtf21:20
rsalvetithis is expected21:20
rsalvetiknown and always was there21:20
sil2100Ah, k21:20
sergiusenscheck ~/.cache/upstart/*camera*.log21:20
popeythere isnt one21:21
popeycom.ubuntu.camera3.0.0.34721:21
popeythats the version I have, and the only camera app log is for r34221:21
=== cprov changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | CI Train support: trainguards | Vanguard (general help): cihelp | CI Train Status: #157 promoted | CI Train Dashboard: http://bit.ly/1mDv1FS | Known issues: Forceful TRAINCON-0! Please work together on getting all blockers resolved.
* popey reboots phone21:22
cjwatsonSetting up proposed-migration for ubuntu-rtm/14.09 now so that I can get a new ubuntu-keyring in so that I can build images21:22
cjwatsonI've flushed out all the old data from the dogfood run21:22
popeyworks after a reboot ToyKeeper21:24
sergiusensUbuntuClientIntegration: connection to Mir server failed. Check that a Mir server is21:24
sergiusensrunning, and the correct socket is being used and is accessible. The shell may have21:24
sergiusensrejected the incoming connection, so check its log file21:24
sergiusensthat's why21:24
ToyKeeperpopey: Thanks.  Usually one of the first things I do is disable updates, so it won't change versions on me mid-test.21:24
sergiusensrsalveti: try and updating the camera before launching it for the first time21:25
sil2100popey, sergiusens: thanks for checking this out21:25
sergiusensrsalveti: if you haven't finished flashing yet21:25
rsalvetistill flashing21:25
rsalvetiso this updating issue might be different21:25
sergiusensdoes the trust store cache the state of the decision and bind it to a full app_id?21:26
sergiusensrsalveti: I bet it's a state issue21:26
rsalveticould be, question and bug for tvoss21:26
sergiusensso any app that is updated will fall into this potential problem21:26
sergiusenswhich uses this code path of course21:26
sergiusenswhich is not "all" apps21:27
sil2100When landing the trust-store update recently we didn't test how it reacts to app updates, so yeah...21:27
ToyKeeperWell, that's an issue...  after merging a couple calls and then hanging up, one of the callers was still active on the other side.21:27
robrusergiusens, yeah, updating the camera app from the click store stops it being able to launch. i'll reflash to confirm...21:27
sergiusensrobru: well if you reboot it works; it should only fail if you launched the previous one and accepted the access in the pompt21:28
sergiusenstheory still though21:28
robrusergiusens, wasn't prompted for anything21:29
rsalvetiyeah, reverting was definitely the best option here21:29
sergiusensrobru: not even the first time?21:29
robrusergiusens, nope21:29
rsalvetiso many issues with this landing21:29
sergiusensrobru: that's strange too21:29
sil2100Indeed... the scary thing was that it was signed off by QA, so even this doesn't completely protect us from issues21:32
sil2100robru: anyway, it was confirmed that a reboot helps21:32
robrusergiusens, sil2100: yeah, reflashing 179, the camera-app that comes with it prompts for location access and works.21:39
ogra_sil2100, the camera smoke test doesnt look so great either21:41
ogra_(i assume that is because there is no test handling of the promot ? )21:41
ToyKeeperWell, it still produces black images with the flash...21:41
sil2100ogra_: that's known21:42
sil2100ogra_: see backlog, but in short: the fix for this is in the store21:42
ogra_right21:42
sil2100ogra_: we didn't want to block the image build on the click package taking ages building21:42
ogra_yep, i see the backliog21:43
rsalvetiflashed, updated, can't open app21:51
rsalvetieven without trying it before21:51
rsalvetilemme reboot21:52
ToyKeeperOkay, had a couple issues I couldn't reproduce more than once...  the "settings -> reset" option took a few taps to launch, and before that it just toggled the button on and off at each tap.  Even stayed depressed when I went to another setting group and back.21:52
ToyKeeperThe other was that hanging up on a merged call left one line open (on the other end only, no audio transfer, no sign of an ongoing call on the UT phone).21:53
ToyKeeperSettings -> Accounts -> Back still crashes and leaves the settings app unresponsive...  known long-standing issue.21:54
ToyKeeperI was asked twice to allow location access when going to google maps...  and the second one was shown as "an unconfined application".21:54
ToyKeeperAnd the app store still forgets what to display when the user changes views and back mid-install.  It shows "Install" instead of the install status.21:55
ToyKeeperHowever, the location indicators no longer uncheck themselves, and the music app can finally accept parameters from the dash again.21:55
rsalveti"an unconfined application" is unfortunately expected21:56
rsalvetiso is the click name in camera-app21:56
rsalvetiinstead of the app name21:56
ToyKeeperThe date/time picker in the calendar still doesn't work.21:57
rsalvetiyeah, so no promotion still21:58
ToyKeeperThat was the only current blocker I noticed.21:58
ToyKeeperWe can't promote with that?  :(21:58
rsalvetiwell, not my call21:58
rsalvetisil2100: robru: ^21:59
sil2100ToyKeeper: huh?21:59
sil2100ToyKeeper: why?21:59
sil2100ToyKeeper: we tested, 3 people tested it and it worked21:59
ToyKeeperThe last I heard was:21:59
ToyKeeper** Date & Time picker is not working on device.21:59
ToyKeeperhttps://bugs.launchpad.net/bugs/135102421:59
ToyKeeper -> Seems like the issue has been caused by the QtCompositor landing.21:59
ToyKeeperFix might take some time sadly, we might have to consider working around21:59
ToyKeeperit in case it takes too long.21:59
sil2100ToyKeeper: did you swipe down the keyboard?21:59
ubot5Ubuntu bug 1351024 in Ubuntu UI Toolkit "Date & Time picker is not working on device." [Critical,In progress]21:59
ToyKeepersil2100: Oh, I see.  It was behind the keyboard.22:00
sil2100ToyKeeper: yes, it was like this in the last promoted image as well22:00
ToyKeeperIf that's considered "working", I can live with that.  :)22:00
sil2100ToyKeeper: not a regression anyway ;)22:00
sil2100;p22:00
rsalvetiso no real blocker it seems?22:01
sil2100It's certainly something we'd want to get fixed, but since it was like this already, we didn't want to block on it22:01
sil2100ToyKeeper: checked your list, mostly non-critical issues I see there22:02
sil2100ToyKeeper: does this mean a +1 from the dogfooding side :D ?22:02
ToyKeeperAt least with a quick set of tests, yes.22:02
ToyKeeperI'm sure I could find a dozen more issues if I keep poking it.22:02
popeythe date picker one is in progress22:03
ToyKeeperAnyway, none of yesterday's blockers seem to be present.22:03
sil2100ToyKeeper: so, are you giving us a green light on promoting this image?22:03
ToyKeeperGo for it.  Nothing seems to be exploding.  :)22:04
sil2100ToyKeeper: I feel I need to hug you!22:04
* sil2100 hugs ToyKeeper 22:04
* ToyKeeper explodes22:05
jdstrandpopey: that denial is known, harmless and just noise. the next update will silence it22:05
ToyKeeperHmm, I seem to have a bug.22:05
sil2100Ok, I'll just check the smoketesting still-running results22:05
* rsalveti off for dinner, bbl22:05
sil2100ogra_: ok, so far the smoke test results look similar to 178, so I think it's time to just promote (tm)22:06
sil2100ogra_: could you promote image #179 ?22:06
ToyKeeperHmm, my screen hasn't shut itself off since I stopped poking it a few minutes ago.22:06
rsalvetipopey: had that earlier today22:06
rsalvetihttps://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/135447322:07
ubot5Ubuntu bug 1354473 in unity8 (Ubuntu) "Flo display never times out #178" [Undecided,New]22:07
popeynot seen it on mako22:07
ToyKeeperThis was on mako.22:07
* popey unplugs and leaves phone alone to test22:07
popeydimmed22:08
ToyKeeperIt was still plugged in though.22:08
popeylocked22:08
ToyKeeperHmm, still not shutting itself off even while unplugged.22:11
ToyKeeperSeems similar to an issue I had long ago but could never trigger on purpose...  except the proximity sensor doesn't blacken the screen now.22:15
ToyKeeperProbably the same bug, just hard to nail down.22:15
popeysame here22:15
popeyit does when dialer app is open22:15
ToyKeeperYeah, or when it has been open at least...  doesn't need to still be open.22:16
ToyKeeperAnyway, biab.22:16
sil2100Thanks everyone22:17
sil2100ogra_: anyway, please promote #179 at all costs22:18
sil2100I am sending out the ANN's about that now since it's late and I have an early wake up tomorrow22:18
=== sil2100 changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | CI Train support: trainguards | Vanguard (general help): cihelp | CI Train Status: #157 promoted | CI Train Dashboard: http://bit.ly/1mDv1FS | Known issues: -
sil2100ogra_, robru: could you guys update the topic (image promoted part) once the actual promotion happens?22:23
sil2100robru: keep poking ogra_ about promotion while I'm away ;)22:23
sil2100It's time for me to go to sleep finally22:23
popeyo/22:23
sil2100Goodnight everyone, have a nice weekend o/22:23
sil2100And thanks again for your hard work \o/22:24
ogra_=== IMAGE 179 Promoted ===22:28
=== ogra_ changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | CI Train support: trainguards | Vanguard (general help): cihelp | CI Train Status: #179 promoted | CI Train Dashboard: http://bit.ly/1mDv1FS | Known issues: -
* popey hugs ogra_ 22:29
popeywas just going to update my #157 phone and thought "wow, this feels old!"22:30
ogra_:)22:30
ogra_yeah22:31
ogra_the new design is so gret22:31
ogra_*great22:31
popeygot the sdcard popup on nexus 4 after updating22:36
popey"failed to initialise storage" or something22:36
popeywhere should I file that?22:36
ollicongrats everyone to #179 !22:55
kenvandinewoot23:08
kenvandineno more traincon-0!23:08
rsalvetiawesome23:19
rsalveti:-)23:19
rsalvetijhodapp: now we can land camera :-)23:19
rsalvetipopey: https://launchpad.net/ubuntu/+source/ciborium23:20

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