[07:39] <jibel> pitti, thanks for fixing the small issues I reported in autopkgtest.
[07:40] <jibel> pitti, another one http://paste.ubuntu.com/11075181/
[07:41] <pitti> jibel: bonjour !
[07:42] <pitti> jibel: I just got a mail notification this morning (just one), that got fixed apparently?
[07:42] <jibel> pitti, apparently. I thought you talked to CI
[07:43] <pitti> jibel: no, I didn't yet; I just saw your "fw rule changed" in backscroll this morning
[07:43] <pitti> jibel: I can't reproduce/understand the "trailing space" yet, I set that to incomplete with a comment
[07:44] <jibel> pitti, I attached the a config file to reproduce with latest git rev
[07:44] <jibel> s/the a/a/
[07:44] <pitti> jibel: http://paste.ubuntu.com/11075181/ applied, thanks!
[07:45] <jibel> pitti, it happens if the space is after -d
[07:45] <pitti> jibel: aah, thanks
[07:45] <jibel> pitti, or after the name of the package
[07:47] <jibel> pitti, I'm almost done with 'dep8ification' of dkms tests. It was pretty straightforward.
[07:47] <pitti> jibel: oh, cool! what did you change now, compared to what we had in Austin?
[07:47] <pitti> jibel: err, London, but all thes ame
[07:47] <jibel> pitti, but I don't use autodep8. dkms-autopkgtest in dkms needs fixing first
[07:48] <pitti> jibel: I saw that it fails on trusty as we don't have the test script in dkms there yet
[07:48] <jibel> pitti, I've a setup command to install any kernel and enable the pockets/ppa I need, and I changed the test to install only the dkms module and collect all the artifacts I need
[07:49] <jibel> pitti, right, but it also fails if the source package build other binaries than only a dkms module
[07:49] <jibel> pitti, see blcr for example
[07:49] <jibel> in that case it install a binary package that doesn't depend on dkms and fails
[07:51] <jibel> so with this setup command and test, the test runs on any release.
[07:51] <jibel> I'll do more tests, deploy and we can remove previous version and old style VMs
[07:52] <pitti> \o/
[07:53] <pitti> jibel: blcr didn't run in wily yet
[07:53] <jibel> pitti, I tried in vivid
[07:54] <jibel> so I can compare with current tests
[07:54] <pitti> http://d-jenkins.ubuntu-ci:8080/job/vivid-adt-blcr ?
[07:54] <pitti> (404)
[07:54] <jibel> blcr-dkms
[07:55] <pitti> that's the binary name
[07:55] <pitti> well, I guess you ran it on the CLI, not through jenkins
[07:56] <jibel> pitti, ah sorry, I was talking about the current DKMS tests http://d-jenkins.ubuntu-ci:8080//job/dkms-vivid-release-generic-blcr_dkms/
[07:57] <jibel> pitti, I'm replacing these tests
[07:57] <jibel> pitti, once it's done, I'll propose to replace dkms-autopkgtest
[07:58] <jibel> pitti, how did you run blcr on the CLI? it fails for me with 'cannot cd to /var/lib/dkms'
[07:59] <pitti> jibel: I thought you did; with just autopkgtest/run-from-checkout bclr ...
[08:00] <pitti> jibel: I thought you meant that the autodep8'ified ones fail in CI
[08:00] <jibel> pitti, yeah it'll fail in CI with http://paste.ubuntu.com/11075465/
[08:01] <pitti> jibel: ok, that looks fixable
[08:01] <jibel> pitti, so I'm converting the DKMS tests for the kernel team first, then I'll propose the test script because autodep8 are just small a subset of the kernel team's tests
[08:02] <jibel> pitti, indeed it is not difficult to fix. It's because the test script install blcr-utils which doesn't depends on dkms
[08:02] <jibel> pitti, it shouldn't install non-dkms modules at all
[08:03] <pitti> jibel: so binaries which don't have DKMS bits should just get skipped
[08:03] <jibel> pitti, is ADT_ARTIFACTS removed on reboot?
[08:04] <jibel> pitti, right
[08:04] <pitti> jibel: no, it survives
[08:04] <pitti> jibel: /tmp/autopkgtest-reboot saves it and restores it after reboot
[08:46] <bip> Ehy ;-)
[13:50] <elopio_> good morning.
=== elopio_ is now known as elopio
[14:10] <elopio> sjcazzol: https://code.launchpad.net/ubuntu-sanity-tests
[14:11] <sjcazzol> elopio: thanks!
[14:11] <elopio> sjcazzol: let me quickly show you how I have my bzr branches in the filesystem. You can choose a different layout of course.
[14:12] <sjcazzol> elopio: ok
[14:12] <elopio> mkdir -p ~/workspace/canonical
[14:12] <elopio> cd ~/workspace/canonical
[14:12] <elopio> bzr init ubuntu-sanity-tests
[14:13] <elopio> cd ubuntu-sanity-tests
[14:13] <elopio> mkdir bugs
[14:13] <elopio> mkdir experimental
[14:13] <elopio> mkdir reviews
[14:13] <elopio> bzr branch lp:ubuntu-sanity-tests trunk
[14:13] <elopio> then cd trunk and take a look at the README.
[14:14] <sjcazzol> elopio: great, I'll try that
[14:20] <elopio> fgimenez: hey, the phonedations planning was cancelled.
[14:20] <fgimenez> hi elopio, ok thx, will it be rescheduled?
[14:21] <elopio> fgimenez: I know nothing. I will tell you if I find out something else.
[14:22] <fgimenez> elopio, ok
[14:24] <elopio> ubuntu-qa: have you met sjcazzol ?
[14:24] <davmor2> no
[14:25] <davmor2> hello sjcazzol
[14:27] <rhuddie> sjcazzol, hello!
[14:29] <fgimenez> hi sjcazzol! welcome to the team
[14:29] <jfunk> hey sjcazzol :) welcome to our team
[14:30] <sjcazzol> Thanks! I hope to make a good job as part of this team
[14:30] <brendand_> sjcazzol, we met before :)
[14:30] <sjcazzol> brendand_: yes! :)
[14:31] <vila> elopio: s/bzr init ubuntu-sanity-tests/bzr init-repo buntu-sanity-tests/
[14:31] <vila> sjcazzol: welcome !
[14:32] <elopio> vila: good to know. Can you explain the difference?
[14:33] <vila> elopio: the later setup a shared repository so all branches below share the common revisions which speeds up most operations (otherwise each branch gets its own branch so, for example, you download the whole history when creating a new branch)
[14:33] <elopio> :) thanks.
[14:51] <fgimenez> elopio, i've pushed a branch with the python-selenium code for the ppa https://code.launchpad.net/~fgimenez/+junk/python-selenium, as far as i know this wasn't versioned
[14:51] <fgimenez> elopio, i've taken the opportunity to tweak the debian directory, changing the source format to quilt so tht the patches are applied at build time, etc
[14:53] <fgimenez> elopio, i've also applied vila's comments for making a recipe, and now it seems to be building fine
[14:54] <fgimenez> elopio, this can be pushed to canonical-platform-qa if needed, and the ppa can be build from there, let me know what do you think
[15:07] <balloons> hey hey sjcazzol
[15:15] <elopio> fgimenez: I think it's awesome.
[15:16] <elopio> thank you. I'm wondering what else we need to send this to debian.
[15:16] <elopio> I think that we need a separate package with the binaries that we stripped out.
[15:16] <elopio> or maybe not as firefox has marionnette embedded, so now the binaries are not really needed.
[15:17] <fgimenez> elopio, thx :) right now it's using the pristine source code from 2.44, i've turned the modifications in setup.py into a quilt patch, perhaps this can be removed?
[15:18] <fgimenez> elopio, that modifications where about firefox .so files, are you refering to that?
[15:20] <elopio> fgimenez: yes, the problem with this package in debian is that you can't easily build those .so files.
[15:20] <fgimenez> elopio, http://bazaar.launchpad.net/~fgimenez/+junk/python-selenium/view/head:/debian/patches/remove_x_ignore_nofocus.patch
[15:21] <fgimenez> elopio, ok, this was previously modified in the setup.py file itself, iirc there was a debian bug?
[15:23] <elopio> fgimenez: there are some bugs, overlapping: https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=python-selenium;dist=unstable
[15:36] <sjcazzol> balloons: Hi, thanks
[16:02] <elopio> sjcazzol: almost done here. Are you ok meeting in 1 hour?
[16:02] <sjcazzol> yes, no problem
=== chihchun is now known as chihchun_afk
[16:35] <balloons> elopio, I'm going to undertake updating the qml testing template in the SDK again based on the changes I made for Rick's app with launching. Is there anything else you'd want to change in the default template?
[16:37] <elopio> balloons: I don't think so. Please add me as a reviewer, to make sure we are all writing following the same template.
[16:52] <vila> elopio: is there a project group for qa ?
[16:53] <elopio> vila: I don't understand your question.
[16:57] <vila> elopio: see https://launchpad.net/bzr , it's part of https://launchpad.net/bazaar (In Porject information, Part of:)
[16:57] <vila> elopio: I want to make uci-{config,tests,vms} part of ???
[16:58] <elopio> vila: yeah, we don't have that I think.
[16:58] <elopio> it would be good to get one.
[16:58] <vila> elopio: so that I can go to ??? and see active reviews (for example) for all projects that are part of ???
[16:58] <vila> elopio: ok
[17:23] <elfy> balloons: any idea when the wily old release schedule is going to make itself known?
[17:24] <elfy> it's being much too wily imo
[17:24] <wxl> oh, i see what he did there
[17:24] <elfy> hey wxl :)
[17:24] <wxl> hai :)
[17:29] <balloons> nice!
[17:29] <balloons> i'll need to update things
[17:32] <elopio> sjcazzol: that was a looong meeting, I'm sorry.
[17:32] <elopio> do you want to do a google hangout?
[17:33] <sjcazzol> ok
[17:36] <elopio> sjcazzol: https://plus.google.com/hangouts/_/canonical.com/qa
[17:36] <elopio> ubuntu-qa: welcome party for sjcazzol  ^
[18:07] <elopio> sjcazzol: I don't know what happened, my monitor just died.
[18:07] <sjcazzol> Ok, no problem
[18:07] <elopio> but anyway, I was talking too much. I will let you go and play with the emulator and stuff, and have lunch in the meantime.
[18:07] <elopio> sjcazzol: ping me, fgimenez or ubuntu-qa in case you need a hand.
[18:08] <sjcazzol> elopio: good, I have a lot to read and try
[18:08] <sjcazzol> elopio: thanks for the support
[18:09] <elopio> sjcazzol: thanks to you.
[20:44] <elopio> veebers: http://paste.ubuntu.com/11084721/
[20:44] <elopio> those are my quick notes.
[20:44] <elopio> first is the list of packages that get installed to their latest version, so if it worked before and it doesn't work now, it could be one of those packages fault.
[20:44] <veebers> elopio: awesome, cheers
[20:44] <elopio> I'm not yet sure it worked before.
[20:45] <veebers> elopio:  how did you get the event information?
[20:45] <elopio> the second part is the events that the input device gets when you touch the screen.
[20:45] <elopio> the third is what it gets when you do it through autopilot.
[20:45] <elopio> what I see is that with autopilot, it never receives x and y, so I got stuck trying to dig more about that.
[20:45] <elopio> veebers: http://python-evdev.readthedocs.org/en/latest/
[20:45] <elopio> it shows and example with a read loop.
[20:46] <veebers> ah cool, cheers
[20:46] <elopio> just change that for the autopilot finger path, and it will print the events.
[20:47] <elopio> I wanted to compare the events that krillin receives to see if it was something weird in there, and here I am.
[20:47] <elopio> so pending, try with older autopilot, which is a little hard because I also have to get older dependencies that are no longer on the archive.
[20:48] <elopio> and try on krillin to compare.
[20:48] <elopio> oh, and talk to sergio again to see if he has more ideas.
[20:49] <veebers> elopio: ack, good luck :-)
[23:12] <elopio> veebers: this might get us somewhere, http://paste.ubuntu.com/11086470/
[23:12] <elopio> the arale is indeed missing the x and y events.
[23:15] <elopio> it makes no sense, as from the autopilot side this is just writing to a file.
[23:25] <veebers> elopio: interesting, good find.
[23:29] <veebers> elopio: I'm not so sure how to proceed though. Perhaps autopilot is writing the x/y events incorrectly? But the other events are received so that might not hold up