Detecting Tests Which Don't Have Enough Workspace

[Gedare Bloom]

On Thu, Mar 12, 2015 at 6:58 PM, Amar Takhar <amar at rtems.org> wrote:
> On 2015-03-12 12:41 -0500, Joel Sherrill wrote:
>> Hi
>>
>> Many BSPs can link a test but don't actually have enough memory
>> to run the test. They will fail in the first few lines when the requested
>> memory for the RTEMS work area is not available. I hacked together
>> a script which adds together the code, data, bss, work space and
>> stack space requested. If this exceeds physical memory on the board,
>> then the test will fail.  It is possible to come close and still run out of
>> memory during initialization (e.g. malloc, etc) but this approach could
>> detect some tests which will fail by inspecting them on the host.
>
> The waf build prints a warning during compile time that the test will not fit
> and pass the build.  I was going to add a summary at the end for any tests that
> won't fit and also add it to a report on BuildBot.
>
It includes the workspace size in its estimation of space? Already if
a test's binary executable size doesn't fit the build will fail at
link-time.

>
> Amar.
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel