[10:04] <luv> hi, I see on launchpad that there are new demands for the patch i contributed to unity - feel free to ping me if that's something i could help with
[10:06] <luv> though im wondering how it can vertically overflow the screen - even on netbook you would have to have open maybe twenty windows of the same application
[10:51] <didrocks> mmrazik|lunch: shouldn't lp:dbus-test-runner move to the qa stack?
[11:01] <mmrazik> didrocks: I don't know/mind. The only thing that puzzles me is that in matter of fact its now an "autopilot" stack rather than "qa" stack and making dbus-test-runner to block most of the other stacks sounds a bit strange
[11:02] <didrocks> mmrazik: it's a testing tool, I think it's part of what qa should look for as a long of PS components are depending on it, isn't it?
[11:04] <mmrazik> didrocks: yeah... that is one of the issues. QA isn't looking after that code. Ted is.
[11:04] <mmrazik> didrocks: but as I said... I don't really mind.
[11:04] <didrocks> mmrazik: ok, will probably move it soon
[11:04] <mmrazik> didrocks: I'm thinking of the stacks as primarily your domain
[11:04] <mmrazik> it doesn't really change much for us if it is in one stack or another
[11:04] <didrocks> ok :)
[11:05] <didrocks> mmrazik: I'll probably remove soon the "release" tag of the stack, I'll grep to see if you look for it before doing it though
[11:05] <didrocks> mmrazik: as we have the directory name duplicating the info"
[11:06] <mmrazik> didrocks: I'm fairly sure we don't use it
[11:06] <mmrazik> at least not now
[11:06] <didrocks> ok, great, I'll just double check in case
[11:19] <seif> didrocks, do you use a thinkpad?
[11:19] <didrocks> good morning seif
[11:19] <didrocks> yeah I do
[11:20] <seif> didrocks, are you also having issues with iwlwifi ?
[11:21] <didrocks> seif: what release and what kind of issue?
[11:21] <didrocks> I don't have any issue
[11:23] <mmrazik> didrocks: actually there is one thing with dbus-test-runner... can you ping me once the move is done? I'll need to cleanup the old, manually generated jobs and generate the new ones
[11:23] <didrocks> mmrazik: will do, not sure if it's today or tomorrow though, finishing other changes first
[11:24] <mmrazik> didrocks: ack
[11:34] <tsdgeos> mzanetti: new test here https://code.launchpad.net/~aacid/unity/autopilot_close_hud/+merge/152644
[11:34] <tsdgeos> mzanetti: whatcha think?
[11:36] <mzanetti> tsdgeos: in general, very good. small remarks:
[11:36] <mzanetti> tsdgeos: 29	+ self.assertThat(hud.shown, Eventually(Equals(True)))
[11:37] <mzanetti> tsdgeos: this doesn't seem to be useful as the property is already true.. depending on timing you could read the old property and only after this evaluates, the property changes
[11:38] <tsdgeos> i thoought about that
[11:38] <mzanetti> tsdgeos: also, this test if clicking outside the handle does NOT close it, doesn't seem to belong in the helper function
[11:38] <tsdgeos> but made it fail
[11:38] <tsdgeos> i.e. click it and hide
[11:38] <tsdgeos> and it did fail
[11:38] <tsdgeos> mzanetti: true
[11:39] <tsdgeos> i'll make a new test for it
[11:39] <mzanetti> tsdgeos: it most likely won't work any more when running in slow jenkins or on the device
[11:39] <tsdgeos> still have the problem of verifying it
[11:39] <mzanetti> tsdgeos: but thats it... really like the reast!
[11:39] <mzanetti> rest
[11:39] <tsdgeos> any suggestion?
[11:39] <mzanetti> tsdgeos: lemme thin
[11:39] <mzanetti> k
[11:40] <tsdgeos> besides a sleep...
[11:40]  * tsdgeos hides
[11:40] <mzanetti> tsdgeos: hmm... all I can come up with right now is to hackish... Seems we're lacking a way to make sure properties do not change
[11:41] <tsdgeos> yep
[11:42] <tsdgeos> the reverse of Eventually
[11:42] <mzanetti> tsdgeos: I think there is something like self.assertNot(), no clue how exactly it works tho... if you want you can give it a shot. otherwise I'll ask thomi if there is something we're missing
[11:44] <tsdgeos> mzanetti: so you prefer me to remove that for the moment, you approve it and then i work on how testing that clicking outside the handle does not hide it?
[11:50] <tsdgeos> mzanetti: ok, did that :-)
[11:50] <mzanetti> tsdgeos: fine with me... (sorry, too many people pinging at the same time right now)
[11:51] <tsdgeos> mzanetti: no worries :D
[11:59] <didrocks> mmrazik: moving dbus-test-runner, ok?
[12:00] <mmrazik> didrocks: ok
[12:02] <tsdgeos> mzanetti: the only thing i can think of is http://paste.ubuntu.com/5604576/ which is a bit lame but...
[12:03] <didrocks> mmrazik: done
[12:05] <tsdgeos> mmrazik: what is your opinion on ↑↑
[12:06] <mmrazik> mzanetti: ^^
[12:06] <mmrazik> tsdgeos: it was for mzanetti, right?
[12:07] <tsdgeos> mmrazik: well it was for him but if you give me your opinion as QA guy i'll take it :-)
[12:07] <mmrazik> tsdgeos: well.. for an external person it is quite hard to figure out all the stuff like (rect[0] + rect[2] /2) and rect[1] + 1
[12:08] <mzanetti> mmrazik: its more about line 27
[12:08] <mmrazik> I would either try get rid of that or at least add a comment so somebody else can understand
[12:08] <tsdgeos> yep
[12:08] <mmrazik> mzanetti: well.. he asked for an opinion :-P
[12:08] <tsdgeos> sure
[12:08] <mmrazik> yeah... that line looks weird too:)
[12:09] <mmrazik> anyway... feel free to ignore me
[12:10] <mzanetti> tsdgeos: hmm... this comes down to a sleep(3) and then assertThat(NotEquals()). Still I think the best shot we have so far
[12:10] <mzanetti> tsdgeos: Lets ask the New Zealanders about it
[12:11] <tsdgeos> mzanetti: ok, i'll put it in a separate MR
[12:11] <mzanetti> cool, thanks
[12:26] <tsdgeos> mmrazik: can i attribute the failure here https://code.launchpad.net/~aacid/unity/autopilot_close_hud_click_outside/+merge/152659 at the jenkins dns issues you mentioned?
[12:26] <mmrazik> tsdgeos: yes
[12:26] <tsdgeos> cool
[12:26] <mmrazik> srry for that :-/
[12:26] <tsdgeos> no worries :D
[12:49] <tsdgeos> mzanetti: so i'm planning to do more qml unittests, shall i not start them for the moment or we are confident we'll get them to run fine on the CI system?
[12:50] <mzanetti> tsdgeos: hmm... we have to get them to run fine in CI... but this is maybe something where mmrazik can help
[12:50] <mzanetti> mmrazik: our unit tests can't run with xvfb as QtQuick 2 requires OpenGL
[12:50] <mzanetti> mmrazik: any other idea?
[12:52] <mmrazik> mzanetti: what is the long term plan? It sounds like these are not unit tests if we need OpenGL. Are we waiting for working mir so we can mock-out mir and simulate what QtQuick needs?
[12:52] <mmrazik> mzanetti:  I fear the other option is a VM then.  We do have opengl in the VM, right?
[12:52] <mmrazik> I guess I need to try canonistack..
[12:53] <mzanetti> mmrazik: yes. VM should do. and yes, they are unit tests. but to instantiate QML objects its required to have some sort of opengl API
[12:53] <tsdgeos> mmrazik: it is a unit test, just a graphical one ;-)
[12:53] <tsdgeos> lunch bbl
[12:53] <mmrazik> mzanetti: sure.. I'm just wondering if we will be able to mock this out once we have unity on mir
[12:54] <mzanetti> I guess so, yes. have not much clue about Mir yet
[12:55] <mmrazik> tsdgeos, mzanetti: all-in-all: lets not start them right now but lets target a solution in a week or so.
[12:55] <mmrazik> I'll check if canonistack is of any help
[12:55] <mmrazik> and if we can get consistent results from it
[12:55] <mzanetti> mmrazik: ok
[12:55] <mmrazik> I fear our VMs are not stable enough
[12:55] <mzanetti> mmrazik: but arent all the Mir tests builds ands run in the VMs?
[12:56] <mzanetti> ... all the Mir builds and tests...
[12:56] <mmrazik> mzanetti: they are but not blocking ci/autolanding. OTOH they seem to be reasonable stable
[12:56] <mmrazik> mzanetti: maybe we can give them a try
[12:57] <mmrazik> mzanetti: changing my mind... lets try our VMs and see how it goes
[12:57] <mzanetti> mmrazik: ok. will you change the ci job or should I?
[12:58] <mmrazik> mzanetti: go for it, please
[12:58] <mzanetti> ok
[12:58] <mmrazik> mzanetti: mhm... but the VMs don't have the pbuilder chroot
[12:59] <mmrazik> mzanetti: where do you actually want to run these tests? in dh_auto_test?
[12:59] <mzanetti> mmrazik: yes
[12:59] <mzanetti> mmrazik: btw. are those executed in the ppa builds too? that could be another issue then
[12:59] <mmrazik> mzanetti: I fear that will fail them to build for ubuntu (I don't think the builders are going to have opengl)
[12:59] <mmrazik> mzanetti: ack
[13:00] <mzanetti> well... but we need that
[13:00] <mzanetti> somehow
[13:00] <mmrazik> mzanetti: but I think we need that only in jenkins. The easiest way to me sounds like a custom make target + pbuilder hook to run those tests
[13:07] <kenvandine> didrocks, yay... so looks like i get to exercise the c2ud tools to publish friends :)
[13:07] <kenvandine> it detected packaging changes
[13:41] <autoditac> hey all. how do add a custom, hard-wired mandatory launcher icon that users are not able to remove from the launcher  - like the nautilus "$home" launcher (12.04)? Judging from what i read in https://wiki.ubuntu.com/Specification/ConfigurationLockdown, lockdown isn't implemented, yet. but how do i set system-wide mandatory values for the launcher?
[13:42] <Squarism> what process handles the dock/dashboard? Or.. is there some service/proces i can restart if unity ui starts behaving?
[14:01] <didrocks> kenvandine: exactly!
[14:08] <mterry> What the heck?  The unity stack is green today?  First time in a long time
[14:17] <seb128> cyphermox, hey
[14:17] <seb128> cyphermox, is https://jenkins.qa.ubuntu.com/job/libappindicator-autolanding/build=pbuilder,distribution=coverity-raring,flavor=amd64/19/console a known issue with libappindicator's test?
[14:17] <cyphermox> hey
[14:17] <seb128> or it seems like the xorg test server is flaky?
[14:18] <cyphermox> the test issues had all been "fixed" but yeah they still tend to be flaky
[14:18] <seb128> trying to land https://code.launchpad.net/~seb128/libappindicator/clean-libindicate-buildeps/+merge/146137
[14:18] <cyphermox> saw it, working on fixing this if I can
[14:18] <seb128> the change is only to the debian/control so I doubt it's making the test fail :p
[14:18] <seb128> cyphermox, thanks?
[14:18] <seb128> cyphermox, thanks
[14:18] <seb128> should I just retry to approve it meanwhile?
[14:19] <cyphermox> I'll ask for jenkins to retry
[14:19] <seb128> thanks
[14:20] <seb128> cyphermox, what about https://code.launchpad.net/~seb128/ubuntu-themes/nautilus-icon-update/+merge/152270 ?
[14:21] <cyphermox> yeah that should pass too, but there was an issue in the qa lab
[14:21] <seb128> cyphermox, see other channel ;-)
[15:40] <kenvandine> mhall119, i have branches of qml-friends that add a Poster component and FriendsModel
[15:40] <kenvandine> mhall119, i think with the addition of FriendsModel, the twitter and facebook apps can be pure qml
[15:41] <kenvandine> mhall119, FriendsModel is only capable of filtering on streams so far, i need to figure out how to deal with a list<int> to deal with filtering by account
[15:42] <mhall119> kenvandine: can I request a name change?
[15:42] <mhall119> FriendsModel, in my mind, would return a list of Friends, not status updates
[15:43] <mhall119> maybe FriendsFeedModel?
[15:44] <kenvandine> FriendsStreamModel?
[15:44] <kenvandine> Feed is ok...
[15:44] <mhall119> stream works too
[15:44] <kenvandine> in friends we use the term stream
[15:44] <mhall119> that way we can have FriendsContactModel or FriendsPersonModel in the future
[15:44] <mhall119> stream then
[15:44] <kenvandine> for messages, images, mentions, private, links
[15:44] <kenvandine> etc
[15:44] <mhall119> works for me
[15:44] <kenvandine> i don't like the sS in there though :)
[15:45] <mhall119> Why, not, it's sssssuper!
[15:45] <kenvandine> hehehe
[15:45] <kenvandine> we are super-friends :)
[15:45] <mhall119> dum-dum-da!
[15:46] <davmor2> kenvandine, mhall119: just call it bad-dum-tish
[15:46] <kenvandine> :)
[15:46] <kenvandine> i could just call it StreamModel
[15:46] <kenvandine> in the Friends namespace
[15:46] <mhall119> kenvandine: that would work
[15:46]  * kenvandine would have to figure out how to deal with namespaces
[15:47] <kenvandine> but i think it might be cleaner
[15:47] <kenvandine> actually i don't :)
[15:53] <kenvandine> mhall119, renamed :)
[15:54] <mhall119> kenvandine: does it all work on the desktop?
[15:54] <mhall119> and are there packages somewhere that the Facebook/Twitter core app developers can use?
[15:54] <kenvandine> not with this merged
[15:54] <kenvandine> qmlfriends is in raring and the PPA for quantal
[15:55] <kenvandine> i need to write tests and docs before i propose the branch
[15:55] <kenvandine> but now it is super easy to setup with a listview
[15:55] <kenvandine> ListView { model: StreamModel {} }
[15:55] <kenvandine> of course you need more in the listview, a delegate and such
[18:04] <mterry> How do I run autopilot tests in lp:unity/phablet?  I get "Unable to find autopilot interface"
[18:10] <mterry> mzanetti, ^
[18:11] <mzanetti> mterry: you most likely don't have libautopilot-qt installed.
[18:11] <mterry> mzanetti, I don't...  Let me retry, thanks
[18:12] <mzanetti> mterry: sent you a mail
[18:15] <mterry> mzanetti, thanks, will follow it and may bug you with further questions  :)
[18:17] <mzanetti> mterry: sure. hf
[18:25] <jP_wanN> hello there
[18:25] <jP_wanN> is anyone here who knows about the unity internals?
[18:26] <jP_wanN> I'd like to know the relation between Unity and Compiz
[18:27] <bschaefer> jP_wanN, what about the relation ship are you interested in?
[18:28] <jP_wanN> does Unity rely on Compiz or does it just use Compiz for the window management (and one could also use another window manager with Unity)?
[18:28] <bschaefer> jP_wanN, unity is plugin to compiz
[18:29] <bschaefer> jP_wanN, and using a different WM for unity (with unity at trunk) would be a lot of work arounds in the main unityshell.cpp file but we do have some abstractions for
[18:29] <bschaefer> different WMs
[18:29] <jP_wanN> that sounds interesting
[18:30] <bschaefer> jP_wanN, the bigger problem about moving to a different WM is unity/plugins/srccd
[18:30] <jP_wanN> I'm particularly interested in using Unity (the panel, the HUD and perhaps the launcher too) with i3
[18:30] <bschaefer> opp, umm the unityshell.cpp uses a bunch of compiz/plugin handling
[18:31] <bschaefer> jP_wanN, well each component has a standalone client
[18:31] <bschaefer> hud/dash/launcher/etc (Im not 100% sure about the panel)
[18:31] <bschaefer> yes there is a standalone panel
[18:31] <jP_wanN> well but there is only one unity process...
[18:32] <jP_wanN> right?
[18:32] <bschaefer> jP_wanN, yes, but the standalone app are most for testing
[18:32] <jP_wanN> so I could just build those myself and try to add them to the i3 autostart? :D
[18:33] <bschaefer> jP_wanN, but the standalone apps just use Nux/Unity
[18:33] <jP_wanN> ?
[18:33] <jP_wanN> what's nux?
[18:33] <bschaefer> jP_wanN, unitys toolkit (for drawing the hud/dash/launcher/etc)
[18:34] <jP_wanN> okay...
[18:34] <jP_wanN> so would it be possible to download or build the standalone apps and just try to run them inside i3?
[18:35] <jP_wanN> (would I have a chance that would work?)
[18:35] <bschaefer> jP_wanN, hmm im not sure what i3 is :), but i've also not tried building just the standalone app on their own
[18:35] <bschaefer> jP_wanN, I would assume you could, but you would need Nux/Unity/ and a bunch of smaller libs unity uses (like libunity)
[18:36] <jP_wanN> well I've got a normal Ubuntu install
[18:36] <jP_wanN> so I should already have everything it requires
[18:36] <jP_wanN> I just installed i3 there
[18:36] <jP_wanN> i3 is a bunch of programs
[18:37] <bschaefer> jP_wanN, well first, you could try to build unity with compiz, and check out the stand alone app in the build dir
[18:37] <jP_wanN> i3-wm is a tiling window manager
[18:37] <jP_wanN> and there are some other i3-programs, a lock screen and a panel
[18:37] <bschaefer> jP_wanN, but there should be a way to compile the standalone app with out compiz...
[18:37] <jP_wanN> okay I'll try
[18:38] <jP_wanN> well I'll first download the unity source
[18:38] <jP_wanN> that will probably take some time with my internet connection
[18:39] <bschaefer> jP_wanN, yeeah, its a bit large, but look at the standalone dash/hud/panel/launcher
[18:41] <jP_wanN> okay. if I don't find it, I'll ask here again ^^
[18:42] <bschaefer> jP_wanN, a problem you might run into is without compiz CMake will most likly complain (though there could be a flag that will turn standalone off/on...)
[18:43] <jP_wanN> well first the download, then I can see if there are problems :D
[18:43] <bschaefer> :)
[19:27] <mterry> fginther, this seems misconfigured: https://jenkins.qa.ubuntu.com/job/phablet-unity-ci/build=panda-pbuilder,distribution=quantal,flavor=armhf/754/console
[19:28] <fginther> mterry, looking
[19:32] <fginther> mterry, there have been some intermittent networking issues in that datacenter. I've restarted it.
[19:38] <mterry> fginther, k, thanks!