swift

History

Peter Portante 9d0067a0f5 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

2014-04-04 15:26:32 -04:00

__init__.py

re-use headers_to_container_info on container GET

2012-11-01 18:46:47 -07:00

test_account.py

Rework use of constraints to ease testing

2014-04-02 23:48:01 -04:00

test_base.py

Generic means for persisting system metadata.

2014-01-06 22:29:37 +00:00

test_container.py

Generic means for persisting system metadata.