[00:34] <robotfuel> elopio: I took care of the vivid issue so it will pass in both utopic and vivid
[01:16] <elopio> robotfuel: I don't like to have two different checks.
[01:16] <elopio> what I wanted was to ask zsombi or timp why it is different.
[01:16] <robotfuel> elopio: ok, I'll ask in the morning
[01:16] <elopio> if the versions on utopic is different from the version on vivid
[01:17] <elopio> then we should update only the test in the utopic branch.
[01:17] <elopio> but I think there's nothing like that.
[01:18] <elopio> robotfuel: my guess is that they are only landing things on 14.09, and the version I get on vivid is outdated.
[01:18] <elopio> in that case, the solution is to stop landing things on 14.09 and start doing it on vivid. 14.09 should be now only for hand-picked important fixes.
[01:19] <elopio> the text in the disabled gallery text field is clearly not an important fix.
[01:21] <elopio> robotfuel: also, IMO, a better intermediate solution while they fix the mess with the branches would be to check
[01:21] <elopio> self.assertNotEqual('This should not be written', textfield_disabled.text)
[01:22] <elopio> not ideal, but in combination with the other tests that check that clear and write work, it serves the same purpose.
[01:22] <robotfuel> elopio: I don't like that if the inpute is 'ths should not be written' it will pass
[01:22] <elopio> or something like this:
[01:22] <elopio> original_text = textfield_disabled.text
[01:22] <elopio> textfield_disabled.keyboard.type('This should not be written')
[01:22] <elopio> self.assertEqual(original_text, textfield_disabled.text)
[01:22] <robotfuel> elopio: +1
[01:23] <robotfuel> elopio: :D
[01:25] <robotfuel> elopio: I just pushed that change
[01:26] <elopio> robotfuel: I like that last one. Seems like a good improvement no matter the reason why it started failing, so +1 to the branch.
[01:26] <elopio> however, you found some important underlying issue that I wouldn't like to go unnoticed by us only doing a clever fix.
[01:26] <elopio> when they reply to you tomorrow, please let the QA team know why the versions are different.
[01:27] <elopio> I'm hoping this won't happen to the other projects, but it could be the case.
[01:27] <robotfuel> elopio: <timp> ChrisGagnon: we have only been pushing changes to rtm that were critical, which were very few changes
 ChrisGagnon: I didn't know we landed anything yet on vivid. But if vivid has our staging branch, then there can be some difference because we continue our development there
[01:28] <robotfuel> elopio: ^
[01:29] <elopio> robotfuel: thanks man.
[06:50] <pitti> Good morning
[07:24] <pitti> jibel: FYI, I enabled vivid-setup-testbed, we now have a /current symlink and the images work
[07:25] <pitti> \o/ no more daily manual dist-upgrading
[07:27] <elfy> morning pitti jibel
[07:27] <pitti> hey elfy
[07:57] <jibel> pitti, Great, thanks!
[07:57] <jibel> pitti, elfy good morning
[07:57] <pitti> bonjour jibel, ça va ?
[07:57] <jibel> pitti, ça va bien et toi?
[07:58] <pitti> jibel: je suis bien aussi, j'ai dormi bien à nouveau
[08:45] <dkessel> morning elfy pitti jibel quality :)
[08:45] <pitti> hey dkessel
[08:45] <pitti> wie gehts?
[08:47] <dkessel> danke gut, hoffe dir auch
[12:58] <average_guy> I am testing vivid-netboot-ppc and during the installation, the UK mirror is the only one presented tho it detects that I am in N. America. Is this normal/cool?
[15:33] <robotfuel> brendand: has the music-app smoke test ever had working test cases?
[15:33] <brendand> robotfuel, music-app is being replaced soon
[15:34] <brendand> robotfuel, well updated
[15:34] <robotfuel> brendand: so don't triage or try to fix the failing test cases?
[16:28] <elopio> what's the antonym of false positive?
[16:28] <elopio> true positive?
[16:28] <elopio> true negative?
[16:29] <slickymasterWork> elopio -> http://en.wiktionary.org/wiki/false_positive
[16:29] <slickymasterWork> according to ^^^^ it's false negative
[16:30] <elopio> slickymasterWork: a false negative is not what a want. I want the term for when we find a real bug
[16:30] <elopio> I will just say that: find a bug
[16:31] <slickymasterWork> well, clearer than that it's impossible
[17:13] <alesage> elopio would you show me your attempt to get the unity8 or toolkit autopilot suite under DEP8?
[17:13] <alesage> elopio, seems like you'd be the furthest along with the initial layout, etc.
[17:23] <elopio> alesage: I don't seem to have pushed any branches, nor I have the code in my machine.
[17:23] <elopio> I didn't go too far. The layout is pretty simple, make a script on debian/tests that runs your tests
[17:23] <elopio> and put the autopkg label on debian/control
[17:23] <alesage> elopio ok nw, righto, reading the spec
[17:24] <elopio> just by doing that, I found two big problems so didn't continue with autopkg
[17:24] <alesage> elopio, we were saying that the calculator has autopkg tests?  balloons?
[17:25] <elopio> alesage: it does. But for click packages the meta data is different than for debian packages.
[17:25] <elopio> it has more magic.
[17:25] <alesage> elopio right ok
[17:25]  * alesage goes for the source
[17:26] <elopio> alesage: http://packaging.ubuntu.com/html/auto-pkg-test.html
[17:26] <elopio> there are debian examples.
[17:27] <alesage> elopio, got it, right
[17:29] <dkessel> balloons: good job on the autopilot primer!
[17:29] <balloons> dkessel, glad you liked it..It's been sitting in draft since the summer :-(
[18:18] <dkessel> balloons: well you did finish it ;)
[18:19] <dkessel> balloons: I noticed there are no netboot images for vivid. Do these get activated later in the cycle?
[18:20] <elfy> http://archive.ubuntu.com/ubuntu/dists/vivid/main/installer-amd64/current/images/netboot/
[18:20] <balloons> ohh well, elfy is speedy
[18:21] <dkessel> Oh so it's just cdimage.u.c not listing it. Thanks elfy
[18:21]  * elfy elfy got one earlier to do the first xubuntu core test - otherwise he'd have not been :p
[18:22] <dkessel> Yeah wanted to do that too... Couldn't find the iso
[18:22] <dkessel> Guess that's a bug in the testcase
[18:23] <elfy> nope
[18:23] <elfy> we can't link to images as the test is for both 32 and 64 bit
[18:24] <dkessel> Ah ok
[18:25] <elfy> and if people are installing it we're kind of assuming they are ok dealing with the netboot installer and should be ok finding it
[18:26] <dkessel> Well I failed. This will put people off in my opinion
[18:29] <elfy> dkessel: when I am wanting people to do the test I'll be calling - the last one did actually point at the netboot iso's :)
[18:30] <elfy> I'm not able to start planning too far yet - not seen a release schedule for vivid <- balloons might have some idea if we'll see anything official soon :p
[18:32] <balloons> dkessel, yea I can understand.. Modifications to the testcase are always welcome
[18:32] <balloons> ohh, we never merged your code
[18:32] <balloons> too much excitement yesterday getting the site itself back up
[18:32] <elfy> balloons: you understand what about the testcase?
[18:33] <elfy> and while we're on about testcases - I fiddled with that usb creator one following your comments
[18:35]  * balloons is staying on target and testing dkessel's 2 changes now
[18:35] <dkessel> :)
[19:15] <alesage> balloons, could we have a few min with you this afternoon to walk through an adt-run test on the phone, from your blog post?  finding a "You must put some 'source' URIs in your sources.list" blockage
[19:17] <alesage> where by "we" I really mean "me"
[19:23] <balloons> alesage, lol, what are you trying to do with adt-run? test clicks on the phone or debian packages or ?
[19:23] <alesage> balloons, just running through this www.theorangenotebook.com/2014/07/a-new-test-runner-approaches.html , trying to do adt-run on device
[19:24] <alesage> balloons, http://pastebin.ubuntu.com/8823479
[19:24] <balloons> alesage, ahh sure. It's gotten easier since I wrote that
[19:25] <alesage> balloons, lay it on me :)
[19:26] <balloons> ok, so let's start very simple. To run the calculator tests for what's already on the device, adt-run --click=com.ubuntu.calculator --- ssh -s adb
[19:26] <alesage> ok
[19:26]  * alesage tries
[19:26] <balloons> alesage, also, https://people.debian.org/~mpitt/autopkgtest/README.running-tests.html
[19:28] <alesage> balloons, /me bookmarks thx
[19:30] <balloons> alesage, now, if you have local tests you'd like to use, you can see the syntax laid out there. you simply pass it as you where doing as the first arg
[19:31] <alesage> balloons ok I'm seeing the tests, although I'm seeing a series of apparmor denials?  resulting in no autopilot interface found?  (also dragged into standup mtg brb)
[20:01] <alesage> balloons nm btw, I see I need some device-setup
[20:05] <Letozaf_> balloons, doug5 hi
[20:08] <balloons> Letozaf_, howdy
[20:08] <Letozaf_> balloons, have you got news for filemanager app ?
[20:09] <elopio> It's a little bit harder to make an autopkg test if we don't have a deb package to start with.
[20:09] <Letozaf_> balloons, I tried compiling it and had no errors. but launching autopilot3 launch gives me an error
[20:16] <doug5> Letozaf_, hello
[20:17] <Letozaf_> doug5, hi
[20:18] <balloons> Letozaf_, paste of the error?
[20:18] <balloons> alesage, so you are a-ok then or ?
[20:18] <Letozaf_> balloons, http://paste.ubuntu.com/8822555/
[20:37] <balloons> Letozaf_, run from the build dir, not the in-tree build
[20:37] <balloons> qtcreator builds in a build directory outside of the branched code folder
[20:38] <Letozaf_> balloons, I used cmake and make... and got this https://dl.dropboxusercontent.com/u/10083981/Ubuntu%20errors/filemanager.png
[20:38] <Letozaf_> balloons, so I will build with qtcreator
[20:38] <balloons> Letozaf_, right we discovered you have to build with qtcreator for now
[20:39] <balloons> so do a fresh branch, open in qtcreator, buid it then use autopilot launch for the binary in the build dir
[20:39] <balloons> it's how I got it to work, and it didn't work otherwise :-)
[20:39] <Letozaf_> balloons, ok fine
[20:41] <balloons> Letozaf_, yea, we will have to spend some time later figuring out why the build is a bit weird
[20:41] <balloons> I spoke with Arto about it and he filed some bugs
[20:41] <Letozaf_> balloons, ok
[21:05] <Letozaf_> balloons, fyi everything is ok now, I have the phone on my desktop :P
[21:23]  * dkessel wonders if balloons is still on target ;)
[23:41] <elopio> nuclearbob: ping. Do you undesrtand the output of lttng?