Issue created by yassine cherni: https://gitlab.rtems.org/rtems/rtos/rtems/-/work_items/5811
## Summary Environment: - RTEMS: 7.0.0.4bca987369df73718cdee1576323c9384fc728b2 - RSB: 74fffa09a3df68b7e6cacabbde243ea7828edb34 - Toolchain: GCC 15.2.0 20250808 (RTEMS 7, Newlib 7d4336cf) - Host: Linux x86_64 (7.0.0-38-generic), Python 3.14.4 Steps: rtems-test --rtems-bsp=erc32-sis build/sparc/erc32/testsuites/libtests/crypt01.exe Result: reported as Failed. Console shows all hashes correct, then SIS prints "Time-out limit reached" and "Stopped at time 5600000000 (400000.000 ms)" before "\*\*\* END OF TEST CRYPT 1 \*\*\*". Reproducible every time (about 67 s real time). Cause: rtems/testing/sis.cfg defines "-tlim 400 s" by default, which is a simulated-time limit, so rtems-test --timeout has no effect. Verification: running the same executable with "sparc-rtems7-sis -r -tlim 2000 s" completes, prints END OF TEST and exits normally. Shutdown occurs at 10539788233 cycles, about 753 s simulated, roughly 1.9x the default limit. Context: full erc32-sis libtests run (675 tests) shows crypt01 as the only failure; the rest pass, are expected-fail, need user input, or are benchmarks. Question: should the erc32-sis time limit be raised, or crypt01 be marked as long-running/reduced for slow targets? Attached: [crypt01-console.log](/uploads/12d7e618b5fe69dc1c6a00c310b12774/crypt01-console.log) (400 s run) [crypt01-longlimit.log](/uploads/fce7e929edac5ef18290bec350e2a24f/crypt01-longlimit.log) (2000 s run) -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/work_items/5811 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-e89jay3ihthn99702hvnyrysu-1d/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
