[issue31026] test_dbm fails when run directly

2017-09-08 Thread Brian Moyles
Brian Moyles added the comment: I ran into the same problem when running the test suite against a fresh Python 3.6.2 build on Ubuntu 16.04. It specifically appears to be a problem with ndbm and retrieving an empty byte string value: Python 3.6.2 (default, Sep 8 2017, 18:31:28) [GCC 5.4.0

[issue31026] test_dbm fails when run directly

2017-09-08 Thread Brian Moyles
Brian Moyles added the comment: Actually, I was able to make things happy by removing libdb5.3-dev and solely relying on libgdbm3-dev (which suggests that Debian upstream may want to pare back their build requirements rather than disable the dbm test as they appear to do now

[issue31436] test_socket.SendfileUsingSendfileTest.testWithTimeoutTriggeredSend fails due to sendfile completing before timeout

2017-09-12 Thread Brian Moyles
New submission from Brian Moyles: In building Python 3.6.2 on Ubuntu 16.04, test_socket repeatedly fails at == FAIL: testWithTimeoutTriggeredSend (test.test_socket.SendfileUsingSendfileTest

[issue31437] test_socket.SendfileUsingSendfileTest.testWithTimeoutTriggeredSend fails due to sendfile completing before timeout

2017-09-12 Thread Brian Moyles
New submission from Brian Moyles: In building Python 3.6.2 on Ubuntu 16.04, test_socket repeatedly fails at == FAIL: testWithTimeoutTriggeredSend (test.test_socket.SendfileUsingSendfileTest

[issue31437] test_socket.SendfileUsingSendfileTest.testWithTimeoutTriggeredSend fails due to sendfile completing before timeout

2017-09-12 Thread Brian Moyles
Brian Moyles added the comment: accidental double-submit, duplicates Issue31436 -- resolution: -> duplicate stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or