#
e70c22b6 |
| 09-Sep-2024 |
Stefan Eissing |
tests: tweak lock file handling and timers - 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 th
tests: tweak lock file handling and timers - 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
show more ...
|
#
3fd80c7b |
| 04-Oct-2023 |
Daniel Stenberg |
tests: remove leading spaces from some tags The threee tags `<name>`, `</name>` and `<command>` were frequently used with a leading space that this removes. The reason this habbit is so
tests: remove leading spaces from some tags The threee tags `<name>`, `</name>` and `<command>` were frequently used with a leading space that this removes. The reason this habbit is so widespread in testcases is probably that they have been copy and pasted. Hence, fixing them all now might curb this practice from now on. Closes #12028
show more ...
|
#
d29a62d7 |
| 11-Sep-2023 |
Dan Fandrich |
tests: stop overriding the lock timeout These tests reduce the server lock wait timeout which can increase flakiness on loaded machines. Since this is merely an optimization, elimina
tests: stop overriding the lock timeout These tests reduce the server lock wait timeout which can increase flakiness on loaded machines. Since this is merely an optimization, eliminate them in favour of reliability. Ref: #11328
show more ...
|
#
381792df |
| 08-Sep-2023 |
Dan Fandrich |
tests: add the timing-dependent keyword on several tests These are ones likely to fail on heavily-loaded machines that alter the normal test timing. Most of these tests already had the f
tests: add the timing-dependent keyword on several tests These are ones likely to fail on heavily-loaded machines that alter the normal test timing. Most of these tests already had the flaky keyword since this condition makes them more likely to fail on CI.
show more ...
|
#
ad3c8359 |
| 06-Sep-2023 |
Dan Fandrich |
tests: improve SLOWDOWN test reliability by reducing sent data These tests are run in SLOWDOWN mode which adds a 10 msec delay after each character output, which means it takes at least
tests: improve SLOWDOWN test reliability by reducing sent data These tests are run in SLOWDOWN mode which adds a 10 msec delay after each character output, which means it takes at least 1.6 seconds (and 320 kernel calls) just to get through the long welcome banner. On an overloaded system, this can end up taking much more than 1.6 seconds, and even more than the 7 or 16 second curl timeout that the tests rely on, causing them to fail. Reducing the size of the welcome banner drops the total number of characters sent before the transfer starts by more than half, which reduces the opportunity for test-breaking slowdowns by the same amount. Ref: #11328
show more ...
|
#
b5d955bc |
| 10-Mar-2023 |
Dan Fandrich |
tests: add timeout, SLOWDOWN and DELAY keywords to tests These are tests that are testing timing and end up being quite slow.
|
Revision tags: curl-7_76_1, curl-7_76_0 |
|
#
e2b4df7b |
| 12-Mar-2021 |
Daniel Stenberg |
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738
|
Revision tags: curl-7_75_0, curl-7_74_0, curl-7_73_0, tiny-curl-7_72_0, curl-7_72_0, curl-7_71_1, curl-7_71_0, curl-7_70_0, curl-7_69_1, curl-7_69_0, curl-7_68_0, curl-7_67_0, curl-7_66_0, curl-7_65_3, curl-7_65_2, curl-7_65_1, curl-7_65_0, curl-7_64_1, curl-7_64_0, curl-7_63_0, curl-7_62_0, curl-7_61_1, curl-7_61_0, curl-7_60_0, curl-7_59_0, curl-7_58_0, curl-7_57_0, curl-7_56_1, curl-7_56_0, curl-7_55_1, curl-7_55_0, curl-7_54_1, curl-7_54_0, curl-7_53_1, curl-7_53_0, curl-7_52_1, curl-7_52_0, curl-7_51_0, curl-7_50_3, curl-7_50_2, curl-7_50_1, curl-7_50_0, curl-7_49_1, curl-7_49_0, curl-7_48_0, curl-7_47_1, curl-7_47_0, curl-7_46_0, curl-7_45_0, curl-7_44_0, curl-7_43_0, curl-7_42_1, curl-7_42_0, curl-7_41_0, curl-7_40_0, curl-7_39_0, curl-7_38_0, curl-7_37_1, curl-7_37_0, curl-7_36_0, curl-7_35_0, curl-7_34_0, curl-7_33_0 |
|
#
4f591b91 |
| 22-Sep-2013 |
Benoit Sigoure |
test1112: Increase the timeout from 7s to 16s As someone reported on the mailing list a while back, the hard-coded arbitrary timeout of 7s in test 1112 is not sufficient in some build
test1112: Increase the timeout from 7s to 16s As someone reported on the mailing list a while back, the hard-coded arbitrary timeout of 7s in test 1112 is not sufficient in some build environments. At Arista Networks we build and test curl as part of our automated build system, and we've run into this timeout 170 times so far. Our build servers are typically quite busy building and testing a lot of code in parallel, so despite being beefy machines with 32 cores and 128GB of RAM we still hit this 7s timeout regularly. URL: http://curl.haxx.se/mail/lib-2010-02/0200.html
show more ...
|
Revision tags: curl-7_32_0, curl-7_31_0, curl-7_30_0, curl-7_29_0, curl-7_28_1, curl-7_28_0, curl-7_27_0, curl-7_26_0, curl-7_25_0, curl-7_24_0, curl-7_23_1, curl-7_23_0, curl-7_22_0, curl-7_21_7, curl-7_21_6, curl-7_21_5, curl-7_21_4, curl-7_21_3, curl-7_21_2, curl-7_21_1, curl-7_21_0, curl-7_20_1, curl-7_20_0 |
|
#
e2fc2944 |
| 03-Feb-2010 |
Yang Tse |
added an additional second to allow test to pass on heavily loaded servers
|
#
8c8df396 |
| 13-Jan-2010 |
Yang Tse |
Give the test a bit mote time to run so it passes on slow machines
|
#
06438294 |
| 12-Jan-2010 |
Yang Tse |
Added test case #1112 which does an FTPS download with strict timeout and slow data transfer in a similar way as test case #1086 does for FTP. This also exercises <killserver> section fo
Added test case #1112 which does an FTPS download with strict timeout and slow data transfer in a similar way as test case #1086 does for FTP. This also exercises <killserver> section for the FTPS server.
show more ...
|