[05:14] <elopio> veebers: you are working on the nfss data file for app-startup, that's great.
[05:14] <elopio> I thought I would had to do it tomorrow.
[05:14] <elopio> you are kicking ass.
[05:15] <elopio> your email makes sense. I was hoping to upload one observation per test, but thomi doesn't seem to like that.
[05:16] <elopio> and as the project was already sending data, I think that for now we should stick with the same agregated format.
[05:17] <elopio> I hope tomorrow by the time you wake up I'll have the tests running and collecting the data, so we can just pass it through the export script.
[05:21] <veebers> elopio: awesome. How I understand it is that CI needs the results aggregated into a single file, so they will still be set per test, but it's just one file
[05:22] <veebers> elopio: if you could review the 2 MPs that I have for my cards that would be great, then I can move them to Done in prep. for Fri morn
[05:22] <elopio> veebers: yes, I get that part. What I mean is that thomi is suggesting on the document that on the dep8 tests we do a loop of 10 tests or so, and send to nfss the agregated results of those 10 tests.
[05:22] <veebers> oh, I don't know anything about that sorry :-P
[05:24] <elopio> veebers: I've just left my comments on two of your branches. Am I missing one? I
[05:24] <elopio> 'm not sure which are the 2 you are referring to.
[05:24] <veebers> elopio: no that should be it, let me check
[05:25] <veebers> elopio: hah, damn ipdb :-\
[05:27] <elopio> veebers: that's why I commented about testing the scripts. A simple and quick test would have caught that. I just don't know where to put it.
[05:28] <veebers> elopio: yeah, I wrote tests for the memevent one, but after that felt it was out of scope
[05:28] <veebers> but you're right, tests for that would be nice
[05:28] <veebers> I'll see what I can come up with tomorrow
[05:29] <veebers> elopio: what's your reason for wanting single quotes over double? (I understand having it consistent, which I haven't here)
[05:31] <elopio> veebers: that's what most people on QA preferred, according to my quick poll some months ago. As long as it's consistent, I'm ok. But I would love consistency between all our projects.
[05:32] <veebers> ack fair enough
[05:38] <veebers> elopio: I have made your suggested changes on both those MPs, I'll add a readme tomorrow, but for now I'm off for the night
[05:40] <veebers> elopio: one request, with the app-startup tests, can you provide the results to me in an email or something, so I don't have to spend time running the tests etc. just to get results to test the nfss-generator script against?
[05:50] <elopio> veebers: sure, no problem.
[05:51] <elopio> let me see what I get tomorrow.
[06:11] <veebers> awesome, cheers leo
[06:11]  * veebers is out o/
[06:19] <pitti> Good morning
[10:02] <dkessel> good morning pitti
[10:03] <dkessel> balloons: i just froze unity-next in preparation for the UOS session :p
[10:04] <pitti> hey dkessel
[10:04] <elfy> balloons is going to be "I hate the day after a day off" today ;)
[10:04] <elfy> morning pitti
[10:04] <dkessel> heh
[13:23] <balloons> elfy, :-)
[13:23] <balloons> good morning!
[13:23] <elfy> hey balloons - welcome to day 1 of your 3 day nightmare :D
[13:24] <balloons> I do believe yesterday was day 1 :p
[13:24] <elfy> I'm going to try to get to the manual testing session - but the mention of phones fills me with sense of depreciating interest ;)
[13:25] <elfy> there's a few I'll try to get to this week
[13:29] <elfy> balloons: thanks for doing that will cooke thing - couldn't see any way to do that - at all, I looked for the manual but couldn't find it :p
[13:29] <stblack> Hi! where I can find something about old UDS ? i.e. 14.06.
[13:31] <balloons> stblack, was it online?
[13:31] <dkessel> i think it is still there: http://summit.ubuntu.com/uos-1406/
[13:31] <balloons> elfy, heh, phones are something we should consider. Most of the "real" discussion will be on the tracker
[13:32] <balloons> stblack, yep dkessel is correct. If it was an online summit, it's still there; the links should still work and the videos too
[13:32] <elfy> balloons: when I have a phone I'll consider it :) couldn't get involved in testcases for it - I'd have to guess :p
[13:35] <stblack> thanks balloons, I was wrongly looking for uds-1406, not uos.
[15:52] <Letozaf_> balloons, hi
[15:59] <balloons> Letozaf_, hello
[15:59] <balloons> Letozaf_, joining fm session?
[16:00] <Letozaf_> balloons, yes
[16:01] <Letozaf_> balloons, sorry but I arrived late at yesterday's filemanager meeting, think I got the wrong time
[16:01] <balloons> Letozaf_, I was away all day national holiday for me, so I certainly missed :-)
[16:02] <balloons> you can ask in the hangout about times for meeting
[16:02] <Letozaf_> balloons, yes
[16:02] <alesage> pitti may I have a few minutes with you before your EOD?  I'm trying to launch an app on device (via adt) as root (needs to run as root), and getting a d-bus denial--attempting to su to a normal user isn't helping, any advice? http://pastebin.ubuntu.com/8929277
[16:03] <pitti> alesage: oh, you put the device into r/w mode?
[16:03] <alesage> pitti I believe so, yes--should I put the device into r/w mode?
[16:04] <pitti> alesage: well, preferably not, but if your test wants to change things in /etc/init, you have to
[16:04] <pitti> alesage: anyway, 3.6git1 doesn't work with current touch images any more, can you please use 3.7.1 from vivid?
[16:05] <pitti> alesage: http://archive.ubuntu.com/ubuntu/pool/main/a/autopkgtest/autopkgtest_3.7.1_all.deb
[16:05] <alesage> pitti, I am cleaning up /var/crash and so need r/w
[16:05] <pitti> alesage: you can install that .deb from precise upwards
[16:05] <pitti> alesage: /var/crash/ shoudl be writable anyway, though
[16:05] <alesage> pitti ok will verify
[16:05] <alesage> pitti I'm hearing you say "should work", yes? :)
[16:06] <pitti> alesage: I don't know your particular test, and presumably su etc. will cause some trouble, but let's at least rule out that it's due to something I already fixed
[16:07] <alesage> pitti ok thanks, let me have another go
[16:08] <pitti> alesage: also, your second sed command is likely broken -- it won't expand the local $CRASH_ID from the script, but instead will add $CRASH_ID verbatim to /etc/init/whoopsie.conf
[16:08] <pitti> alesage: powerd-cli display on bright -> that bit is already taken care of by the adb setup script, you can drop it
[16:09] <alesage> pitti ok for mini-review, will amend
[16:43] <alesage> pitti ok this is on a fresh image, no r/w, 3.7git1--this is essentially what I need to do in my adt script: http://pastebin.ubuntu.com/8967208/ --is there a more correct way to launch an app from within autopilot?
[16:43] <alesage> pitti (i.e. more correct than using ubuntu-app-launch)
[16:44] <pitti> alesage: yeah, you can't run apps as root, they don't have an upstart session running
[16:44] <pitti> alesage: that needs to happen as phablet
[16:45] <alesage> pitti would su'ing over give me the right env to do so, do you think?
[16:45] <pitti> alesage: I'm not sure, I suppose through the sudo/su/su you are losing env variables, but it's worth a try
[16:46] <alesage> pitti confirmed, yes I'm able to do (with --login)
[16:46] <pitti> alesage: the other q is, why do you need root privs in the first place?
[16:46] <alesage> pitti well b/c of the whoopsie tinkering
[16:47] <alesage> pitti possibly we have a different schema for that, handing over to CI, will verify
[16:47] <alesage> pitti thanks for the coaching
[16:47] <pitti> alesage: the whoopsie bits could be done in --setup-commands, and then your actual test would jsut run as user
[16:48] <alesage> pitti hmm ok thx will look into
[16:48] <pitti> alesage: calling sudo out of your test makes it very specific to current touch, and you somehow need to put the passphrase into the test (and then assume that whoever runs the test uses that)
[16:49] <pitti> sorry, need to run out, time for sports
[16:49] <alesage> pitti all of this is true, yes--agreed it's better as user, will depend on how CI prefers to set up (will ask in standup today)
[16:49] <alesage> pitti enjoy!
[18:11] <balloons> knome, will you be about for http://summit.ubuntu.com/uos-1411/meeting/22340/improving-manual-testing/ which is in 50 mins?
[18:11] <balloons> knome, I'm thinking about showing the UI mockup you did again. thoughts?
[18:43] <elfy> balloons: I'm kind of going to be about for that session
[18:43] <balloons> elfy, awesome. I put the mockup in the notes
[18:43] <elfy> yea - read those ;)
[18:44] <elfy> got someone visiting at some point - and I've got a wicked cough so might be just on irc
[19:00] <brendand> balloons, i'm here
[19:00] <balloons> brendand, awesome, check pm
[20:06] <Letozaf_> balloons, have you got time for filemanager app now ?
[20:07] <balloons> Letozaf_, I saw that it didn't work for you.. but it works locally? in both phone and tablet mode?
[20:07] <balloons> Letozaf_, btw, it would be cool to have launchers for both so the tests are duplicated and run during jenkins
[20:07] <Letozaf_> balloons, I tested the app on the desktop and on my nexus4
[20:08] <Letozaf_> balloons, the tests paseed but on jenkins one test fials
[20:08] <Letozaf_> fails
[20:08] <Letozaf_> balloons, the error is quite weired to me
[20:09] <Letozaf_> balloons, do you mean launch the tests with the -p and -b swtich ?
[20:09] <Letozaf_> switches
[20:11] <Letozaf_> balloons, by the way if I launch filemanager with the -p switch on desktop, the places side bar is displayed have to change the dimensioin of the window to the phone one to get the places side bar to hide and get the bottom edge for places
[20:12] <Letozaf_> dimension
[20:12] <balloons> Letozaf_, are you saying the -p doesn't work properly?
[20:12] <balloons> Letozaf_, and yes I mean run the tests under each mode
[20:12] <balloons> another MP though, not this one :-)
[20:12] <Letozaf_> balloons, ok
[20:13] <Letozaf_> balloons, I would expect the filemanager app to open with the phone dimensions with -p
[20:13] <Letozaf_> balloons, but it is a bit bigger and has the places side bar visible
[20:14] <balloons> Letozaf_, ok so that's probably something worth asking arto about. Did you talk about it today?
[20:14] <balloons> ideally it would be exactly the same.
[20:14] <Letozaf_> balloons, nope as I wasn't sure if I was getting this wrogn
[20:14] <Letozaf_> wrong
[20:14] <balloons> Anyways, to your error, if it passes locally that's confusing to me why it's not passing in jenkins
[20:15] <Letozaf_> balloons, http://91.189.93.70:8080/job/generic-mediumtests-vivid/156/testReport/junit/filemanager.tests.test_places/PlacesTestCase/test_go_to_root_must_open_the_root_directory/
[20:15] <Letozaf_> the MismatchError: After 10.0 seconds test failed: '/' != '/tmp/tmp2tsfl4lb'
[20:15] <Letozaf_> balloons, why is it in /tmp/tmp2tsfl4lb and not /
[20:15] <Letozaf_> balloons, is that right ?
[20:16] <Letozaf_> balloons, by the why with the -p switch you can read in the logs that the app is running in phone mode, but it's not what you seee
[20:17] <Letozaf_> balloons, Patched home to fake home directory /tmp/tmp2tsfl4lb
[20:17] <Letozaf_> balloons, shouldn't it be in /
[20:18] <balloons> Letozaf_, let me look at the test since you updated it
[20:18] <balloons> so I can be correct in my thoughts :-)
[20:20] <Letozaf_> balloons, if I run the app on my device and go to device place I go to / shouldn't that be the same on Jenkins?
[20:20] <Letozaf_> balloons, or maybe you use a temp directory for moking...
[20:21] <balloons> Letozaf_, right that's the issue
[20:21]  * balloons pulls code
[20:21] <balloons> Letozaf_, I think the only thing needing changed is what the assert looks for
[20:21] <balloons> it should look for the mocked / when it's mocked
[20:22] <Letozaf_> balloons, ok, so I got it wrong :P I thought that only home was mocked, I will look at the code again and figure this out
[20:24] <balloons> Letozaf_, ok I have the code
[20:25] <balloons> the difference between your local version and jenkins is that jenkins uses the debian package version
[20:25] <balloons> otherwise they are the same
[20:25] <Letozaf_> balloons, ah ok
[20:29] <balloons> Letozaf_, ahh right.. So look at test_go_home_must_open_the_home_directory
[20:29] <balloons> it asserts to self.fakehome
[20:30] <Letozaf_> balloons, so in the root directory test I suppose that if the test type is 'deb' I will have to assert to self.fakehome
[20:37] <balloons> Letozaf_, it's confusing to me actually why that is
[20:37] <balloons> I wouldn't do anything special for .deb no
[20:39] <Letozaf_> balloons, yea: Location:  "/tmp/tmp2tsfl4lb"
[20:39] <Letozaf_> Location:  ""
[20:39] <Letozaf_> Location:  ""
[20:39] <Letozaf_> Location:  ""
[20:39] <Letozaf_> Location:  ""
[20:39] <Letozaf_> Location:  ""
[20:39] <Letozaf_> Location:  "/"
[20:39] <Letozaf_> balloons, Location:  "/"
[20:39] <Letozaf_> balloons, it's /
[20:39]  * Letozaf_ is a bit confused
[20:39] <balloons> Letozaf_, if you read the log, home is set to Patched home to fake home directory /tmp/tmp2tsfl4lb
[20:40] <balloons> so '/' should not be the same as home
[20:40] <Letozaf_> balloons, the test that's failing is the root directory one
[20:40] <balloons> Letozaf_, lol ohh my. should have watched the video
[20:40] <balloons> Letozaf_, it fails to wait for the animation
[20:40] <balloons> simple fix
[20:41] <Letozaf_> balloons, how do get the video ? I tried to
[20:41]  * Letozaf_ blushes
[20:41] <balloons> http://91.189.93.70:8080/job/generic-mediumtests-vivid/156/artifact/filemanager.tests.test_places.PlacesTestCase.test_go_to_root_must_open_the_root_directory.ogv
[20:41] <Letozaf_> :P
[20:43] <balloons> Letozaf_, so _drag_Bottomedge_to_open_places or open_places should wait for the places page to load
[20:43] <balloons> Letozaf_, also I would make those methods all lower case instead of mixed case, to follow the rest of the app
[20:44] <Letozaf_> balloons, ok thanks
[20:44] <balloons> cool! Shold hopefully we a simple thing to fix
[20:44]  * balloons would put the wait_for in _drag_Bottomedge_to_open_places
[20:44] <balloons> hopefully there is an expanded property or ?
[20:45] <Letozaf_> balloons, thanks I will check now
[21:02] <knome> balloons, sorry, wasn't around... and feel free to show any of the stuff i've done :)
[21:03] <balloons> knome, no worries, it was a good session.. heh, but that I mean plenty o stuff for me
[21:03] <knome> ;)=
[21:43] <Letozaf_> balloons, I will fix the test tomorrow, I am tired and probably the two properties I tried to use on the places page aren't the right ones, I will find the "right" one tomorrow now I am KO :P
[21:44] <Letozaf_> balloons, good night :-)
[23:05]  * ianorlin is wondering why all of the reporting bugs documenation doesn't have a link to help describe different ui elements so they could use precise langauge and know the different ui elements they are talking about when writing a bug report
[23:06] <ianorlin> because if someone basically taught themselves how to use computers they and use them a lot they might not know ui elements are called to use in bug reports to be specific in what they are saying.
[23:07] <ianorlin> It is a lot easier to describe what is going on if you know what to call a widget
[23:20] <balloons> defining UI elements.. sadly they change :-(
[23:20] <knome> and defining them would mean somebody reading the bug report might need to double check
[23:21] <knome> describing them clearly enough in human-readable format is much better
[23:21] <knome> and doesn't take that much longer time
[23:29]  * balloons floats towards the light
[23:29] <knome> don't hit the sun, it'll blow you
[23:29] <knome> ..."blow" in the balloon-pop sense
[23:30] <knome> reminds me, should play the incredible machine some day
[23:47] <alesage> elopio, ping
[23:47] <elopio> alesage: pong
[23:47] <alesage> elopio in your DEP 8 travels have you ever discovered which scripts to use for provisioning?
[23:47] <alesage> elopio, and/or have you ever discussed with CI folks?
[23:48] <alesage> elopio, i.e. if LRT has special needs, I assume I'll be discussing with them but would like to get a head start
[23:48] <elopio> alesage: this should be ok for simple cases:
[23:48] <elopio> $ adt-run -B --built-tree=tests/app-startup --output-dir=output --- ssh -s adb
[23:48] <elopio> i.e, just set up ssh through adb, the phone will already be provisioned
[23:49] <alesage> elopio, yes I know how to run 'em, wondering if you've been exposed to the scripts they use to provision (they = CI)
[23:49] <elopio> now I'm having problems because my test needs root access. I'm not yet sure how to fix that.
[23:49] <alesage> elopio, there's a switch for that in debian/tests/control
[23:49] <alesage> (one sec)
[23:49] <elopio> alesage: I don't know about those scripts because they told us the phone will be provisioned, so I didn't dig more.
[23:49] <alesage> add Restrictions: needs-root
[23:50] <alesage> elopio, if you find yourself still blocked as again :) (my pw was set specially so I needed a special invocation of adt-run)
[23:50] <alesage> s/as/ask/
[23:50] <alesage> elopio, right, makes sense re: provisioning
[23:50] <elopio> alesage: I got SKIP Test needs root on testbed which is not available
[23:51] <alesage> elopio, one sec
[23:51] <elopio> I was missing -P 1234
[23:51] <elopio> to pass the password. Looks better now :)
[23:51] <alesage> elopio riight ok :)
[23:56] <elopio> alesage: I found that I don't need to run the tests as root. I just need to be able to sudo for one command
[23:56] <alesage> elopio, o ok interesting, and that works?  /me hadn't considered
[23:57] <elopio> no. I guess can sudo su phablet