curl/tests/data/DISABLED

# This file can be used to specify test cases that should not run when all
# test cases are run by runtests.pl. Just add the plain test case numbers, one
# per line.
# Lines starting with '#' letters are treated as comments.
594
1209
1211
1316
1512
836
882
938
# test 1801 causes problems on Mac OS X and github
# https://github.com/curl/curl/issues/380
1801
# test 1510 causes problems on the CI on github
# example: https://travis-ci.org/curl/curl/builds/81633600
1510
# Pipelining test that is causing false positives a little too often
1903
# fnmatch differences are just too common to make testing them sensible
1307
# Pipelining is deprecated
530
536
584
1900
1901
1902
2033
# Uses SRP to "a server not supporting it" but modern stunnel versions
# will silently accept it and remain happy
323
Added a generic way to disable test cases when "all" is run, and added the FTP 3rd party transfers to that file for now until I have them sorted out. 2006-09-13 06:16:36 -04:00			`# This file can be used to specify test cases that should not run when all`
			`# test cases are run by runtests.pl. Just add the plain test case numbers, one`
			`# per line.`
added CVS id and clarified the comment lines 2006-09-13 06:18:01 -04:00			`# Lines starting with '#' letters are treated as comments.`
Active mode FTP test cases with server not establishing data connection 591 -> FTP multi PORT and 425 on upload 592 -> FTP multi PORT and 421 on upload 593 -> FTP multi PORT upload, no data conn and no transient neg. reply 594 -> FTP multi PORT upload, no data conn and no positive prelim. reply 1206 -> FTP PORT and 425 on download 1207 -> FTP PORT and 421 on download 1208 -> FTP PORT download, no data conn and no transient negative reply 1209 -> FTP PORT download, no data conn and no positive preliminary reply 2011-11-11 13:46:44 -05:00			`594`
FTP: perform active connections non-blocking 1- Two new error codes are introduced. CURLE_FTP_ACCEPT_FAILED to be set whenever ACCEPTing fails because of FTP server connected. CURLE_FTP_ACCEPT_TIMEOUT to be set whenever ACCEPTing timeouts. Neither of these errors are considered fatal and control connection remains OK because it could just be a firewall blocking server to connect to the client. 2- One new setopt option was introduced. CURLOPT_ACCEPTTIMEOUT_MS It sets the maximum amount of time FTP client is going to wait for a server to connect. Internal default accept timeout is 60 seconds. 2011-12-19 08:35:20 -05:00			`1209`
test 1211: FTP test to repeat bug #3429299 "Active FTP hangs if server does not open data connection" The server first sends a 150 and then when libcurl waits for the data transfer, the server sends a 425. 2011-11-25 17:15:58 -05:00			`1211`
tests: Disabled broken test 1316 See http://curl.haxx.se/mail/lib-2014-02/0004.html for a discussion on the problem. 2014-02-11 15:27:32 -05:00			`1316`
DISABLED: shut of test 1512 for now It shows intermittent failures and I haven't been able to track them down yet. Disable this test for now. 2013-08-10 17:55:10 -04:00			`1512`
DISABLED: 836, 882 and 938 hang 2014-03-30 17:36:57 -04:00			`836`
			`882`
			`938`
tests: disable 1801 until fixed It is unreliable and causes CI problems on github Closes #380 2015-09-20 07:12:44 -04:00			`# test 1801 causes problems on Mac OS X and github`
URLs: follow GitHub project rename (also Travis CI) Closes #632 2016-02-03 12:34:16 -05:00			`# https://github.com/curl/curl/issues/380`
tests: disable 1801 until fixed It is unreliable and causes CI problems on github Closes #380 2015-09-20 07:12:44 -04:00			`1801`
spelling fixes Closes #1356 2017-03-26 11:02:22 -04:00			`# test 1510 causes problems on the CI on github`
URLs: follow GitHub project rename (also Travis CI) Closes #632 2016-02-03 12:34:16 -05:00			`# example: https://travis-ci.org/curl/curl/builds/81633600`
tests: disable 1510 due to CI-problems on github 2015-09-23 07:53:38 -04:00			`1510`
tests: disabled 1903 now Test 1903 is doing HTTP pipelining, and that is a timing and ordering sensitive operation and this fails far too often on the Travis CI leading to people more or less ignoring test failures there. Not good. The end of pipelning is probably coming sooner rather than later anyway... 2017-03-09 17:55:30 -05:00			`# Pipelining test that is causing false positives a little too often`
			`1903`
test1307: disabled Turns out that since we're using the native fnmatch function now when available, and they simply disagree on a huge number of test patterns that make it hard to test this function like this... Fixes #2825 2018-08-01 18:57:01 -04:00			`# fnmatch differences are just too common to make testing them sensible`
			`1307`
pipelining: deprecated Transparently. The related curl_multi_setopt() options all still returns OK when pipelining is selected. To re-enable the support, the single line change in lib/multi.c needs to be reverted. See docs/DEPRECATE.md Closes #2705 2018-09-05 05:33:51 -04:00			`# Pipelining is deprecated`
			`530`
			`536`
			`584`
			`1900`
			`1901`
			`1902`
			`2033`
DISABLED: disable test 323 The test uses SRP to "a server not supporting it" but modern stunnel versions will silently accept it and remain happy. The test is therefore faulty. I haven't figured out how to make stunnel explicitly reject SRP-using connects. Reported-by: Marc Hörsken Fixes #5105 Closes #5113 2020-03-16 09:53:14 -04:00			`# Uses SRP to "a server not supporting it" but modern stunnel versions`
			`# will silently accept it and remain happy`
			`323`