moparisthebest
/
curl
mirror of https://github.com/moparisthebest/curl
1
0
Fork 0
Code Issues Releases Wiki Activity
15,257 Commits 10 Branches 144 Tags 113 MiB
Commit Graph

12 Commits

Author SHA1 Message Date
Yang Tse 629d2e3450 multi tests: OOM handling fixes 
Additionally, improved error checking and logging.
 2011-10-21 16:52:14 +02:00
Yang Tse c8ba8740b9 test suite: libtest header inclusion cleanup 
Added missing memoryTracking to test cases 560 and 583. If this triggers
leak detection on these, it only means that previously it was going unnoticed.
 2011-09-06 17:47:54 +02:00
Yang Tse 78bbd0eecf fix compiler warning 2011-07-26 19:42:16 +02:00
Daniel Stenberg fb48e2050b libtests: stop checking for CURLM_CALL_MULTI_PERFORM 
CURLM_CALL_MULTI_PERFORM stopped being a valid return code from
curl_multi_perform back in 7.20.0. All the libcurl tests are ajusted to
this and no longer check for this return code. Makes them simpler.
 2011-06-27 16:01:41 +02:00
Yang Tse 5d39dea3b3 compiler warning: fix 
Fix compiler warning: variable was set but never used

Fix compiler warning: clobber ignored
 2011-05-26 12:40:04 +02:00
Daniel Stenberg 1aeb635cdd sources: update source headers 
All C and H files now (should) feature the proper project curl source
code header, which includes basic info, a copyright statement and some
basic disclaimers.
 2011-03-10 12:04:33 +01:00
Dan Fandrich 8c6793d79a Call curl_global_cleanup() in test 560 to avoid a memory leak 2010-03-30 12:52:44 -07:00
Daniel Stenberg 2309b4e330 remove the CVSish $Id$ lines 2010-03-24 11:02:54 +01:00
Yang Tse cad9c3f55f Addes OOM handling for curl_easy_setopt() calls in test 2010-02-05 18:07:19 +00:00
Yang Tse 640e49976f Fix compiler warning: loop without body 2009-10-10 12:29:32 +00:00
Dan Fandrich b2ed1e2607 Fixed an OOM problem with test 560 2008-11-12 22:26:06 +00:00
Daniel Stenberg d07d1a6ef8 Added test case 560: 
This test was added after the HTTPS-using-multi-interface with OpenSSL
regression of 7.19.1 to hopefully prevent this embarassing mistake from
appearing again... Unfortunately the bug wasn't triggered by this test, which
presumably is because the connect to a local server is too fast/different
compared to the real/distant servers we saw the bug happen with.
 2008-11-11 21:59:25 +00:00