Dmitry Ilvokhin 143f458188 Fix hpa_strict_min_purge_interval option logic ... We update `shard->last_purge` on each call of `hpa_try_purge` if we purged something. This means, when `hpa_strict_min_purge_interval` option is set only one slab will be purged, because on the next call condition for too frequent purge protection `since_last_purge_ms < shard->opts.min_purge_interval_ms` will always be true. This is not an intended behaviour. Instead, we need to check `min_purge_interval_ms` once and purge as many pages as needed to satisfy requirements for `hpa_dirty_mult` option. Make possible to count number of actions performed in unit tests (purge, hugify, dehugify) instead of binary: called/not called. Extended current unit tests with cases where we need to purge more than one page for a purge phase.		2024-08-20 10:02:38 -07:00
..
analyze	Tcache batching: Plumbing	2024-05-22 10:30:31 -07:00
include/test	Add batching to arena bins.	2024-05-22 10:30:31 -07:00
integration	Make headers self-contained by fixing #includes	2023-07-14 09:06:32 -07:00
src	Enable a few additional warnings for CI and fix the issues they uncovered	2023-08-11 13:56:23 -07:00
stress	increase the ncached_max in fill_flush test case to 1024	2024-08-06 13:16:09 -07:00
unit	Fix hpa_strict_min_purge_interval option logic	2024-08-20 10:02:38 -07:00
test.sh.in	Print test error messages in color when stderr is a terminal	2023-07-13 13:03:23 -07:00