[16:24] <flocculant> balloons: just a thought here - we've picked up autologin bugs - none of the install tests use autologin - so tracker would normally miss these. Should there be an 'install with autologin' test do you think?
[16:35] <balloons> flocculant, in theory we should have coverage for every combination. In practice, I wonder how many tests that would be, heh. I usually test using autologin at some point. It's an interesting discussion to have
[16:36] <balloons> Ideally, I'd like to find a way to make the tests themselves a bit easier to do; especially when you are talking about redoing the same test with only minor option changes
[16:36] <flocculant> well
[16:36] <balloons> in other words, I'm not quick to want another testcase we have to admin and run
[16:37] <flocculant> yea - I can understand that for sure
[16:37] <flocculant> also - do we want people to autologin :)
[16:37] <flocculant> could always make it optional
[16:40] <flocculant> personally it's not something I'd be too worried about, but given that it's come up - just as we B2 - thought I should at least mention it
[16:41] <flocculant> balloons: just so you're aware of what's gone on - wily - autologin fails (but waiting fix release) vivid with autologin working fails on upgrade to wily
[16:42]  * balloons should reboot and see if autologin is working
[16:47] <flocculant> balloons should let me know how that goes :p
[18:15] <sethj> erm, what is this o_O
[18:15] <sethj> WARNING **: Could not open X display
[18:15] <sethj> Maximum number of clients reachedgdk_mir_display_open
[19:55] <wxl> ugh how does this happen
[19:59] <wxl> um someone added a testcase for unencrypted home for lubuntu's alternates but it seems to be a copy of the encrypted one! wtf! https://bazaar.launchpad.net/~ubuntu-testcase/ubuntu-manual-tests/trunk/revision/313
[19:59] <wxl> i can't believe i would have let that through
[20:09] <knome> just remove the file and push a new revision if it's not on the tracker yet
[20:10] <flocculant> it is
[20:15] <flocculant> if anyone does that - there's a pending merge from me kicking around
[20:16] <flocculant> or I can mp that as well - got the branch here atm
[20:36] <gQuigs> alright.. nano segfaults for me now
[20:36] <gQuigs> and pidgin... but someone else has already reported the nano segfault as a bug
[20:37] <gQuigs> does nano work for anyone else?
[20:37] <gQuigs> and now it works.. /me runs away
[20:38] <ianorlin> gQuigs: were you trying to run like nano and then a file that did not exist
[20:51] <gQuigs> I was trying to open configure.ac in the libreoffice source code, not sure if that's what I actally did or not
[21:29] <flexiondotorg> balloons, I'd like to file some test results for "Upgrade Ubuntu Mate" but can't.
[21:29] <flexiondotorg> balloons, Can you tweak my access?
[21:29] <balloons> flexiondotorg, what are you hitting?
[21:30] <flexiondotorg> balloons, There are no test cases for "Upgrade Ubuntu Mate"
[21:30] <flexiondotorg> And I've found a bug and posted a bug with fix attached :-)
[21:34] <balloons> flexiondotorg, you have permissions now for the upgrade tests
[21:34] <balloons> I'll let you add them as desired
[21:34] <flexiondotorg> balloons, How do I added them?
[21:38] <balloons> flexiondotorg, I added the tests. You should be able to link testsuites to the upgrade products, just like the ubuntu mate product
[21:39] <balloons> did you not setup ubuntu mate originally?
[22:05] <flexiondotorg> balloons, No, I didn't setup Ubuntu MATE. elfy did it.
[22:05] <balloons> flexiondotorg, ahh. Go into the admin section and you should see how it works