RTEMS | crypt01 exceeds the default 400 s simulator time limit on sparc/erc32 (erc32-sis) (#5811)

[Joel Sherrill (@joel)]

Joel Sherrill commented: https://gitlab.rtems.org/rtems/rtos/rtems/-/work_items/5811#note_161290


Raising the time limit results in huge test times when there are failures. The original core set of tests never exceeded 40 seconds. 

@chris we have a per BSP test state. Is it possible for long running to have an argument? 

There still is the difference between simulated target execution time and how much host elapsed time that one takes. But on real hardware and simulators like sis and Tsim which have a way to set a simulated time limit, this distinction wouldn't matter. Thoughts?

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/work_items/5811#note_161290
You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/namespace/49/sent_notifications/6-06xjsjbfb5m7uvwo6wg8n7fky-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/20261019/5ba294bc/attachment-0001.htm>