Change #238529
Category | None |
Changed by | Daniel Stenberg <daniel | @haxx.se>
Changed at | Sun 06 Jul 2025 20:33:18 |
Repository | https://api.github.com/repos/curl/curl |
Project | curl/curl |
Branch | bagder/memory-limits |
Revision | f00a2add71b2cc248003fd45d434bfe6c16f8970 |
Comments
runtests: support memory-limits per test The idea here is to set limits per test how many allocations and maximum amount of memory it is allowed to use. This is a means to make sure the number and total size of allocations are kept in check and don't mistakenly "blow up". If runtests.pl detects that the given limits have been exceeded it fails the test case with an error. The `<verify>` part now supports `<limits>`, and in this section two limits can be set for each test (verified in debug builds only): Allocations: [number of allocation calls] Maximum allocated: [maximum concurrent memory allocated] Default limits (used if nothing is set in the test file): Allocations: 1000 Maximum allocated: 1000000 Closes #17821
Changed files
- docs/tests/FILEFORMAT.md
- tests/data/test1
- tests/data/test1129
- tests/data/test1156
- tests/data/test1291
- tests/data/test1559
- tests/data/test1560
- tests/data/test1651
- tests/data/test2302
- tests/data/test2303
- tests/data/test2601
- tests/data/test3207
- tests/data/test440
- tests/data/test442
- tests/data/test445
- tests/data/test497
- tests/data/test500
- tests/data/test575
- tests/data/test747
- tests/data/test751
- tests/data/test993
- tests/runtests.pl