mirror of
https://github.com/curl/curl.git
synced 2024-12-15 06:40:09 +08:00
e70c22b622
- when server are killed by a test case, do not wait for the server lock file to go away. These tests are mostly about client timeouts and the server will hang until killed. - when killing a server successfully, check for a remaining lock file, log its existence and remove it. - lower the delay timings on SLOWDOWN by half - add SLOWDOWNDATA server command to only slow down the FTP data bytes, not the control ones. - lower some timeout values Closes #14835
112 lines
4.3 KiB
Plaintext
112 lines
4.3 KiB
Plaintext
<testcase>
|
|
<info>
|
|
<keywords>
|
|
FTP
|
|
EPSV
|
|
RETR
|
|
timeout
|
|
FAILURE
|
|
SLOWDOWNDATA
|
|
flaky
|
|
timing-dependent
|
|
</keywords>
|
|
</info>
|
|
|
|
# Server-side
|
|
<reply>
|
|
<servercmd>
|
|
SLOWDOWNDATA
|
|
REPLY welcome 220 Hey
|
|
REPLY USER 331 OK
|
|
REPLY PASS 230 OK
|
|
REPLY PWD 257 "/"
|
|
REPLY TYPE 200 OK
|
|
</servercmd>
|
|
<data nocheck="yes">
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
Long chunk of data that couldn't possibly be sent in the time allotted.
|
|
</data>
|
|
</reply>
|
|
|
|
# Client-side
|
|
<client>
|
|
<server>
|
|
ftp
|
|
</server>
|
|
<killserver>
|
|
ftp
|
|
</killserver>
|
|
<name>
|
|
FTP download with strict timeout and slow data transfer
|
|
</name>
|
|
<command>
|
|
ftp://%HOSTIP:%FTPPORT/%TESTNUMBER -m 5
|
|
</command>
|
|
</client>
|
|
|
|
# Verify data after the test has been "shot"
|
|
<verify>
|
|
# 28 is CURLE_OPERATION_TIMEDOUT
|
|
<errorcode>
|
|
28
|
|
</errorcode>
|
|
<protocol>
|
|
USER anonymous
|
|
PASS ftp@example.com
|
|
PWD
|
|
EPSV
|
|
TYPE I
|
|
SIZE %TESTNUMBER
|
|
RETR %TESTNUMBER
|
|
</protocol>
|
|
</verify>
|
|
</testcase>
|