[08:33] <DrManhattan> I have upgraded my samba to version 4.1.6 but Im still getting the talloc memory leak error. Is there any way I can keep samba password sync to user accounts and get rid of this memory error? no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory
[14:19] <elopio> good morning.
[15:29] <elopio> ping rhuddie, about the launching click app.
[15:30] <rhuddie> elopio, hey
[15:30] <elopio> rhuddie: hello.
[15:31] <elopio> rhuddie: can you please add a card for the application custom proxy object, and put an estimate on it.
[15:31] <elopio> hopefully, we will have time at the end to document it.
[15:32] <elopio> rhuddie: and, about the last part of launching with qmlscene, I was referring to do it from a test.
[15:32] <elopio> qmlscene would be the binary to launch, and the qml file the argument.
[15:32] <rhuddie> elopio, ah, I was going to check with you about that
[15:32] <elopio> so it would be something like self.launch_test_application('qmlscene', '....qml')
[15:33] <rhuddie> right
[15:33] <rhuddie> I'll add the card and make that update
[15:34] <elopio> rhuddie: http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/view/head:/tests/autopilot/ubuntuuitoolkit/base.py#L47
[15:34] <elopio> I'm not sure if we should document that's the function we should use. It feels like it's in the wrong module.
[15:34] <elopio> but in many cases, you need to pass the full path to qmlscene, and that depends on your arch.
[15:37] <elopio> rhuddie: and lastly, this doesn't work for all click applications. Some will need to be compiled and launched from the binary they generate.
[15:37] <elopio> rhuddie: "A click application can also be launched directly from source."
[15:38] <elopio> maybe instead you can say, the main qml file of some click applications can be launched directly from source.
[15:39] <rhuddie> elopio, I'll do that
[15:39] <elopio> rhuddie: thank you.
[15:40] <elopio> rhuddie: veebers didn't reply about the failing tests, so I think we'll have to wait until monday to merge all your branches.
[15:41] <rhuddie> elopio, ok. I ran your new test this morning and got it to work
[15:41] <elopio> paulliu: I will touch a little your rotation branch, so we can have a branch for everybody to review. I'll send you the MP by mail, in case I finish too late for you.
[15:42] <elopio> rhuddie: yes, in order to run the autopilot tests from source you have to do like
[15:42] <elopio> python3 -m autopilot.run run autopilot.tests.functional...
[15:42] <elopio> otherwise it will use the installed ones.
[15:42] <elopio> it took like a month for me to realize that. I used to rely only on jenkins results :)
[15:43] <rhuddie> elopio, well, you learn something new every day.... I'll make of that one!
[15:49] <balloons> elopio, rhuddie :-) Do we think the docs could be more explicit about that . . . because you know, we are updating them
[15:50] <elopio> balloons: I think so. Can you please write two cards, and estimate them. One for documenting on the readme how to run the tests, and one for documenting on the readme how to generate the docs?
[15:50] <balloons> elopio, sure thing
[15:50] <elopio> balloons: thanks.
[16:01] <alesage> elopio IMO let's stop adding cards else the work will "expand to fit" the sprint as for the last few
[16:01] <alesage> need to plan better if we're not really serving the story
[16:03] <elopio> alesage: we need the cards. I'm not sure if we have to move them to the backlog, or to do them this sprint.
[16:03] <elopio> that's something to discuss in our meeting.
[16:04] <balloons> alesage, I agree in principle, but they are 2 hour tasks. In addition, I feel like this might be a natural thing and thus we should plan a buffer of hours which we intend to fill
[16:04] <balloons> does that turn afoul of scrum?
[16:05] <alesage> elopio, balloons, just don't want to ride off the rails, we'll discuss; balloons imagine we're billing (as if we're not really :) )
[16:09] <balloons> alesage, it's a somewhat outlandish idea, no worries about knocking it down. But if I was billing I would most certainly adjust it into my estimate, or set expectations. It's not work we're forced to do, simply something that needs done which is 'on sale' because we're already working in that area
[16:09] <balloons> I would upsell it if billing by the hour, or try to squeeze it in as a value-add if billing contractually
[16:10] <alesage> balloons, I like the "on sale" idea :)
[16:10] <balloons> "it'll never be cheaper"
[16:10] <alesage> :)
[16:14] <alesage> weird scenario in that you're both the client and resource here balloons
[16:15] <balloons> elopio, have you updated the template for autopilot tests in qtcreator yet?
[16:18] <balloons> if so, I'd love to have it
[16:18] <balloons> I just wanted to have a peek at the ap tests ofc
[16:21] <knome> balloons, if elopio and alesage aren't billing you, can i?
[16:21] <knome> :P
[16:21] <balloons> ahh knome, I knew you could offer something on this subject :)
[16:21] <knome> of course
[16:21] <knome> i can make you an offer you can't deny
[16:22] <balloons> always compelling knome
[16:22] <knome> not if it involved blackmailing ;)
[16:22] <alesage> we need a currency based on Launchpad karma
[16:22]  * knome gets some coffee
[16:23] <knome> alesage, if only the launchpad karma would be an accurate figure of how much you have contributed to *anything* in ubuntu...
[16:24] <rhuddie> elopio, I made updates to the click mp, but I didn't mention get_qmlscene_launch_command(), as it seemed like the wrong place to mention it
[16:25] <knome> besides, wouldn't that mean canonical employees should decide if they take their salary in money or karma :P
[16:25] <alesage> personally I do it for the t-shirts
[16:26] <knome> hah :)
[16:26] <elopio> rhuddie: +1
[16:45] <rhuddie> balloons, for autopilot launch, you mentioned -t parameter for specifying toolkit. I can't find mention of that, do you mean -i ?
[16:46] <balloons> rhuddie, indeed I do sorry about that
[16:46] <balloons> rhuddie, I was just looking at https://code.launchpad.net/~canonical-platform-qa/autopilot/launch-cmd-doc/+merge/246601; I'm working on the tutorial re-write, and I'm wondering if it might be easier for you to not update the references to python3 so my mp goes in easier
[16:47] <balloons> or I should just depend on yours
[16:47] <balloons> I think I'll just merge yours and depend on it as it should be set soon
[16:47] <balloons> nvm
[16:48] <rhuddie> balloons, I don't mind. quite happy to remove the 3s from mine. then all my changes are in 1 place and easy to merge
[16:53] <balloons> rhuddie, thanks. I'll do the updates as I go then
[16:54] <rhuddie> balloons, no problem
[17:22] <elopio> balloons: I'm not working on autopilot for qtcreator. At least not yet.
[17:22] <elopio> what I updated was the qml template.
[17:23] <balloons> elopio, ack, no worries I just carried on myself anyway
[17:23] <elopio> and after our meeting and lunch, I'll need to re-merge it, so it's not done yet.
[17:23] <balloons> mmm.. lunch
[17:24] <elopio> balloons: even better, lunch not cooked by me, but by somebody who knows how to cook, my mother-in-law :)
[17:24] <elopio> there's plenty, you should come.
[17:25] <balloons> elopio, wonderful. Food by someone who can cook is always welcome
[17:32] <alesage> elopio, rhuddie balloons forgot that we don't have a standup today :)
[17:32] <balloons> alesage, I realized the same, but went to the hangout anyway
[17:34] <elopio> https://plus.google.com/hangouts/_/canonical.com/qa-scrum?authuser=1
[17:34] <elopio> alesage: balloons: rhuddie: charles: can you join please?
[17:34] <elopio> it's an error that we don't have a standup in the calendar for today.
[17:35] <alesage> charles, care to hop on for a sec?
[17:35] <alesage> balloons too :)
[17:49] <sak> balloons are you their?
[17:50] <balloons> hey sak, I am indeed
[17:51] <sak> Awhile back, I was maintaing, or trying to create test cased for two ubuntu packages, vimo and other I can't remember.  would like to get back into package maintaining. Is this on option for QA testers?
[17:52] <balloons> sak, maintaining the test or the package?
[17:52] <sak> I think that was what I was doing.
[17:52] <balloons> if you want to help maintain tests that is always welcome and definitely possible. elfy loves to see people helping out :-)
[17:52] <sak> The test, I think
[17:53] <sak> Is there a list of packages that needs test cases?
[17:54] <balloons> sak, https://bugs.launchpad.net/ubuntu-manual-tests, and you can use the tags to find bugs specific to a flavor, or things that are easy (bitesize)
[17:55] <sak> Thanks
[17:57] <sak> Also, is launchpad used as the central news site for anything or everything related to ubuntu development , testing milestones and beta releases?
[17:58] <balloons> sak, planet.ubuntu.com is helpful for a what's what. Specific to testing, you can use the qa calendar
[17:58] <balloons> https://wiki.ubuntu.com/QATeam/Calendar
[17:58] <balloons> following ubuntu, ubuntu qa, etc on social media also helps
[17:59] <sak> ;-)
[18:05] <balloons> sak, also don't be a stranger on IRC, plenty of folks idling here happy to help you out or chat :-)
[18:08] <sak> Ok, I will try to be more active here. I figured if not related to QA, there wasn't much to say
[18:10] <charles> elopio, sorry I didn't join, you're right I didn't think there was a standup today b/c of your comments yesterday and it not being on the calendar today
[18:10] <balloons> sak, speaking personally I like channels to feel alive. Feel free to say hello anytime
[18:10] <charles> elopio, did alesage discuss the code we've been working on?
[18:12] <sak> Hello!!! LOL. balloons, you got
[18:14] <balloons> sak, :) Howdy! I think you'll fit right in here
[18:17] <elopio> charles: if you can go to the document and update your status there, it would be great.
[18:17] <elopio> charles: sorry about the meeting. I still don't know how to move it from nz monday to rest-of-the-world friday
[18:19] <sak> Have to go. Thanks for the helping balloons ;-)
[18:23] <elopio> I'm doing a mess and the calendar is still not updatig :@@
[18:24] <elopio> charles: balloons: alesage: next week stand ups will be one hour from now, at 19:30 UTC.
[18:24] <elopio> I'll keep trying to fix the calendar.
[18:24] <balloons> elopio, just to keep us on our toes?
[18:24] <charles> elopio, ack
[18:25] <elopio> balloons: you lost me :) Can you translate that to plain english?
[18:25] <charles> balloons, maybe different participants & he's trying to find the median time for the timezones
[18:26]  * alesage now wonders about the origin of balloons' phrase
[18:26] <elopio> I'm just going back to the original time. Next week we'll have thomi and veebers.
[18:26] <balloons> elopio, you are moving the time for the meeting just as we've gotten used to it. The 'just to keep us on our toes' is an idiom meaning keep us attentive and guessing
[18:26] <elopio> balloons: got it :)
[18:27] <elopio> I was confusing toes with ankles. That was a lot harder to picture...
[18:29] <balloons> elopio, right, I suppose on your toes instead of on your feet means you are nimble
[18:29] <balloons> ready to react :-)
[18:29] <balloons> idioms are so fun
[18:30] <elopio> we could do that. Surprise stand ups, whenever someone feels like bothering the rest :D
[22:45] <sak> someone please tell summer to speed up. Could not feel my hands for a good 5mins after I got home