[00:15] <kotux> Cool, thanks Noskcaj
[00:25] <sak> How did the hackfest go today? I was unable to attend.
[00:25]  * kotux wants to know too.
[00:33] <balloons> hey sak and kotux
[00:34] <balloons> not too bad.. you can see what happened here: http://pad.ubuntu.com/CFXkuLR7Lb
[00:34] <sak> hey balloons
[00:34] <sak> Thanks
[00:34] <balloons> in addition feel free to pick any of the unclaimed tests and make a branch for it and convert it :-)
[00:35] <balloons> I'm relaxing my brain after today.. we cleaned up the repo, and we have a production branch that's stable now
[00:35] <sak> In addition to contributing our own testcases
[00:35] <sak> ?
[00:36] <balloons> lol.. that's me just being tired
[00:36] <balloons> just wanted you to know about the pad
[00:40] <sak> I am looking over the pad now.
[00:40] <sak> I thought nautilus was rewritten to a new file manager
[01:15] <sak> Just assigned myself to remmina and vino
[03:38] <pitti> Good morning
[04:08] <sak> morning and good night LOL
[06:44] <jibel> good morning
[06:46] <pitti> bonjour Monsieur Lallement
[06:50] <jibel> Guten Morgen Herr Pitt :)
[07:44] <gema> asac: it means we are working on it, but yeah, we are starting to run something after installing :D
[07:46] <Noskcaj> gema, wrong channel?
[07:47] <gema> Noskcaj: nope, asac said something to me yesterday night, I was answering now :D
[07:47] <gema> Noskcaj: he should be able to figure it out!
[07:47] <Noskcaj> he's also not online
[07:47] <gema> Noskcaj: he is in the channel
[07:48] <Noskcaj> true
[09:28] <Noskcaj> Someone find howard, i'm slightly concerned, but mostly annoyed because he has testdrive stuff to do
[10:00] <asac> gema: thx :)
=== mmrazik is now known as mmrazik|lunch
=== mzanetti is now known as mzanetti|lunch
=== mzanetti|lunch is now known as mzanetti
=== mmrazik|lunch is now known as mmrazik
=== _salem is now known as salem_
=== mmrazik is now known as mmrazik|afk
=== Ursinha_ is now known as Ursinha
=== salem_ is now known as _salem
=== _salem is now known as salem_
=== salem_ is now known as _salem
=== balloons changed the topic of #ubuntu-quality to: Welcome to Ubuntu Quality | http://wiki.ubuntu.com/QATeam | Next Hackfest is June 4th! Hackfest from May 23rd: https://wiki.ubuntu.com/QATeam/Hackfest/20130523 http://pad.ubuntu.com/CFXkuLR7Lb
=== _salem is now known as salem_
[17:42] <fginther> pitti, Hi, I'm working on an autopilot tutorial for gtk apps. Do you happen know of any good test examples?
=== francisco is now known as Guest60367
[17:59] <balloons> fginther, I'm not pitti but I'm happy to hear your writing a tutorial. If I can help in anyway, let me know ;-)
[18:04] <fginther> balloons, thanks. I'm looking for tests that use the autopilot API most efficiently. I was planning on looking at the tests you guys worked on yesterday, but thought that Pitti had a lot of experience here as well
[18:04] <fginther> I don't want to document bad practices in a tutorial :-)
[18:04] <balloons> fginther, heh, much of the stuff we wrote highlights trying to hack around issues with autopilot-gtk ;-(
[18:04] <fginther> which is what would happen if I used my own tests as an example
[18:05] <fginther> yeah, autopilot-gtk needs some love
[18:12] <phillw> balloons: hiyas, sorry I was not about much yesterday, one of the F/OSS virtual machine's was hit with a DDoS. I spent some time trying to find out which, which was my tor relay ipV4; but we have no idea why. Maybe just what is called a 'drive by shooting'. It did however reduce the bandwidth available to all as to cause the znc server instance to fail. It appears fatally as TheLordOfTime of time has not been able to get it re-started.... My th
[18:16] <balloons> I saw the znc dc's :-)
[18:19] <phillw> balloons: the only thought that the tor people had was if that relay had an error in the config file that throttles the amount of connections it will take. The logs show that it had no increase in traffic, so it was a DDoS. As to if it was against the tor relay or some dim-wit setting up a random DDoS to check if it worked, or an equally dim-wit typing in the wrong ipV4 address to attack, we will never know :(
[18:21]  * TheLordOfTime pokes phillw
[18:21] <TheLordOfTime> "restarted" isn't the issue
[18:21] <TheLordOfTime> "fatal"?  not really
[18:21] <TheLordOfTime> "problem with secure connectivity, SSL, SSH, etc"? yes.
[18:21] <TheLordOfTime> afaik non-SSL works, but that's, you know, not really that "useful" per se.
[18:22] <TheLordOfTime> since lots of people like SSL
[18:22]  * TheLordOfTime goes back to digging in nginx to fix a security bug
[18:26]  * phillw would like to correct himself for the record " TheLordOfTime  has not been able to get SSL / SSH to run stably. "
[19:18] <asomething> anyone around that can help me make sense of an autopkgtest result?
[19:18] <asomething> https://jenkins.qa.ubuntu.com/view/Saucy/view/AutoPkgTest/job/saucy-adt-trac-bzr/ARCH=i386,label=adt/1/
[19:18] <asomething> The test "fails" but the actually test suite seems to pass AFAICT
[20:46] <asomething> hmm... it seems that maybe nosetests outputs even successful test results to stderr. I guess thats why the autopkgtests "fail"
[20:53] <asomething> I guess that's it... from 'man nosetests': "Log debug messages to this file (default: sys.stderr)"
[20:58] <balloons> asomething, heh :-)
=== salem_ is now known as _salem
[22:29] <jtaylor> why is pyzmq autopkgtest failing in saucy jenkins?
[22:29] <jtaylor> the summary says all test passed
[22:29] <jtaylor> log is fine too
[22:29] <jtaylor> https://jenkins.qa.ubuntu.com/view/Saucy/view/AutoPkgTest/job/saucy-adt-pyzmq/