From 39f32eac370249cfce99c8a0d150a8247b0b3a25 Mon Sep 17 00:00:00 2001 From: Declan Snyder Date: Thu, 7 Nov 2024 10:49:54 -0600 Subject: [PATCH] doc: twister: Clarify that the minimums are rough There is no way to know for sure the size of an image built for a test, given that zephyr can build for so many different architectures, platforms, software supports, etc. So it should be clear that the filter for min_ram and min_flash on the twister testcases is an estimate, and not a strictly well known value. Signed-off-by: Declan Snyder --- doc/develop/test/twister.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/develop/test/twister.rst b/doc/develop/test/twister.rst index 3999e6c96014cd..f535648dd6e910 100644 --- a/doc/develop/test/twister.rst +++ b/doc/develop/test/twister.rst @@ -415,11 +415,11 @@ levels: test will be selectable using the command line option ``--level `` min_ram: - minimum amount of RAM in KB needed for this test to build and run. This is + estimated minimum amount of RAM in KB needed for this test to build and run. This is compared with information provided by the board metadata. min_flash: - minimum amount of ROM in KB needed for this test to build and run. This is + estimated minimum amount of ROM in KB needed for this test to build and run. This is compared with information provided by the board metadata. .. _twister_test_case_timeout: