[issue12958] test_socket failures on Mac OS X

2014-02-01 Thread Ned Deily
Ned Deily added the comment: FYI, the OS X platform bugs causing the three "send timeout" test failures were fixed in OS X 10.7 causing those test cases to have previously silently skipped "unexpected successes". See Issue20474 for more details. -- ___

[issue12958] test_socket failures on Mac OS X

2013-04-23 Thread Ronald Oussoren
Ronald Oussoren added the comment: FWIW I've filed a bug report about the behavior of sendmsg with Apple, the RADAR number is 13716133. -- ___ Python tracker ___ ___

[issue12958] test_socket failures on Mac OS X

2013-04-23 Thread Nick Coghlan
Nick Coghlan added the comment: It's entirely possible the hack in test_socket (where it catches unittest._ExpectedFailure to suppress the issues in the tearDown code after the test fails) were invalidated by the subtest changes. -- ___ Python track

[issue12958] test_socket failures on Mac OS X

2013-04-23 Thread Ronald Oussoren
Ronald Oussoren added the comment: Yes, only on 3.4: == ERROR: testFDPassSeparate (test.test_socket.RecvmsgSCMRightsStreamTest) -- Traceback (most recent call

[issue12958] test_socket failures on Mac OS X

2013-04-23 Thread R. David Murray
R. David Murray added the comment: Ronald: in 3.4 only? If so I wonder if the subtests patch had an unintended side effect...I'm pretty sure it touched the expected failure machinery somehow. -- nosy: +r.david.murray ___ Python tracker

[issue12958] test_socket failures on Mac OS X

2013-04-23 Thread Ronald Oussoren
Ronald Oussoren added the comment: Not sure what changed, but these tests are reported as failures when I run 'make test' and not as expected failures. -- nosy: +ronaldoussoren versions: +Python 3.4 ___ Python tracker

[issue12958] test_socket failures on Mac OS X

2012-04-30 Thread Roundup Robot
Roundup Robot added the comment: New changeset e64bec91ac91 by Richard Oudkerk in branch 'default': Issue #14669: Skip multiprocessing connection pickling test on MacOSX http://hg.python.org/cpython/rev/e64bec91ac91 -- ___ Python tracker

[issue12958] test_socket failures on Mac OS X

2011-09-19 Thread Roundup Robot
Roundup Robot added the comment: New changeset a4e4facad164 by Nick Coghlan in branch 'default': Close issue 12958 by flagging expected failures in test_socket on Mac OS X http://hg.python.org/cpython/rev/a4e4facad164 -- nosy: +python-dev resolution: -> fixed stage: -> committed/rejec

[issue12958] test_socket failures on Mac OS X

2011-09-18 Thread Nick Coghlan
Nick Coghlan added the comment: OK, I'll just deal with the problem directly in test_socket then. It looks like my latest attempt (suppressing unittest._ExpectedFailure in test_socket.ThreadableTest.clientRun) did the trick, so I'll push the updated tests some time this evening: http://www.py

[issue12958] test_socket failures on Mac OS X

2011-09-18 Thread Michael Foord
Michael Foord added the comment: See issue 10548. There is some resistance to expectedFailure masking errors in setUp/tearDown as these aren't the place where you would normally expect the expected failure... -- ___ Python tracker

[issue12958] test_socket failures on Mac OS X

2011-09-18 Thread Nick Coghlan
Nick Coghlan added the comment: OK, I've now looked into *why* the socket tests are throwing errors in tearDown, and it has to do with the way the threaded client/server tests in test_socket are set up. Specifically, ThreadableTest uses tearDown to reraise any exception raised in the client

[issue12958] test_socket failures on Mac OS X

2011-09-12 Thread David Watson
Changes by David Watson : -- nosy: +baikie ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue12958] test_socket failures on Mac OS X

2011-09-11 Thread Brett Cannon
Changes by Brett Cannon : -- nosy: +brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue12958] test_socket failures on Mac OS X

2011-09-11 Thread Nick Coghlan
Nick Coghlan added the comment: Ah, I believe I see why the expected failure isn't working properly - the failing testFDPass* tests are causing the subsequent tear down code to also fail. -- ___ Python tracker _

[issue12958] test_socket failures on Mac OS X

2011-09-11 Thread Nick Coghlan
Nick Coghlan added the comment: First attempt didn't quite work - the FD passing tests somehow seem to be reporting both 'ERROR' *and* 'expected failure', which is causing the test overall to remain red. http://www.python.org/dev/buildbot/all/builders/AMD64%20Snow%20Leopard%202%20custom/build

[issue12958] test_socket failures on Mac OS X

2011-09-11 Thread Ned Deily
Changes by Ned Deily : -- nosy: +ned.deily ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue12958] test_socket failures on Mac OS X

2011-09-10 Thread Nick Coghlan
New submission from Nick Coghlan : Several of the new socket tests introduced in #6560 are failing on the Mac OS X buildbots. These appear to be due to platform problems rather than anything in the test suite or the new sendmsg/recvmsg code, but it would be good if a developer on Mac OS X coul