[07:08] <ara> morning all!
[07:34] <fagan> moening
[07:49] <fagan> morning not moening lol
[07:51] <sbeattie> moaning?
[07:52] <fagan> :)
[07:54] <ara> morning fagan
[10:18] <davmor2> Morning all
[10:18] <ara> morning davmor2
[10:18] <ara> davmor2, how is your back? feeling any better?
[10:18] <davmor2> ara: Yeah thanks finally feeling human again
[10:19] <ara> davmor2, nice to hear :)
[13:25] <cr3> fader_: morning dude
[13:26] <fader_> cr3: Morning.  You're in early today!
[13:29] <cr3> fader_: yeah, got bored of sleeping
[13:29] <fader_> cr3: I've never had that happen to me.
[13:32] <cr3> soren: hey dude, I'll start working on that qa-regression-testing integration. I should have an update for you shortly
[13:33] <cr3> soren: I already started during some sessions at uds, so the integration should almost be done
[13:38] <soren> cr3: Coolness.
[13:38] <soren> cr3: How do you run these things?
[13:39] <soren> cr3: You do a fresh install onto some spare hardware, branch the stuff and run some magic command?
[13:39] <soren> or something more clever than that?
[13:41] <cr3> soren: if you mean all those things are automated, yes
[13:41] <soren> cr3: I probably do, yes :)
[13:45] <fagan> anything anyone want me to test in particular?
[13:45] <fagan> (checkbox scripts too)
[13:46] <fagan> ara: anything I should be testing in lucid at the moment?
[13:48] <cr3> soren and fagan: I'm almost done with integrating the qa-regression-testing suite, the challenge will then be to make sure each desired test runs as expected. perhaps you guys can work together once I push my branch
[13:49] <cr3> so many scripts require sudo privileges and yet should not be run as root, that this will present a problem
[13:50] <cr3> crap, some scripts require running as root and others not
[13:51] <cr3> soren: we'll have to extend the scripts under the qa-regression-testing suite to formalize how the scripts should be run
[13:52] <ara> fagan, are you subscribe to lucid uploads mailing list?
[13:52] <fader_> Chuck Norris^W^Wcheckbox is so hard-core it runs with UID -(sizeof(int))
[13:52] <soren> cr3: They want to run as a user who can sudo? Why can't they just run as root?
[13:53]  * fader_ needs more coffee -- that should have been INT_MIN, not sizeof().
[13:54] <cr3> soren: not sure the exact reason, but I've been told by leann and confirmed by sbeattie that some tests must be initiated as a normal user
[13:55] <cr3> soren: so, I've pushed an initial integration to lp:~cr3/checkbox/qrt, look at suites/qa_regression.txt and scripts/qa_regression_suite
[13:56] <cr3> soren: you will mostly be interested in the latter, try running it and it will output test descriptions on how checkobx should run each test
[13:56] <cr3> soren: if you are tight on bandwidth, you should know that it'll branch the qa-regression-testing suite to /tmp/checkbox.qa.regression
[13:57] <cr3> soren: if you already have it branched, you can either create a symlink or pass the -d or --directory option pointing to your copy of the branch
[13:58] <cr3> soren: the next step is making sure that checkbox will invoke the scripts properly, as root or not as root, with proper dependencies or not, etc.
[13:59] <cr3> soren: to do so, we should need to look at the output generated by scripts/qa_regression_suite [OPTION] [SCRIPTS] and make sure we can run it ourselves using the command value in the output
[13:59] <cr3> for example, if I run: ./scripts/qa_regression_suite test-apache2.py
[13:59] <cr3> I get the command: cd /tmp/checkbox.qa.regression/scripts; SUDO_PASSWORD=insecure python test-apache2.py
[13:59] <fagan> ara: hell no my mailbox is hammered enough as it is :)
[14:00] <cr3> if this works, then we can assume that test-apache2.py is integrated. then repeat for each test
[14:00] <cr3> note that SUDO_PASSWORD doesn't work, we need to discuss a better solution for this sudo problem
[14:01] <cr3> soren: make sense so far?
[14:02] <fagan> cr3: im back what do you need
[14:03] <ara> fagan, well, going to the archives (no need to subscribe) you can see what new things have landed in Lucid, and it is a good way of knowing what to test
[14:03] <cr3> fagan: I'm preparing a ppa for you, one moment :)
[14:04] <fagan> ara: good idea
[14:04]  * fagan noticed that the software center got some synaptic like funtions last night. 
[14:05] <mvo> it did, feedback welcome
[14:06] <soren> cr3: I think so.
[14:06] <fagan> mvo: its a little slow to search
[14:06] <fagan> It works though
[14:06] <mvo> fagan: yeah, I noticed that too, especially for short search terms
[14:08] <fagan> mvo: maybe parse down the list on first letter then the rest of the letters typed will be a lot quicker
[14:08] <ara> fagan, that list contain the changelogs, so it is a very easy way to spot new features and bugs fixed
[14:09] <fagan> So if I typed "c" it would cut out everything but things beginning with c. Its how I did the search in a college project it made searching a lot faster
[14:09] <fagan> ara: got it
[14:09]  * fagan bookmarks the archives for the lucid uploads 
[14:11] <davmor2> morning fader_ cr3
[14:11] <fader_> davmor2: Howdy dude
[14:12] <davmor2> fader_: no demotion just on my real machine for a change :)
[14:12] <fader_> davmor2: Hehe, out of bed and hobbling around then?
[14:12] <davmor2> something like that ar
[14:13] <soren> cr3: Couldn't we just configure this user to have NOPASSWD sudo access?
[14:13] <soren> cr3: These are expected to be throw-away installs anyways, aren't they?
[14:15] <cr3> soren: sounds like a plan, I can take care of putting that logic in the right place
[14:15] <soren> cr3: neat.
[14:15] <cr3> soren: so, that solves scripts requiring to initially run as the normal user and then calling sudo
[14:15] <soren> cr3: The initial checkout scripts/qa_regression_suite does was how big? 500 MB?
[14:15] <cr3> soren: I noticed some scripts initially need to be run as root, so we need to find a way to formalize that information so that it can be determined programmatically
[14:15] <cr3> soren: yes
[14:16] <cr3> fagan: my ppa is building: https://edge.launchpad.net/~cr3/+archive/ppa/+packages
[14:17] <fagan> cr3: cool
[14:18]  * fagan grabs the ppa info 
[14:18]  * fagan prays to the gods for a one click ppa install in the future
[14:18] <mvo> fagan: thanks, I check out what can be done to make it faster
[14:19] <mvo> fagan: "sudo add-apt-repository ppa:the-name"
[14:19] <cr3> fagan: note that the ppa is still building checkbox, make sure you get 0.9-ppa1
[14:19] <fagan> mvo: cool ill keep on testing away and see if I can break it
[14:20] <fagan> oh I didnt know that awesome mvo thanks
[14:20] <mvo> cheers :)
[14:22] <moustafa> Bonjour cr3, fader_, je voudrais un croissant
[14:22] <cr3> fader_: that is true, he would like a croissant
[14:23]  * fagan even understood that
[14:23] <moustafa> fader_: I'm very popular
[14:23] <soren> cr3: Ok, let's pretend that I've forgotten everything about checkbox. Hypothetically, of course.
[14:23] <cr3> fader_: by the way, if you run the QA regression suite in checkbox, note that it might be destructive. do you have a virtual machine or a machine on which you can reinstall everything?
[14:23] <soren> cr3: ...and let's pretend I want to just run all of those qrt test things. What's the command to run?
[14:24] <soren> cr3: I can usually work my way down the layers from something like that, I just need a starting point.
[14:24] <fader_> moustafa: Splish-splash!
[14:24] <cr3> soren: first, integration phase: we make sure that scripts/qa_regression_suite outputs commands that can work when running them from the command line
[14:24] <moustafa> fader_ Je ne comprends pas!
[14:25] <soren> cr3: Ok.
[14:25] <soren> cr3: Makes sense.
[14:25] <fader_> cr3: I can set up a VM if necessary... do you need me to test some tests?
[14:25] <soren> cr3: What I need to understand is how do I know that this step is succesful.
[14:25] <cr3> soren: the script in question can run all tests if not given any arguments, but I think we'll want to cherry pick those we want by passing them as arguments
[14:26] <fagan> Oh ive been meaning to ask are there any plans to make hwdb.ubuntu.com any better?
[14:26] <cr3> soren: second, suite definition: once we know what tests we want to run, we define how to call scripts/qa_regression_suite in suites/qa_regression.txt
[14:26] <cr3> soren: the suite should already be defined for running a couple scripts, so we can simply add to that list
[14:27] <cr3> soren: third, running the suite: if running from the branch, simply run ./bin/checkbox-gtk or ./bin/checkbox-cli and only select the suite of interest from the second prompted step
[14:27] <cr3> soren: fourth, profit!
[14:28] <cr3> the cool part is that most of the integration consists of making sure scripts work on the command line and output sane information, scripts/qa_regression_suite in this case and how to call each individual script within the qa-regression-testing suite in our particular case of interest
[14:29] <cr3> fagan: man, hwdb is so deprecated, I think we should make plans to get rid of it
[14:30] <fagan> I would like if we could have some way to make the test results available so people can know what works and what doesnt
[14:32] <soren> cr3: Err...
[14:32] <soren> cr3: I run ./bin/checkbox-cli
[14:32] <soren> cr3: ...
[14:32] <soren> cr3: and I get..
[14:33] <soren> A list of suites.. h is the qrt thing. Pressing h changes nothing. What gives?
[14:34] <cr3> soren: interesting, it's the only one that doesn't work, probably because it's external (meaning the actual suite resides on an external source such as launchpad), but that shouldn't affect being able to select or deselect it. I'll have a look
[14:37] <fagan> ok cr3 I have the ppa update for checkbox
[14:37] <cr3> fagan: do you have a throw away system on which you can run that particular version of checkbox?
[14:38] <fagan> Oh no but I can recover this one fine if needs be
[14:38] <fagan> cr3: are there any ones that break things?
[14:39]  * fagan is starting to feel like the nutty professor
[14:40] <soren> cr3: You do see the same behaviour, right?
[14:42] <cr3> soren: yep
[14:42] <cr3> fagan: nope, the others don't break anything, just QA regression tests. however, those are the ones of particular interest right now :)
[14:42] <davmor2> fagan: come on you're not as funny as eddie murphy ;)
[14:42] <cr3> soren: the graphical interface should work just fine though
[14:42] <fagan> oh cr3 could you look at this bug report its https://bugs.launchpad.net/checkbox/+bug/487143
[14:42] <ubot4> Launchpad bug 487143 in checkbox "More specific hardware questions shouldnt be asked" [Undecided,New]
[14:43] <fagan> davmor2: I am so :D
[14:44] <cr3> fagan: I'd be happy to make those questions more human friendly, might you have suggestions?
[14:44] <fagan> just do the tests I suggested in the backround
[14:44] <fagan> They arent really yes or no questions anyone can answer off the top of their head
[14:45] <cr3> fagan: agreed, but how would you propose to improve that situation and make it easier to answer by anyone?
[14:46] <fagan> hmmm thats the question
[14:48] <fagan> I dont think there is an easier way to ask how fast you hard drive writes
[14:49]  * fagan is of the opinion if his mother cant answer it then most other people cant answer it
[14:50] <davmor2> fagan: I think the big issue here is the amount of info provided rather than the question being right or wrong, the big problem is though that manufactures don't name there stuff in a similar fashion so you can't pull out key info from that provided.
[14:52] <fagan> davmor2: true but the users might not know the answer that the problem
[14:53] <fagan> the xrander cycle is fun :)
[14:54] <davmor2> fagan: there is always the option to skip if they are unsure
[14:55] <fagan> true but still in most cases I think checkbox should do it in the backround
[14:58] <davmor2> fagan: but checkbox can't magically tell what level of knowledge you have about your machine.  Hence the skip button ;)
[15:01] <fagan> davmor2: it would be great if it could :D
[15:01] <fader_> fagan: Out of curiosity, the checkbox window doesn't get 'lost' or moved around too badly at the end of the xrandr-cycle test, does it?
[15:02] <fagan> fader_: no the resolution gos funny but the window returns to the original position
[15:03] <fader_> fagan: "the resolution goes funny" -- that's only during the test though, right?  It returns to the proper resolution at the end?
[15:03] <fagan> yep
[15:17] <moustafa> fader_: I'd like to add that the xrandr test is troublesome on NVIDIA cards with the proprietary drivers.  I tried it on my home machine, and got stuck at the lowest available resolution.
[15:18] <fader_> moustafa: If that's something you can replicate every time I'd be very interested in troubleshooting that
[15:18] <moustafa> I'll try it again tonight, then ;)
[15:19] <fader_> It *shouldn't* happen :)  I grab the current resolution before changing anything and then set it back to that resolution at the end explicitly, so I'd be curious as to what is going on if it stays at a low resolution.
[15:22] <cr3> soren: checkbox-cli fixed and push to my qrt branch
[15:23] <cr3> soren: now working on NOPASSWD thing
[15:24] <soren> cr3: Awesomeness.
[15:43] <soren> cr3: I'm about to call it a day. I'll play more with this tomorrow morning.
[15:43] <soren> Bah, who am I kidding? I'll be back in  3-4 hours.
[15:44] <cr3> soren: I just pushed more changes
[15:44] <cr3> soren: the qa_regression_suite script now writes to the sudoers file properly
[15:45] <cr3> soren: there's one remaining problem though: in order for the script itself to run as root, it must be run by the dbus backend. unfortunately, the dbus backend doesn't know who called it, which I need to know in order to configure the sudoers file properly
[15:45] <cr3> so, that's what I'm working on now
[16:25] <davmor2> by the way fagan bug 487143 you should write an individual bug for each one not cluster them together like that.   1 might be fixable with a rewrite where as others might need recoding etc.
[16:25] <ubot4> Launchpad bug 487143 in checkbox "More specific hardware questions shouldnt be asked" [Undecided,New] https://launchpad.net/bugs/487143
[16:26] <fagan> davmor2: oh ok
[17:06] <cr3> sbeattie: when you come back, are you sure qa-regression-testing scripts depend on python-unit? they work just fine with just python2.(5|6) which comes with the unittest module
[17:07] <sbeattie> cr3: doh, that seems correct.
[17:13] <cr3> sbeattie: what seems correct? depending on python-unit?
[17:14]  * cr3 wonders since when unittest came with python
[17:27] <sbeattie> cr3: it seems correct that the dependency on python-unit is not needed at least for python 2.5 and 2.6.
[17:29] <sbeattie> that's probably not be true for dapper, though; it has python-2.4
[17:29] <sbeattie> s/probably/possibly/
[17:30] <cr3> sbeattie: if you could confirm that dependency and update the qa-regression-testing trunk accordingly, that'd be awesome
[17:31] <sbeattie> cr3: will do.
[17:31] <cr3> sbeattie: also, have you figured a way to formalize how to describe dependency on packages depending on ubuntu release? it seems that the QRT-Alternates requires human intervention and prior knowledge in order to be enforced
[22:07] <moustafa> cr3, fader_: I'm off for the night, see you tomorrow!
[22:08] <fader_> moustafa: g'night!