Comment 1 for bug 1302781

Reviewed: https://review.openstack.org/85457
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=9d0067a0f546ce8a0fddb257655f2944c05e35e6
Submitter: Jenkins
Branch: master

commit 9d0067a0f546ce8a0fddb257655f2944c05e35e6
Author: Peter Portante <email address hidden>
Date: Fri Apr 4 15:26:32 2014 -0400

    Attempt to ensure connect always timesout

    It seems that the test_connect_put_timeout() test does not always fail
    when it is expected. Sometimes, not very often, the attempt to connect
    succeeds, resulting in a failed test.

    This might be because the fake-connection infrastructure uses a
    sleep(0.1) and the test uses a connect timeout of 0.1. There might be a
    case where the two values result in the exact time where the entries
    happen to be added in the wrong order such that the sleep() completes
    first before the connect timeout fires, where the connect completes
    successfully.

    Closes bug 1302781

    Change-Id: Ie23e40cf294170eccdf0713e313f9a31a92f9071