=== iveand is now known as rikshaw76 [07:01] heads up everyone. unity8 doesn't start any more because of a bad merge in ubuntu-ui-toolkit. Don't upgrade your system if it still works for you [07:06] save yourself! [07:08] asac: ping [07:10] morning tsdgeos [07:10] mzanetti: morning [07:15] mzanetti, can you get out that word on the mailing list, too, please? [07:16] tvoss: sure [07:17] mzanetti, great, thx [07:22] mzanetti: hi [07:23] asac: hi. do we run any integration tests for ubuntu-ui-toolkit? [07:23] asac: if yes, how do they work/look like? [07:24] mzanetti: what test framework are you using? autopilot? [07:24] mzanetti: oh ... so no, not yet [07:24] mzanetti: we just have application integration tests that implicitely test the SDK where we use it [07:25] asac: yeah... weird thing is: [07:25] we are waiting for more advanced tests [07:25] asac: unity8 doesn't start any more with the latest ubuntu-ui-toolkit [07:25] asac: so I'm wondering how that has passed the release chain [07:25] mzanetti: so one way you can do that is basically just write a tests that reproduced this phenomenon and then you will be protected in future [07:26] mzanetti: yeah, so reason is lack of testing on real phones and images at merge and daily-release gates [07:26] mzanetti: which sdk broke you? [07:26] when did that land? [07:26] timestamp: Tue 2013-08-27 20:04:05 +0000 [07:26] this is when the bot committed the changelog [07:27] so I guess released a few hours later [07:27] mzanetti: can you point me at the commit? [07:27] asac: rev 714 in ubuntu-ui-toolkit [07:27] mzanetti: you think you could write a test that reproduces this issue for future protection? [07:28] asac: yeah sure [07:28] asac: but just for my understanding [07:28] asac: I assume that ubuntu-ui-toolkit package got released because there were no tests failing in there, right? [07:29] asac: and if later unity8 comes along and all the tests fail, it's considered being an issue in unity8 and that one doesn't get released any more, right? [07:30] mzanetti: well, the idea is that we figure out the right blamee [07:30] the approach ofr that is to: a) blame the owner of the apps whose tests fails as first stop [07:31] so if you handn't talked to me i would have come to unity8 first, yes [07:31] asac: ok [07:31] in order to steer me directly to sdk you could easily add tests for the sdk [07:31] basically just put your own safety nets in place [07:31] so OTHERS dont shoot you in the foot [07:31] if you have a test that clearly diverts initial attention to sdk, then you are fine :) [07:31] asac: yeah, but those tests need to be in the ubuntu-ui-toolkit, no? [07:31] NOW THAT I KNOW, i WILL know who to blame :) [07:32] that's not really the point... I'm trying to catch such failures earlier [07:32] mzanetti: no... absolutelyt not... any autopilot test should work, but as i said problem is that daily release doesnt run on real phones yet [07:32] so might just not catch everything [07:32] mzanetti: so here the stacks we treat as ONE entity: http://reports.qa.ubuntu.com/daily/ [07:32] asac: no... this completely breaks QML compilation... nothing to with phone or not [07:33] hmm [07:33] mzanetti: so if you see those stacks, everything has to pass all autopilot tests for now [07:33] so if sdk busts everything it should be catched there [07:33] if it wasn't I have to check why [07:33] so let me see [07:33] mzanetti: did you see the ui-toolkit already in the archive? [07:34] asac: yeah. apt-get upgrade breaks all unity8 installations right now [07:34] mzanetti: i'm starting to think that lp:~stolowski/unity8/fix-filter-activation and lp:~saviq/unity8/ap-raise-on-typing are actaully problematic by themselves :D [07:34] omg [07:34] sil2100: Mirv: hey [07:35] jamesh: hi! Any luck on getting rid of those gstreamer deps? [07:35] asac: morning! [07:35] sil2100: Mirv: can you tell me why the fact that ui-toolkit breaks everything in unity8 wasn't seen in our daily-release systems? [07:35] tsdgeos: hehe, yeah. might be. but our latest flakyness in jenkins makes it hard to tell [07:35] http://reports.qa.ubuntu.com/daily/ [07:35] tvoss: didn't get your emaiil about benhcmarks yesterday [07:35] sil2100: still working on it. I should have it cleared up a bit later today. [07:35] sil2100: i thought we at least try to run all autopilots there, so unity8 autopilot should have revealed if its really that bad [07:35] tvoss: i already recorded a video of the nexus4+mir if you want to see it [07:35] tsdgeos, right, still in my draft folder [07:35] mzanetti: how is it broken afterards? [07:35] asac: doesn't start any more [07:35] tsdgeos, have seen it, thanks [07:35] mzanetti: doesnt boot? did you try run unity8 autopilots? [07:35] s/already/also [07:36] mzanetti: ok. then its odd. if that also happens on the x86 side, we should have seen it in daily-release gatest [07:36] asac: everything fails... it's like unity8 would crash directly at startup [07:36] asac: let me see what we're actually running for unity8 [07:36] sil2100: almost everything still worked with those build-deps removed, except for some tests [07:36] jamesh: \o/ [07:36] asac: yep, that's why I pinged you. I couldn't find any failure [07:36] sil2100: right. seems there was a superbogus commit that busted us and we try to find out how that slipped through :) [07:36] sil2100: can you confirm that we run all autopilots (*just not on phone) here: http://reports.qa.ubuntu.com/daily/ ? [07:37] tsdgeos: btw: https://code.launchpad.net/~mzanetti/unity8/launcher-initial-extensionSize/+merge/182504 this one seems to reliably work around the initial ListView positioning [07:37] sil2100: also, can we backout ui-toolkit? [07:37] i would really like to do that until they fixed it :) [07:37] tsdgeos: and also might have an impact on our analysis of the bug :/ [07:37] but lets talk later what to do [07:37] lets first figure what happened :) [07:37] asac: unity8 stack runs only unity8-autopilot tests [07:37] mzanetti: hmmm [07:37] (from first glance) [07:37] well, why? [07:38] Mirv: but I see it's upgrading the SDK, so it should see if things are broken [07:38] mzanetti: i mean the simple example we ahve behaves wrong [07:38] mzanetti: no? [07:38] sil2100: assuming there are tests that break with the SDK update, not sure if ui-toolkit is used much in unity8 itself (probably not) [07:38] tsdgeos: yeah... but I think setting the currentIndex doesn't work because of the listview margings (i.e. it thinks the item would already be in the visible part) [07:39] Mirv: but they say it's *badly* broken, so we should detect the case where nothing works, right? [07:39] Mirv: those would have catched this issue though [07:39] Mirv: we should at least include one stable app or two i think in that stack as well fwiw, but that unity8 should have failed in this case [07:39] sil2100: sure, although I thought I was running the latest one on my device but maybe not [07:39] this is an example of "badly broken" :) http://s-jenkins:8080/job/generic-mediumtests-runner-saucy/2300/console [07:40] sil2100: any progress on getting unity-scope-mediascanner in the archive? [07:40] tsdgeos: and this one should improve the autopilot test reliability I hope. http://10.97.2.10:8080/job/generic-mediumtests-runner-saucy/2300/console [07:40] Mirv: sil2100: ok, please let me know once you figured how this slipped through. also if we can back this out without trying to investigate/fix/debugg (just revert to previoyus state) that would be fantastic [07:40] tsdgeos: mind reviewing those two? [07:40] we really try to get a good image out today [07:40] bad paste :D [07:40] and this is the least i can need for that goal:) [07:40] but i saw the "stable tests" one or whatever is called [07:41] tsdgeos: https://code.launchpad.net/~mzanetti/unity8/more-stable-tests/+merge/182448 [07:41] mzanetti: ironically it's not passing in CI :D [07:41] tsdgeos: haha, yeah [07:41] probably also UI Toolkit tests shouldn't have passed, if this was the offending commit? https://code.launchpad.net/~nicolas-doffay/ubuntu-ui-toolkit/ubuntu-shape-option-selector/+merge/175242 [07:41] tsdgeos: well, the first run passed. then all hell broke loose in our ci [07:41] Mirv: we dont run any toolkit tests that i know during integration [07:41] ah right [07:41] sorry [07:41] tsdgeos: first the VM's being borked and then unity not starting any more at all [07:41] if there are tests i want to know [07:42] no need to restage the failed autolandings obviouly [07:42] jamesh: it's waiting for actual publishing - which didn't happen just yet, so it should be in real quick [07:42] okay [07:42] * mzanetti goes for writing a test in ubuntu-ui-toolkit [07:42] mzanetti: can you give us also tests that we can run in the image? [07:43] like autopilots etc. [07:43] asac: how do you mean? [07:43] asac: well all of the unit tests are run and were successful https://jenkins.qa.ubuntu.com/job/ubuntu-ui-toolkit-saucy-amd64-ci/425/? , I'd guess there should be a test that would catch something like this [07:43] e.g. not only unit/make check tests [07:43] mzanetti: there are build time tests [07:43] and runtime/integration tests [07:43] i also would want more int3egration tests [07:43] that test the whole thing [07:43] Mirv: i dont care about unit tests ... thats something that is fine and good :) ... but ultimately i want our autopilots/integration tests [07:44] to detect if something busts unity8 completely [07:44] * mzanetti doesn't agree [07:44] mzanetti: how can you disagree on something expressing what i care about :)? [07:44] hehe [07:44] :D [07:44] i said: unit tests are fine and good [07:44] right... [07:45] I missed the "i" in the beginning [07:45] hmm, first of all, is there a bug against ui-toolkit for the breakage? [07:45] Mirv: i guess not. [07:45] mzanetti: hmmmm [07:45] https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1217650 maybe this [07:45] i am still stuck at an earlier stage :) [07:45] Launchpad bug 1217650 in ubuntu-ui-toolkit (Ubuntu) "Unity8 does not start with the latest ubuntu-ui-toolkit packages" [Critical,New] [07:45] yeah that sounds right from title :) [07:46] mzanetti: so i read https://code.launchpad.net/~mzanetti/unity8/more-stable-tests/+merge/182448 as "wait for infographic anim to fnish before moving the greeter away", is that right? [07:46] tsdgeos: yes [07:46] mzanetti: shouldn't we fix that to work? :D [07:47] tsdgeos: I think it does work (if the machine running it actually fulfills our minimum hardware requirements) [07:47] but we're testing with less :D [07:47] tsdgeos: but I do agree... If there is really an issue in our code, that should be fixed. [07:48] mzanetti: maybe adding a todo in the Greeter code? [07:48] something like "TODO investigate bla bla" [07:48] asac: question: wouldn't it make sense to start (just start) all the applications and unity8 as some sort of integration test for the SDK? [07:48] mzanetti: we have all that [07:48] it seems its just not run :) [07:48] right... [07:49] our autopilots have that as well [07:49] and more :) [07:49] mzanetti: noone's going to fix it, but we'll cover our asses :D [07:49] asac: so in the end it's just an issue that parts of the test suite were currently disabled? [07:49] Mirv: sil2100: so, you think we have the means/tools to just throw this out temporarily so sdk team can fix this for real? [07:50] mzanetti: yeah... its surely about our daily-release gates not doing what we wanted in this case [07:50] the sdk stack should have gone red here: http://reports.qa.ubuntu.com/daily/ [07:50] and waited for action before pushing to archive [07:51] asac: I'm just asking SDK team to revert it in trunk until it's resolved [07:51] mzanetti: however, without direct integration tests for ui-toolkit the blame would first fall to the busted app/unity maintainers [07:51] Mirv: do we have means to do that without team involvement? [07:51] asac: that's not a problem for me... I can redirect you after analyzing the issue [07:51] we should be able to solve problems like that without having to wait for anything :) [07:52] asac: the bigger issue is that it got released [07:52] mzanetti: yeah ... thats good. [07:52] mzanetti: just sayingL if you want blame protection you can also write tests for your biggest offenders :) [07:52] but i agree as long as we catch such things we should be happy [07:52] asac: yeah. understood. I wouldn't call the SDK our biggest offender tho... usually it works out quite well. this case is really a stupid mistake [07:53] :) [07:53] asac: not nicely, of course one can forcefully push stuff to trunk [07:53] right. thats what safety belts are meant to do [07:53] asac: but the team is there, online [07:53] Mirv: ok, are there other commits? [07:53] or just this one? [07:54] asac: just one commit, and apparently the problem is about PopoverForegroundStyle being made internal [07:54] Mirv: ok, can you get them to revert without debugging/testing/fixing? [07:54] they can do the real fix in a second step [07:54] without firedrill [07:54] (so we dont risk picking up another stupid mistake() [07:54] see what they say [07:55] we really would like to push the button for a new package/image in a couple minutes at best [08:16] asac: sil2100: ok, revert is merged (merged it manually to hasten) and launched a rebuild [08:16] nice! [08:16] thanks! [08:17] Mirv: keep me posted (e.g. when package hits daily-release pcoket etc.) [08:17] ok [08:34] there are so many points that could be a bit faster. amd64 always finishes before i386, so running tests on amd64 might be worthwhile. then, publishing packages after they've been uploaded to PPA takes another 5-10mins, added by the polling interval of 5mins [08:34] but, it's building now https://launchpad.net/~ubuntu-unity/+archive/daily-build/+sourcepub/3450226/+listing-archive-extra and after i386 has both built and published the tests will be run [09:01] Zhenech: where was the debian status page for ubuntu indicators again? [09:02] asac: now in LP https://launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/0.1.46+13.10.20130828-0ubuntu1 [09:03] Mirv: awesome [09:03] hyperair, pkg-ayatana-devel@alioth on qa? [09:04] Zhenech: more like the stuff that hasn't been packaged [09:04] nevermind, found it. [09:04] * hyperair forgot it was called pkg-ayatana [09:04] hyperair, there is like a ton not merged since wheezy [09:04] yeah i figured [09:04] as someone at your end thought it was a good idea to create all new packages and libs [09:05] and I did not have time [09:05] new packages? [09:05] what new packages? [09:05] like there is no more dbusmenu etc [09:05] ah hell [09:05] would have to search myself [09:53] sil2100, is unity stack completely disabled, or is it going to be run soonish? [09:53] Mirv, ^? [09:57] mhr3: let's wait for the next tick, since this tick was badly broken because of all the *things* [09:58] mhr3: indicators is blocking it, still [09:58] even next tick at the moment it'd seem, since there is some powerpc related problem [09:59] Mirv, why did you stop the indicator runs? [09:59] Mirv, http://10.97.0.1:8080/view/cu2d/view/Head/view/Indicators/job/cu2d-indicators-head-2.1build/434/ [09:59] says you stopped it [09:59] the ppa builds seemed fine [09:59] oh, or is that the "keep waiting on indicator-network"? [10:02] seb128: I guess he might have aborted so that the next tick kicks in? [10:02] sil2100, no, read #ubuntu-desktop, I think it's an issue with indicator-network [10:02] seb128: yes, it's that [10:03] seb128: it happened already yesterday but apparently cyphermox & co didn't notice it, and I didn't notice it until two hours into my day either [10:03] I filed bug #1217811 now [10:03] bug 1217811 in Network Menu "libqmenumodel-dev dependency prevents powerpc build and indicators stack release" [Critical,New] https://launchpad.net/bugs/1217811 [10:03] not sure if indicator-network should be tri-arched now, for that [10:03] pstolowski: yay [10:03] :D [10:03] at least [10:04] tsdgeos: well... look at #phablet [10:04] Mirv, cf #ubuntu-desktop [10:04] really? [10:04] that happened with some other MR too [10:04] tsdgeos: yeah, I just discovered by looking at the history [10:04] something bad happened that day [10:05] ok, good enough we found out :D [10:06] maybe saviq's one that keeps failing is the same? [10:06] tsdgeos: it should show empty diff on LP if this is the case [10:06] pstolowski: only if you repush the branch, no? [10:06] or yours did show empty? [10:07] tsdgeos: yes, my did show empty, at least when I checked today [10:07] ah [10:07] ok [10:07] let's see saviq's [10:08] asac: ui-toolkit in release pocket [10:09] nice [10:09] Mirv: how long did it take? 2.5 hours? [10:09] so proposed took 1h [10:09] it seems [10:09] roughly [10:09] maybe 50 [10:10] asac, rather ~2hours between commit and landing in saucy [10:11] asac, https://launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+publishinghistory [10:11] Published 57 minutes ago [10:11] Deleted 39 minutes ago by Ubuntu Archive Robot [10:11] moved to release [10:11] seb128: commit == merge proposal time? [10:11] asac, so ~1.5 hour commit to saucy release [10:11] or local commit? or landing in trunk? [10:12] asac, they directly pushed the revert to trunk without mp it [10:12] seb128: yeah... then it took another 10 minutes before i got it on archive.ubuntu.com [10:12] ok [10:12] guess not yet perfect, but definitely a success :) [10:12] my phone works [10:16] asac: something like that [10:17] asac: and I bypassed the merge proposal phase by direct merge [10:17] asac: one good point is that when it's build in the PPA, it's copied from there to archives [10:18] and the amd64 point I made doesn't apply, since armhf often takes more time than i386 + tests [10:19] the polling in cu2d could be more often, and the PPA publishing is annoyingly slow [10:34] is taking screenshots broken for anybody else? [10:38] screenshots, screencasts, screen* [10:41] dednick: you there? [10:41] tsdgeos: i am [10:42] dednick: if i run https://code.launchpad.net/~nick-dedekind/unity8/indicator.multi-icon/+merge/181862 on the desktop should i see something different? [10:42] tsdgeos, ah I see what you mean with clicking when the hud is on [10:42] tsdgeos, you meant t dismiss the hud? [10:42] yes [10:42] *to [10:42] ok [10:42] tsdgeos, you think it should block inputs? [10:43] I am not sure [10:43] tsdgeos: i am [10:43] sorry [10:43] :D [10:43] tsdgeos: only if you're running on a device at the moment [10:43] Cimi: well it does for the launcher, right? [10:43] tsdgeos: you "may" get the cellular icon next to the wifi icon. [10:43] Cimi: so either we undo the launcher or do this [10:43] tsdgeos, I'll ask oren [10:44] tsdgeos: or if you dont have a sim, it should show "No SIM" [10:44] but having different dismiss goes thorught the thing [10:44] seems very weird to me [10:44] mmm maybe [10:47] dednick: ok, let me see if i can get that to work [10:48] my phone is in a bit of unity-mir flux :D [10:48] sil2100: the mediascanner change to get rid of those extra gstreamer build deps should land shortly. [10:49] tsdgeos, ok it's fullscreen now [10:49] oki === sergiuse1s is now known as sergiusens [10:52] dednick: not sure if you know anything about this [10:53] but i have a bluetooth indicator [10:53] without icon :D [10:55] tsdgeos: yep, we are aware. there is no icon in the theme. [10:55] ok [10:56] jamesh: that's excellent news [11:05] dednick: ok, i see nothing new [11:06] dednick: tbh the code "looks good" [11:06] but without a way to try it [11:06] don't know what to do :-/ [11:06] tsdgeos: you have a sim in? [11:06] nope [11:06] shall i? [11:06] tsdgeos: when last did you do upgrade? [11:06] dednick: minutes ago [11:07] tsdgeos: let me just check if that code is in archive yet. [11:08] tsdgeos: in your wifi indicator, is "mobile" enabled? [11:08] let me see [11:10] dednick: my network indicator is "Empty!" [11:10] * tsdgeos reboots the phone [11:12] dednick: not even that [11:12] no network indicator at all [11:12] dednick: can you check there? [11:13] tsdgeos: yeah, it's been a few days since i updated [11:15] tsdgeos: actually, can you make sure that you have indicator-network installed. there was a problem with doing upgrades awhile ago. [11:16] tsdgeos: it was holding back ubuntu-touch upgrade [11:16] dednick: he he [11:16] seems i don't === alan_g is now known as alan_g|afk [11:17] tsdgeos: just do manual install of ubuntu-touch and it should resolve [11:17] dednick: oh wait i do [11:17] i was doing the dpkg query on my desktop :D [11:17] ii indicator-network 0.5.0+13.10.20130827.3-0ubuntu1 armhf Systems settings menu service - Network indicator [11:17] is that my phone has [11:18] hm. ok [11:18] can you check if the process is running? [11:20] 5.1.1 relesed at last [11:20] yay [11:20] root@ubuntu-phablet:/# ps -A | grep netw [11:20] 1673 ? 00:00:00 indicator-netwo [11:20] dednick: ↑↑↑ [11:20] tsdgeos: yeah [11:20] hm [11:21] what more can i do to debug it a bit more? [11:21] tsdgeos: so you're not even getting the icon? [11:21] i do get the icon [11:21] but empty? [11:21] but if i expand it [11:21] it says [11:21] Emtpy! [11:21] er [11:21] without the typo [11:21] :D [11:22] * greyback back in 40 [11:22] dednick: hey :) Can you reproduce bug #1215644 on the device? [11:22] bug 1215644 in Messaging Menu "Messaging menu does not change icon when a new message appears" [Undecided,New] https://launchpad.net/bugs/1215644 [11:23] larsu: i have indeed noticed mine not changing. but i havent looked into it [11:27] dednick: ah, I can reproduce it now too with my test script. Seems to be a bug in the service after all. Sorry to bother :) === alan_g|afk is now known as alan_g [11:28] larsu: no worries :) [11:36] Anyone got time for quick sdk review? https://code.launchpad.net/~nicolas-doffay/ubuntu-ui-toolkit/crossfadeimage-size-output-fix/+merge/181836 === swook` is now known as swook [11:55] dandrader: hey. welcome back! [11:56] mzanetti, thanks :) [11:56] mzanetti, how are things going? [11:56] dandrader: not too bad actually. [11:57] dandrader: did you already flash a phone? [11:57] probably not... [11:57] mzanetti, no. still downloading e-mail and :apt-get dist-upgrading" [11:57] dandrader: lots of new stuff in the image :) [11:58] mzanetti, great. now I'm curious :) === alan_g is now known as alan_g|lunch [11:58] dandrader: I was playing around with location stuff lately. couldn't get geoclue working and then I found a hangout session from you where you suggested to rewrite geoclue [11:59] dandrader: are you still involved in that stuff? [12:00] mzanetti, no, I'm not. I worked on that rewrite for a week then gave up and joined this team [12:01] mzanetti, but tvoss was working on it just before I left on vacations [12:01] dandrader: ah ok. but do you still know what's going on there? [12:01] ah, I'll ask him [12:02] mzanetti, but I think we are not going to use geoclue or a rewrite of it [12:02] tvoss__: is location stuff supposed to work already? I tried to enable that in one of my app but failed. [12:03] mzanetti, I made a pure-gps backend for Qt location framework but it was removed a couple of days before my holidays as well [12:03] QtLocation was printing a debug message that it couldn't connect to geoclue. I tried to configure geoclue but haven't managed to do so. [12:04] mzanetti, but I'm sure we won't use geoclue [12:05] dandrader: yeah... I'm fine with that... just saying, 3 days ago any access to QtLocation was still printing a message that it is trying to connect to geoclue. That's why I assumed we would use it. [12:05] mzanetti, it's meant to work, let me check if all packages landed [12:05] tvoss__: note: my status if from the weekend [12:05] if something landed last 3 days, I'm outdated already [12:07] mzanetti, ack, might be outdated then, the respective packages could possibly land only yesterday after [12:07] having unblocked proposed [12:08] tvoss__: cool, thanks. I'll try again in the next days and let you know. [12:09] mzanetti, thx === dednick is now known as dednick|lunch === _salem is now known as salem_ === alan_g|lunch is now known as alan_g [12:53] dandrader: welcome back :) [12:53] kgunn, thanks! [12:59] mzanetti, ok... so should I phablet-flash ubuntu-system or cdimage-touch? === hikiko is now known as hikiko|lunch [13:03] dandrader: cdimage-touch --pending [13:04] hmm... ok [13:18] mzanetti, I only have a videos dash, is that expected? [13:18] dandrader: no [13:19] dandrader: you might want to add -p then... to reset everything [13:20] mzanetti, -p or --wipe? [13:20] dandrader: hmm... didn't know about --wipe [13:20] dandrader: always used -p when shit broke loose [13:22] mzanetti, -p is "Installs from base path, you must have the same directory structure as if you downloaded for real. This option is completely offline." [13:22] doesn't sound like a reset switch [13:22] dandrader: no clue what I did then :D [13:22] hahah [13:22] dandrader: I thought -p would be like --provision or something like that [13:22]