[issue6460] test failure in test_xmlrpc on Gentoo in trunk

Changes by R. David Murray : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue6460] test failure in test_xmlrpc on Gentoo in trunk

Ned Deily added the comment: I have not seen any recent failures either. -- ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue6460] test failure in test_xmlrpc on Gentoo in trunk

Sandro Tosi added the comment: Hello, can we consider this bug as fixed? test has been fixed, buildbots don't show this problem anymore and a run on my system with 300 instances of the test_xmlrpc running in parallel generated only OK as result. Regards, Sandro -- nosy: +sandro.tosi

[issue6460] test failure in test_xmlrpc on Gentoo in trunk

Kristján Valur Jónsson added the comment: merged testsuite fix to py3k in revision 73961 -- ___ Python tracker ___ ___ Python-bugs-lis

[issue6460] test failure in test_xmlrpc on Gentoo in trunk

Kristján Valur Jónsson added the comment: No, this should take care of it. In order for the client side request to succeed, the server must have cycled through the previous request and updated its statistic. It is only the statistic for the final request tha t may be missed. And yes, I was

[issue6460] test failure in test_xmlrpc on Gentoo in trunk

R. David Murray added the comment: By the way, although my system doesn't show it, the Gentoo 3.x buildbot shows the error. I'm sure you were going to forward port the patch anyway :) -- ___ Python tracker ___

[issue6460] test failure in test_xmlrpc on Gentoo in trunk

R. David Murray added the comment: OK, the test passes on my box now. But from the way the test is phrased it sounds like there is still a small risk that the test will fail in unusual timing circumstances? -- ___ Python tracker

[issue6460] test failure in test_xmlrpc on Gentoo in trunk

Kristján Valur Jónsson added the comment: This is probably a race condition, where the server thread hasn't updated the stats yet when the client is testing them. I'm so used to work with non-preemtive scheduling in stackless python that I sometimes forget how threads work :) I submitted rev

[issue6460] test failure in test_xmlrpc on Gentoo in trunk

Ned Deily added the comment: FWIW, I've just seen a couple of intermittent 'test_two' failures with a current py3k on OS X but, in each case, the test passed when auto rerun in verbose mode. test test_xmlrpc failed -- Traceback (most recent call last): File "/Library/Frameworks/Python.fram

[issue6460] test failure in test_xmlrpc on Gentoo in trunk

New submission from R. David Murray : Another apparent fallout from r73638 (issue 6267). On my gentoo system I am currently seeing a consistent failure in test_xmlrpc of 'test_two' in KeepaliveServerTestCase (as is the Gentoo buildbot). I made the assert the new GreaterEqual and stuck just a ta