bartoszek/zephyr
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc: twister: Clarify that the minimums are rough

Browse Source 
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 <declan.snyder@nxp.com>
This commit is contained in:
Declan Snyder 2024-11-07 10:49:54 -06:00 committed by Mahesh Mahadevan
parent 91a59e7e15
commit 39f32eac37
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/develop/test/twister.rst
View File

@ -415,11 +415,11 @@ levels: <list of levels>
test will be selectable using the command line option ``--level <level name>``
min_ram: <integer>
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: <integer>
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: