[00:02] robru: thanks! [00:10] alecu: Is silo 8 fixed now? [00:11] ToyKeeper: 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:12] ToyKeeper: tedg suspects that bug is in Unity, and will look at it tomorrow with tvoss [00:15] alecu: Flashing now for testing... could take a while to finish though. [00:16] thanks! [00:16] (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] will join the family for dinner and will check here afterwards [00:17] I'm a little distracted today too; just have tonight to finish house repairs before the new floor goes in tomorrow morning. [00:18] ToyKeeper: 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 steps [00:18] Hmm. [00:18] ToyKeeper: also, it's the first time we are asking QA people to take a look at this [00:19] In that case, perhaps I can skip the "before" phase. [00:19] great [00:20] sorry 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] I think pretty much everyone is behind where they'd like to be. There's just too much to do. :) [00:21] indeed :- [00:21] ) [01:56] alecu: 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.png [01:58] ToyKeeper: those are awesome news! [01:58] ... 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:59] ToyKeeper: 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 branch [01:59] ToyKeeper: in fact, let's open a bug with that screenshot in Software center agent [02:00] alecu: ... 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] But again, server-side. [02:00] The client looks fine. [02:01] yay! [02:01] (aside from issues noted in the test plan, which I assume we're not blocking over) [02:01] sure [02:02] ToyKeeper: thanks a lot for staying so late. Hope you can finish with your house repairs :-) [02:03] It'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] ToyKeeper, thanks! [02:05] === trainguard: IMAGE 178 building (started: 20140808 02:05) === [02:05] infinity, 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.diff [02:05] Er, did we just miss getting silo 8 into image 178? [02:05] I'm very happy anyway :-) [02:06] ToyKeeper, yep [02:06] Sigh. [02:06] ToyKeeper, 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] It 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:09] ToyKeeper: we can add some instructions to run over plain adb shell [02:09] ToyKeeper: "su -l phablet" should be enough [02:51] so quiet.. [03:40] === trainguard: IMAGE 178 DONE (finished: 20140808 03:40) === [03:40] === changelog: http://people.canonical.com/~ogra/touch-image-stats/178.changes === [04:04] hello [06:59] Morning. How are we looking for a promotion? [07:01] The bug list doesn't look immediately promising for that :-( [07:06] Drat, it doesn't want to let me mount /android/system as read-write. [07:06] Loop-mount on RO base? [07:07] Yes, I think so. I'm looking for the image file. [07:10] no progress seems to be yet done on the date/time picker or the camera launch (popup notifications) [07:10] music app was confirmed to be fixed as it passed 100% on #177 [07:11] cihelp, hey, our qmluitests job started timing out after yesterday's jenkins reboot (??) http://s-jenkins.ubuntu-ci:8080/job/unity-phablet-qmluitests-utopic/814/console [07:11] a complete run before took under an hour, now it times out after 3h [07:12] always after the actual tests complete, last step seems to be generating coverage report [07:13] #178 would be the bestest ever if it weren't for those two blockers [07:13] mako pass rate 99.0% [07:24] we'll get there :) [08:03] trainguards: can I get a silo for line 31? [08:06] tvoss: hi! Let me try [08:06] sil2100, thank you [08:06] wow, looks like traincon actually helped :) [08:08] tvoss: how's silo 004 going? :) [08:09] Ah, ok, so the hot-fix landed in the meantime [08:09] camera app crashes though :/ [08:09] So the only blocker left for us is the date-time picker... [08:09] ogra_: on start? [08:09] no on the smoketest page [08:10] surely unrelated to the location stuff [08:10] but due to that we didnt have any results for it for the last uploads it had [08:11] It works fine on my device, so I wouldn't consider it a blocker, as it probably crashed on shutdown [08:11] oh, i didnt talk about it being a blocker :) [08:11] just another thing we have to look at now [08:11] zsombi: hi! Soooo...! Any luck with the date-time picker? [08:12] zsombi: it's basically our last blocker (I hope) [08:12] sil2100: I made a small JS workaround for it, as it did not work in C++.... it ended up that Qt Compositor changes screwed it up [08:12] ogra_: right... let's see if it happens on the next smoketesting [08:12] yup [08:13] zsombi: yeah, we saw Mirv bi-secting it to QtCompositor - so do you think we can land the JS workaround today? We would be super happy [08:13] sil2100: so, all we can do in the toolkit is to provide this workaround which apps shoudl use till we get the Qt Compositor fixed === 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. [08:14] sil2100: that wouldn't be the only thing we must do: apps must use the PickerPanelWorkaround.openDatePicker() in order to get it working [08:14] zsombi: 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] sil2100: yes, until we get the causing bug fixed, then they can go back to PickerPanel [08:14] sil2100: replacing the component "PickerPanel" with the workaround woudl break the API [08:14] sil2100, still exhibiting the issues, but the immediate user facing problems are fixed by whitelisting the camera app and osmtouch [08:15] tvoss, trust-stored-skeleton also has a bunch of crashes during testing, did anyone ping you about that already ? [08:15] ogra_, nope [08:15] zsombi: 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 component [08:16] sil2100: ai sire! [08:16] 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 later [08:16] zsombi: thanks in overall! [08:16] * sil2100 smells promotion today [08:17] zsombi, do we have a theory why qtcomp influences the date-time picker. I have difficulties understanding why qtcomp would influence in-app rendering [08:17] davmor2: ready your dogfooding skills, those will be needed soon! [08:17] ogra_, thanks, do we have retraces available for the crash files? [08:18] tvoss: not much, but all we know was that it got broken after that fix [08:18] tvoss, i dont think so ... psivaa-afk-bbl could tell you i guess === psivaa-afk-bbl is now known as psivaa [08:18] tvoss: what it looks from our side is that it behaves like the Singleton would have been created with a different root context [08:18] tvoss: despite it gets created with the same QML engine [08:19] tvoss: the Singleton (PickerPanel) does not get anything from the other root context [08:19] zsombi, 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] tvoss: any context property that it gets defined there [08:20] tvoss: 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] tvoss: there was no other change in between those two releases that would have affected it... [08:20] otherwise this file has to be processed manually i guess [08:20] yeah, thought so [08:21] tvoss: it works by downgrading platform-api, unity8 and by switching from qtmir to qtubuntu+unity-mir. so, no other Qt/QML changes. [08:23] that is, doing those downgrades on #158 image to the versions that were on #157 [08:26] Mirv, so I would suspect the issue in qtmir then, in its implementation of the qpa [08:26] Mirv, zsombi do you guys have time on your hands to look into the issue? [08:27] tvoss: greyback promised to look deeper into this [08:27] zsombi, ack [08:31] tvoss: 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. === vrruiz_ is now known as rvr [08:56] Saviq: 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 fginther [08:57] psivaa, ok thanks, same happened in http://s-jenkins.ubuntu-ci:8080/job/ubuntu-settings-components-qmltests-utopic/ FWIW [08:58] Saviq: yea, the same slave [09:04] sil2100, could you reconfigure silo 4, please? [09:08] ACK [09:10] tvoss: done [09:10] sil2100, thank you [09:10] yw! [09:15] hmmm, 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/230059 [09:29] cihelp, could someone help me in understanding the build timeout here: https://jenkins.qa.ubuntu.com/job/location-service-utopic-amd64-ci/163/console [09:42] tvoss: we see this timing out in some other jobs too.. waiting for retoad to see what caused it [09:50] psivaa, something is indeed weird: https://jenkins.qa.ubuntu.com/job/process-cpp-utopic-armhf-ci/11/console [09:59] I need to AFK for a moment, brb [10:01] ooh, bug!. making note to file this - have two events at the same time, dismiss first, can't dismiss second... [10:01] phone unusable [10:22] are there any silos that need testing? [10:23] Saviq, the new UI !!!!!! [10:23] so sexy !!!!!!!! [10:24] * ogra_ just upgraded to 178 and is super impressed [10:25] ogra_, you mean the indicator? [10:25] Saviq, url-dispatcher broke again [10:25] brendand, nope, unity8 [10:26] ogra_, what - you mean the loading bar? and the dots? [10:26] yeah :) [10:27] i think the dots should remain static when swiping [10:28] yeah, true [10:28] file a bug :) [10:29] sil2100: Was there ever a decision on where the target series would go in the spreadsheet? [10:33] brendand: what changed with the indicator? [10:34] the dots are nice I agree [10:38] brendand, ogra_, they can't stay static [10:38] as the bar in which they are in can move around [10:38] yeah, what i thought ... would be nicer though [10:38] it feels like the icon drawing slowness got a bit worse though [10:39] (in the app scope) [10:39] (when scrolling) [10:39] ogra_, [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 least [10:39] yeah, no biggie [10:40] nik90, sim details are shown [10:40] brendand: ah yes that === tvoss is now known as tvoss|errands [10:45] I'll try out zsombi's UITK branch and try to modify calendar to use it [10:46] 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? [11:03] cjwatson: there will be an additional column, but we didn't yet decide on the position [11:04] cjwatson: I'll experiment as we already have, so to say, 'too many columns' [11:05] Mirv: thanks! [11:05] Mirv, bzoltan: is there a branch ready somewhere? Or a landing prepared? [11:07] sil2100: 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:09] Yeah, 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 hours [11:10] sil2100: 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] sil2100: I think we could even add a landing line plus kick a build without waiting for Zoltan? [11:10] boiko requested it [11:10] in case it takes time [11:11] piiramar: adding [11:11] Mirv: thanks [11:11] olepa hyvä [11:11] kiitos [11:13] piiramar: done [11:13] thanks [11:14] Mirv: 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] So that we make sure it's in staging as well === MacSlow is now known as MacSlow|lunch [11:29] sil2100: so I don't see anything that isn't already known in 178 [11:36] sil2100: oh except the twitter password in accounts I must bug that before I head off :) [11:40] davmor2: seen the issue where if you have two alarms at the same time it blocks pin unlock, you have to reboot phone? [11:40] ;) [11:41] sil2100: https://bugs.launchpad.net/account-plugins/+bug/1354402 not a blocker just annoying :) [11:41] Ubuntu 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] oSoMoN: ^ that one might be of interest to you [11:42] popey: 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 it [11:43] no, will do === tvoss|errands is now known as tvoss [11:48] sil2100: what Mirv said is correct. I am preparing that MR and land it on the staging when we decide to go with the workaround === lool- is now known as lool [11:50] popey: confirmed it so just need a bug [11:51] sil2100: the hot fix is not to make it promotable though [11:52] sil2100: as it has the camera-app version hardcoded in it, is just to unblock other stuff [11:53] sil2100: so the location-service trust-helper changes are still blocking promotion, until silo 4 lands [11:53] rsalveti, why wouldn't we promote with the hotfix in? [11:54] tvoss: because as soon we update camera-app or osmtouch (from app store, for example), it will be broken again [11:54] unless we don't care about osmtouch [11:54] not sure if camera-app could be updated via store though [11:54] davmor2: bug 1354406 [11:54] bug 1354406 in indicator-datetime (Ubuntu) "2nd of 2 alarms at same time is unclickable" [Undecided,New] https://launchpad.net/bugs/1354406 [11:55] rsalveti, so your proposal then is to extend the hotfix to arbitrary versions in case silo 4 does not fix the issue? [11:55] tvoss: if you want a promotable image, yes [11:56] or a revert, as we discussed yesterday [11:56] but I thought silo 4 would land today [11:56] is it still in progress? [11:56] rsalveti, dednick is on it, I rebuilt it an hour ago, will test it now [11:57] great [11:57] sil2100: which other issue is blocking promotion? [11:58] Right 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 :) === nik90 is now known as nik90|Lunch [12:03] sil2100, hey, can we have a silo for line 32 ? === alan_g is now known as alan_g|lunch [12:04] rsalveti, time/date picker issues iirc [12:06] tvoss, rsalveti: so, to get things straight... the current hot-fix for the camera-app only work for the current camera-app? [12:06] And it will be broken again if we release a new version of camera? [12:06] sil2100: we have the workaround branches for the UITK and for the Calendar ready if you guys want it [12:07] davmor2: have a great weekend. [12:07] bzoltan: do you know how the real fix is going? [12:07] davmor2: see you next week! [12:07] sil2100: I do not. [12:07] sil2100, gerry knows why it broke and is working on it [12:07] sil2100: and that is not coming from the SDK team for sure. [12:08] sil2100: basically, yes [12:08] greyback: hi, how far are you with the real fix for the date-time picker? [12:08] hm, booted 178 on flo and got a black screen in unity8 [12:08] sil2100: pmcgowan: just give me the signal if you decide to go with the workaround. [12:08] bzoltan: 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/20 [12:08] Ubuntu bug 1351024 in Ubuntu UI Toolkit "Date & Time picker is not working on device." [Critical,In progress] [12:08] sil2100: I have a preliminary fix: https://code.launchpad.net/~gerboland/qtubuntu/fix_1351024/+merge/230094 but it needs careful review & testing [12:09] unity8-dash crashed [12:09] Mirv: you need this on the calendar app https://code.launchpad.net/~bzoltan/ubuntu-calendar-app/lp_1351024_workaround/+merge/230095 [12:09] Forking RTM [12:09] together with maliit-server and system-settings [12:09] doooh [12:09] bzoltan: looks identical to mine http://bazaar.launchpad.net/~timo-jyrinki/ubuntu-calendar-app/use_pickerpanelworkaround_lp1351024/revision/387 [12:09] cjwatson, good luck! [12:09] (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:10] (collective sigh of relief) [12:12] cjwatson: \o/ [12:12] sil2100: Saviq: just got on flo https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1354412 [12:12] Error: ubuntu bug 1354412 not found [12:12] now public https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1354412 [12:13] Mirv: you sure it does not work? [12:13] This has been a bit of an exercise in how much time we can spend polishing a single extremely complicated run-rarely launchpadlib script [12:14] greyback, do you recommend we go with the sdk and app side workaround or await your review and test? [12:15] tvoss, any testing get done on silo 14? [12:15] sil2100: well, it doesn't work for me, other eyeballs on the branches and testing would be welcome [12:15] pmcgowan: my fix is more correct, I think it would be better to get it in [12:15] pmcgowan, have to check with charles, he worked on it yesterday [12:15] greyback, ok lets focus there bzoltan Mirv [12:16] greyback: excellent [12:16] yay for greyback's fix [12:16] I'm running UITK AP tests now [12:16] greyback: I love you man... I was feeling bad about our solution === nik90|Lunch is now known as nik90 [12:17] bzoltan: yeah I didn't like it so much :) [12:17] greyback: tell me if you need any help :) [12:18] bzoltan: when CI has the package built, I'd appreciate testers [12:25] * sil2100 gets his device ready === MacSlow|lunch is now known as MacSlow === greyback is now known as greyback|lunch [12:33] restarting branching script, we found a mistake just in the nick of time :) [12:35] bzoltan: sil2100: greyback|lunch: working! "Tested with a local build, works with this branch! (ie. similar to #157)" [12:35] (added a comment to greyback's branch) [12:35] Mirv: with greyback|lunch's lunch? :) [12:35] *branch [12:35] sil2100: indeed [12:39] but was CI broken btw? and does anyone want my hand-build .deb:s to install? [12:39] I'd add a line for qtubuntu already (doing) [12:40] Mirv: if you could upload those somewhere then it would save me some time [12:40] pmcgowan, so silo 14 fixes the issue that we see in the indicator <-> location service communication. However, charles encountered issue in the indicator backend <-> frontend configuration [12:41] tvoss, thanks for update, so still diddling that silo? [12:41] rsalveti, can you grep ~/.cache/upstart/unity8-dash.log* for "what", the abort message? [12:41] pmcgowan, 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 switches [12:41] Ubuntu bug 1336715 in Unity 8 "switch-items in indicators sometimes get out of sync" [Critical,Confirmed] [12:42] pmcgowan, 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, then [12:42] charles, pmcgowan makes sense? [12:42] pmcgowan, tvoss, so that still leaves an asterisk next to kenvandine's u-s-s GPS changes, but IMO doesn't block silo 014 [12:42] Saviq: hm, sorry, flashed it again, will try to reproduce and see if I can get that to you [12:43] tvoss, yes, that's fine [12:43] charles, but we could enable at that point yes? [12:43] modulo the bug above [12:43] pmcgowan, yes, IMO that's the way to go [12:43] +1 [12:43] http://people.canonical.com/~tjyrinki/datepicker/qtubuntu-android_0.60+14.10.20140728+fix1351024-0ubuntu1_armhf.deb [12:43] rsalveti, thanks [12:43] charles, pmcgowan I will take care of getting it in then, likely Monday though [12:43] and building in silo 015 [12:43] pmcgowan, 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 in [12:43] Mirv: \o/ [12:43] Mirv: thanks [12:44] yw [12:44] sil2100: doh, what was the most modern way to do the -gles part, or still a manual upload? === 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. [12:46] Mirv: 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 in [12:46] Mirv: best if you check some examples in qtmir, since it had some recent uploads to the gles branch [12:46] Mirv, something along those lines is needed https://code.launchpad.net/~saviq/qtmir/gles-sync-20140716/+merge/227000 [12:47] Mirv, needs a dch -v $non-gles-version and an update to the watch file to point at the correct silo [12:47] sil2100: Saviq: ok, trying [12:48] Saviq: got it again, let me get that for you [12:48] * sil2100 is trying out greyback|lunch's fix [12:49] Saviq: http://paste.ubuntu.com/7988563/ [12:49] rsalveti, interesting, unity8.log ? [12:49] Saviq: http://paste.ubuntu.com/7988571/ [12:50] rsalveti, *interesting* [12:50] Mirv, I am not seeing it fixed here with that deb [12:51] rsalveti, dash is basically saying it can't connect to unity8, which seems to be happily running [12:51] Mirv, greyback|lunch: confirming it fixed here on my device [12:51] rsalveti, like some env isn't set up properly [12:51] what did I do wrong [12:51] pmcgowan: how come? What do you see? [12:51] rsalveti, can you please upload those to the bug and confirm it [12:51] same nothing pops up [12:51] Saviq: done [12:51] pmcgowan: since the date-time picker will appear below the keyboard if you have it visible, so you have to dismiss the keyboard first [12:52] cihelp: seems building of uss is broken? https://jenkins.qa.ubuntu.com/job/ubuntu-system-settings-ci/1173/ [12:52] Saviq: trying with that https://code.launchpad.net/~timo-jyrinki/qtubuntu/gles-sync-20140808/+merge/230101 [12:52] pmcgowan: did you reboot after installing the package? [12:52] sil2100, ahh, forgot about tht other bug [12:52] once sec [12:52] yep its there [12:52] pmcgowan: it gets fixed only to the state it was at #157 [12:52] yeah [12:52] At least it's usable now [12:52] so works [12:53] bug #1338956 is that other problem [12:53] bug 1338956 in Ubuntu Calendar App "Date/time changer hidden when textfields have focus" [High,In progress] https://launchpad.net/bugs/1338956 [12:53] We need to make sure now nothing else is b0rken, but so far things look good [12:55] jgdx: 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:56] josepht, that's great. Thanks. My sbuild is broken locally for uss, probably not related though. [12:56] Saviq: any other info? [12:56] rsalveti, don't think so, you get that on first flo boot after flashing? wiped? [12:57] rsalveti, silo 4 fixes the issue for me. Could you give it a spin? [12:57] dednick, ^ [12:58] \o/ [12:58] sil2100, ^ [12:58] Then there's a possibility that we won't have to rely on any workarounds/hot-fixes if we'll be able to get both landed [12:58] tvoss: did you also revert your location-service changes on that silo? [12:58] tvoss: woop [12:59] sil2100, silo 4 actually reverts the location service hotfix [12:59] rsalveti, yup [12:59] Saviq: yes, bootstrap on flo, first boot [12:59] tvoss: sure [12:59] It makes me smile then [12:59] sil2100, please give it a spin, too [12:59] * Mirv is foreseeing a promotion today [12:59] uhoh [12:59] tvoss: will do! [12:59] tvoss: missing qtmir-gles in there [12:59] ...and then popey found a Bug? ;) [13:00] rsalveti, yup, taking care of that now [13:00] great [13:00] heh [13:00] popey: NO [13:00] * popey puts the phone down [13:00] We say NO to bugs [13:00] Bad popey! [13:03] rsalveti, really weird, as the dash should only start after unity8 started, so it should've set up the environment properly ;/ [13:04] Saviq, greyback|lunch https://code.launchpad.net/~thomas-voss/qtmir/sync-20140808/+merge/230103 [13:04] * Mirv tries to guess the magic order/way of building the silo with twin package [13:04] Mirv, first with ignore twin packages, grab version, propose mp, take mp and add to silo [13:05] sil2100, could you reconfigure 4, please? [13:05] tvoss: 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] tvoss: sure [13:05] sil2100, thanks [13:07] Done [13:07] Mirv, yup, pre-guessing version works, too ;) [13:07] tvoss, ACK [13:08] Saviq, just need to rebuild the gles twin, correct? [13:08] tvoss, yup, you don't want to rebuild non-gles as it would get a different version again [13:08] Saviq, yup [13:09] sil2100, rsalveti building === alan_g|lunch is now known as alan_g [13:14] tvoss: installed your silo as well, now I will perform some tests on it to see if all is ok [13:15] And I guess we'll land both silos (4 and 15) [13:16] sil2100, i think there's a functional bug in gallery app caught by the autopilot tests [13:16] sil2100, basically you can see the shell from behind the image [13:16] brendand: is it something serious? What do you mean it can be seen? [13:16] sil2100, not sure if the corresponding AP test actually fails, i need to look closer [13:16] sil2100, more details soon [13:17] sil2100, just a heads up that it could be a promotion blocker [13:17] brendand: ok, give me a sign as well if it's serious or not, since small visual glitches shouldn't block us from promoting [13:17] sil2100, well okay [13:23] hi trainguards! may I ask you what's needed for silo-008? [13:24] alecu: 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 hours [13:24] great, thanks! === greyback|lunch is now known as greyback [13:26] sil2100: we need QA to sign silo 4 [13:28] rsalveti: theoretically we do not need to, but on the other hand it would be good to double-check nothing is broken [13:28] brendand: can you install silo 4? [13:28] sil2100: the reason for QA is that we're now finally using trust-store for camera [13:28] sil2100: so while this is fixing a bug, it's also adding a feature [13:29] that was supposed to be validated before, but which wasn't [13:29] and that's how we got the bug in first place :-) [13:29] Right ;) So in theory it was supposed to be already QA signed-off [13:29] Anyway, +1 on that in overall [13:29] sil2100, yes! [13:29] brendand: are you busy now? We would need this really since we want to land it ASAP ;) [13:30] sil2100, om26er is around now as well, but i can certainly give a second pair of eyes [13:30] om26er: pong! [13:30] sil2100, it fixes the camera issue? [13:31] brendand: yes [13:31] sil2100, don't you mean ping ? [13:31] ;) [13:31] om26er: ;) [13:31] sil2100, i'm on it [13:32] om26er: 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 much [13:32] sil2100: landing-015 just finished the qtubuntu part, should QA be testing that too at the same time? [13:33] Mirv: not sure if QA needs to test that, would be enough if the lander tests it [13:33] Mirv: as it's an isolated bugfix for a blocker [13:34] brendand: so please test camera-app and osmtouch [13:36] sil2100: 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:41] rsalveti, with camera app the dialog appears [13:42] great [13:42] rsalveti, interesting that the ap tests can pass with that there [13:46] retoad, 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:47] brendand: even before accepting it on the first time? [13:47] retoad, 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-c [13:47] Saviq, /me looks [13:47] rsalveti, you ran them right? [13:47] retoad, the jobs get stuck on generating coverage info [13:47]