[05:05] <elopio> vila: it worked the second time I ran it.
[05:05] <elopio> the first time it gave an error about timing out waiting for login. Not sure what that's about.
[05:39] <vila> elopio: O_o you got a log or something ?
[05:39]  * vila yawns
[13:19] <vila> elopio: did I mention that with the latest changes the same dep8 tests runs on the phone, the archive and -proposed ?
[13:20] <elopio> vila: \o/
[13:20] <vila> ^_^
[13:20] <elopio> so we are ready to get the MP reviewed by the dev, right?
[13:20] <vila> that's what I asked you in my last comment yes
[13:21] <vila> elopio: keep in mind that since those are new dep8 tests, they won't block promotion if they fail at first
[13:21] <vila> elopio: they will need to succeed at least once and *thne* they'll block ;)
[13:22] <elopio> oh, that's handy.
[13:22] <vila> kudos to jibel&pitti
[13:22] <elopio> vila: lets get a review from oSoMoN and pitti.
[13:22] <elopio> https://code.launchpad.net/~canonical-platform-qa/webbrowser-app/autopkgtest/+merge/256858
[13:22] <pitti> wut?
[13:23] <elopio> also, anybody else from ubuntu-qa who wants to chime in ^
[13:23] <pitti> oh yes, ISTR that it was mentioned on the ML, but after two sprint weeks I'm hopelessly behind in mails
[13:23] <elopio> pitti: it's a branch to run the browser autopilot tests as dep8.
[13:23] <vila> right, I'm not sure all the tricks I used are really... well, I'd be happy to have pitti's feedback on them indeed ;)
[13:23] <pitti> elopio: nice work!
[13:26] <elopio> pitti: well, lots of people involved to get this to work, with yourself first in the list :)
[13:27]  * vila nods . o O (ubuntu-touch-sessioin)
[13:29] <brendand_> elopio, bing
[13:29] <brendand_> elopio, i chimed. nothing major
[13:29] <elopio> balloons: bong.
[13:29] <brendand_> oh boy balloons is going to be deeply confused
[13:30] <elopio> brendand_: agree with your comment.
[13:30]  * balloons scratches head
[13:30] <elopio> and btw, now we are in a better shape to document this in a central place instead of the README.
[13:30] <elopio> do you have any recommendations for a good place in the wiki?
[13:31] <balloons> pitti, did alesage ping you about showing off adt as a demo session @ UOS?
[13:31] <balloons> elopio, a good place for ?
[13:31] <vila> elopio: by the way, you mentioned a login issue on first run ? Details ? Did you get logs for that ?
[13:34]  * balloons suddenly feels the bong was for brendand_ 
[13:34]  * balloons feels left out
[13:36] <brendand_> balloons, hey whoah man - i don't do drugs okay!
[13:38] <pitti> elopio, vila: reviewed the MP
[13:38] <pitti> balloons: no, not yet
[13:39] <balloons> pitti, we're soliciting folks to give cool demos, and alesage mentioned perhaps showing off adt would make a nice demo. It would be cool to see the different / novel ways it can be used
[13:40] <balloons> and/or if you have some other pitti created goodness to show off, feel free :-)
[13:40] <vila> pitti: ghaaaa, I tried set +a instead of set -a....
[13:40] <pitti> just boring boot stuff last cycle
[13:41] <pitti> so if anything there, I could demo some ways how to do boot speed and debug stuff now
[13:41] <elopio> balloons: good place to write the steps to run the dep8 tests and analyze the results.
[13:42] <balloons> pitti, ohh right.. I imagine the bootspeed chart and hackery has changed eh
[13:42] <vila> pitti: thanks for the review ;-D I stumble across many things and didn't mention them all (but some hints in the history), you found them all and then some \o/
[13:43] <vila> pitti: about needs-recommends, I wondered if python3-evdev should move to Depends in autopilot-touch ?
[13:44] <balloons> elopio, hmm.. we have a page on autpkgtest already, let me dig it up. It might make sense there
[13:44] <pitti> https://wiki.ubuntu.com/Touch/Testing#Running_tests_with_autopkgtest
[13:45] <pitti> http://packaging.ubuntu.com/html/auto-pkg-test.html
[13:45] <pitti> those are the two I'm aware of, aside from the docs that autopkgtest ships itself
[13:46] <vila> pitti: i.e. I thought using needs-recommends may install too much or something (will use it for now)
[13:50] <elopio> pitti: ahh, right. That's actually a good place to document about trv.
[13:50] <elopio> we should probably clean it up a little and push it to the archive.
[13:52] <balloons> elopio, yea pitti linked the page I was thinking of
[13:52] <balloons> and yea, upstream as well: http://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/tree/doc/README.package-tests.rst
[13:54] <pitti> jibel: http://d-jenkins.ubuntu-ci:8080/view/Vivid/view/AutoPkgTest/job/vivid-adt-libanyevent-cachedns-perl/
[13:56] <vila> pitti: ADT_NORMAL_USER is only set for setup-commands, not for tests (IIRC my late-night readings). Should it ?
[14:09] <pitti> vila: err yes, it absolutely should; it's not supposed to be set for setup-commands
[14:09] <pitti> (it might be, but not specified)
[14:10] <pitti> vila: oh sorry, you are right
[14:10] <pitti> I totally misremembered what this was for
[14:20] <vila> pitti: so, the next best choice after ADT_NORMAL_USER is USER or LOGNAME ?
[14:21] <pitti> vila: yes, the solution in the branch seems fine
[14:21] <vila> ack
[15:02] <elopio> vila: you might prefer the command line tool corey wrote.
[15:03] <elopio> https://github.com/cgoldberg/subunitdetails
[15:03] <vila> hmm
[15:04] <vila> I'm torn between my personal preferences and the greater good ;) Sounds like enhancing trv may benefit more people no ?
[15:06] <elopio> vila: yes. And trv should probably be a UI for that library.
[15:06] <elopio> vila: do you have a trace for that Mouse error?
[15:06] <elopio> I want to see where it decides it should create a Mouse instead of a Touch.
[15:06] <vila> elopio: yup, but in standup right now ;)
[15:07] <vila> elopio: ack, I'm re-running without needs-recommends to isolate
[15:40] <vila> elopio: so, one traceback is https://pastebin.canonical.com/130219/ but I've seen the message for tests that succeeded O_o
[15:41] <vila> elopio: I've push my latest change, if you use revision 978 you should be able to reproduce on a phone
[15:41] <vila> elopio: reverting needs-recommends fixes the issue
[15:42] <vila> pitti: ^ needs-recommends is too greedy, not fully diagnosed yet but it seems to install too much which probably confuse autopilot
[15:49] <pitti> vila: hm, that might be a problem in itself, but I guess you instaed just explicitly add the deps you need?
[15:50] <vila> pitti: yup, it's only python3-evdev at that point (you may have missed my previous question, let me re-paste)
 pitti: about needs-recommends, I wondered if python3-evdev should move to Depends in autopilot-touch ?
[15:50] <pitti> vila: for -touch, I think yes
[15:51] <pitti> vila: recommends on such meta-packages are a bit pointless
[15:51] <vila> i.e. I'm unclear about what the package does but ... right will file a MP explaining my issue and see what the reviewers say ;)
[15:51] <vila> ha
[15:52] <vila> I'm also unclear about whether this meta-package is mentioned somewhere to get installed...
[15:52] <vila> pitti: why is this pointless ? (That may wait for next week if you don't have time to reply now ;)
[15:53] <pitti> vila: well, metapackages sohld install a group of packages that you need for this case, and make up its mind if it wants a recommended one or not
[15:53] <pitti> vila: but yeah, I suppose it's perfect bikeshedding material :)
[15:53] <pitti> vila: I think the more interesting issue is why ap3 breaks when you install all recommends
[15:54] <vila> pitti: yup, that's the one elopio wants to look at more closely
[15:54] <vila> elopio: correct ?
[15:55] <elopio> vila: yes. Now I'm wondering why on test end it's moving the mouse.
[15:55] <vila> it's in the way ?
[15:56] <vila> ;-D
[15:56] <elopio> I suppose this comes from earlier, it somehow instantiates the Mouse on setup and tries to clean it up.
[15:56] <elopio> I'll get a phone and debug.
[15:59] <vila> elopio: https://bugs.launchpad.net/autopilot/+bug/1447688
[16:01] <elopio> vila: I'm not yet sure how to define a dependency on autopilot-touch
[16:01] <elopio> we need to install autopilot-touch only if we are on the phone, bug debs can't depend on that, only on architecture, right?
[16:02] <elopio> how would we know if we have a touchscreen or not?
[16:04] <vila> yeah, it's unclear to me too, we may want to install it explicitly when we're not using ubuntu-touch-session (still hackish)
[16:05] <vila> It's a different axis, we use ubuntu-touch-session to setup a screen, not an input device
[16:06] <vila> I don't think it matters much for now but it's something to keep in mind
[17:24] <elopio> ubuntu-qa: meeting with balloons in 30 minutes to talk about docs for the test helpers.
[17:42] <jfunk> elopio: thx for highlighting that, I think everyone who participates in developing those should attend, likely everyone in projects-team no?
[17:43] <ki7mt> where is the meeting taking place ?
[17:43] <elopio> jfunk: also ops should be interested, as they can quickly write a high level test to reproduce an issue.
[17:44] <elopio> ki7mt: google hangouts.
[17:44] <elopio> ki7mt: I saw your email about wanting to write tests. Welcome, and please ping if you have questions.
[17:45] <ki7mt> elopio, thanks, I'm sure there will be many questions, but have a fare amount of reading to do first :-)
[17:48] <jfunk> ops-team ^
[17:49] <rvr> ops-team is really really busy with silos
[17:53] <davmor2> not a good week for meetings could be why jibel cancelled them all
[17:59] <nuclearbob> balloons: do you have a hangout link?
[18:01] <elopio> nuclearbob: https://plus.google.com/hangouts/_/canonical.com/leo-nicholas
[18:04] <balloons> isn't it now?
[18:04] <elopio> balloons: we are waiting for you.
[18:04] <balloons> yes, google hates m
[18:11] <elopio> now internet hates me, the hangout seems fine but I'm talking to myself
[18:11] <balloons> no worries, we'll wait
[18:19] <ki7mt> elopio, that's ok m8, I talk to myself all the time :-)
[18:34] <balloons> ki7mt, nice to see you here as well. You're going to enjoy test writing :-)
[19:23] <ki7mt> balloons, Hi, yes, I think so, will be a steep learning curve, but I like those sort of challenges.