aboutsummaryrefslogtreecommitdiff
path: root/tests/libtest/lib536.c
AgeCommit message (Collapse)Author
2008-09-20include "memdebug.h"Yang Tse
2008-05-22Made sure to pass longs in to curl_easy_setopt where necessary in theDan Fandrich
libtest code.
2007-10-02Renamed a couple of global variables to avoid shadowing warningsYang Tse
2007-05-02Check the return code from curl_multi_add_handle()Dan Fandrich
2007-03-10change max allowed time for this test to complete to 90 secondsYang Tse
2007-02-09Some tests were using functions curlx_tvnow and curlx_tvdiff which are notYang Tse
part of the official libcurl API http://curl.haxx.se/lxr/source/lib/README.curlx The documented way of using them would be to use timeval.c as a source code file. The above described method works very well when statically linking libcurl and apps, test programs, but has several drawbacks when you build a true shared libcurl (i.e. Name space clash at linkage stage as functions are defined more than once. Windows makefiles are not capable of handling this system of source-level sharing) So... Now testutil.h and testutil.c define and implement tutil_tvnow and tutil_tvdiff which replace curlx_tvnow and curlx_tvdiff for the libtest programs. Doing this we avoid the above described problems, and the code in the testsuite does not impose the need to keep those functions public in libcurl even when not part of the API.
2006-10-25Use curl_global_init() and curl_global_cleanup().Yang Tse
Improve cleanup in case of initialization failure.
2006-10-21Compiler warning fixYang Tse
2006-10-20Oops! Actually set the limit to 30 seconds.Yang Tse
2006-10-20Decrease the posibility of aborting a test which actually is notYang Tse
stale by replacing loop counters with timeouts. In this way the main loop of the test will be allowed to run up to 30 seconds on any platform before aborting it.
2006-10-19Replace tabs with spaces and Compiler warning fix.Yang Tse
2006-10-19Abort test if it seems that it would have run forever. This is just to preventYang Tse
test hanging and actually is an indication that there's a condition that is not being properly handled at some point in the library. Loop counter limits might need to be further increased on false positives.
2006-10-10Compiler warning fixYang Tse
2006-10-09Added test case 536 in an attempt to add Bogdan Nicula's problematic caseDaniel Stenberg
with multi interface and pipelining. This test just works and did not repeat the problem his test code showed, but could still serve as a useful test.