cdce2460b3
Viktor Szakats
2026-06-08
Subject
runtests: allow skipping tests on torture, use for test 357
Binary
No binary (build failed)
Architecture & Compiler Flags
—
Build Log
(log yok)
Commit Diff GitHub →
docs/tests/FILEFORMAT.md +1 -0docs/tests/TEST-SUITE.md +3 -0tests/data/test357 +3 -0tests/runtests.pl +4 -0
docs/tests/FILEFORMAT.md+1 -0
| @@ -539,6 +539,7 @@ Features testable here are: | |
| - `SSPI` | |
| - `threaded-resolver` | |
| - `TLS-SRP` | |
| + | - `torture` - if runtests is running in memory test mode |
| - `TrackMemory` | |
| - `typecheck` | |
| - `threadsafe` | |
docs/tests/TEST-SUITE.md+3 -0
| @@ -188,6 +188,9 @@ that memory leaks do not occur even in those situations. It can help to | |
| compile curl with `CPPFLAGS=-DMEMDEBUG_LOG_SYNC` when using this option, to | |
| ensure that the memory log file is properly written even if curl crashes. | |
| + | If a specific test takes a long time to run in memory test mode, you can |
| + | disable it individually by adding `!torture` to its `<features>` section. |
| + | |
| ### Debug | |
| If a test case fails, you can conveniently get the script to invoke the | |
tests/data/test357+3 -0
| @@ -48,6 +48,9 @@ no-expect | |
| <server> | |
| http | |
| </server> | |
| + | <features> |
| + | !torture |
| + | </features> |
| <name> | |
| HTTP PUT with Expect: 100-continue and 417 response | |
| </name> | |
tests/runtests.pl+4 -0
| @@ -759,6 +759,10 @@ sub checksystemfeatures { | |
| } | |
| } | |
| + | if($torture) { |
| + | $feature{"torture"} = 1; |
| + | } |
| + | |
| if(!$curl) { | |
| logmsg "unable to get curl's version, further details are:\n"; | |
| logmsg "issued command: \n"; | |