RTEMS | testsuites: Fix init task stack size and runner setup (!1480)

[Sharvin Neve (@Sharvin)]

Sharvin Neve created a merge request: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1480

Project:Branches: Sharvin/rtems:fix-testsuite-init-task-sizes to rtems/rtos/rtems:main
Author:   Sharvin Neve



Closes #5748.

Addresses the two issues described in #5748:

1. **`flashdev01`**: `run_test()` holds a 2048-byte buffer and takes a ~2496-byte
   stack frame. On SPARC (and other targets where minimum stack is 4096 bytes or
   lower), running on the default minimum stack caused stack overflow and
   overwrote the first block of the heap, triggering exceptions in `_Heap_Iterate()`.
   Configured `CONFIGURE_INIT_TASK_STACK_SIZE` to `( 2 * RTEMS_MINIMUM_STACK_SIZE + 4096 )`
   to ensure ample headroom across all architectures.

2. **`smpmulticast01`**: `after_drivers()` initialized the test framework via
   `T_run_initialize()` during early device driver system initialization before
   multitasking started. This recorded the boot processor idle thread as the
   test runner. When `Init()` executed `T_run_all()`, all test reports were directed
   into `config.buf` which is NULL, silently dropping all results and causing test
   failure. Calling `T_make_runner()` inside `Init()` prior to `T_run_all()` assigns
   the init task as the test runner, restoring direct unbuffered output.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1480
You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/sent_notifications/5-7y2rbz5cdai80rg3ttaa9zq60-1d/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260908/7acf8c60/attachment.htm>