e582bc128a
The original k_mem_pool tests were a mix of code that tests routine allocator behavior, the synchronization layer above that, and a significant amount of code that made low-level assumptions about the specific memory layout of the original allocator, which doesn't run out of memory in exactly the same way. Adjust the expectations as needed for the backend. A few test cases were skipped if they were too specific. Most have been generalized (for example, iteratively allocating to use up all memory instead of assuming that it will be empty after N allocations). Signed-off-by: Andy Ross <andrew.j.ross@intel.com> |
||
|---|---|---|
| .. | ||
| main.c | ||
| test_mpool_api.c | ||
| test_mpool_extern.c | ||
| test_mpool.h | ||