Issue created by Sebastian Huber: https://gitlab.rtems.org/rtems/rtos/rtems/-/work_items/5710
Six tests assume that the target executes fast enough for an operation to fit inside a window they do not state. On a slow target or an emulator they fail without a defect in the code they test. `psxclock` allows no tick of tolerance. `sp69` uses an asymmetric wall time window. `sptimecounter02` bounds the error by a constant rather than by a tick. The rbtree unit test records every verification, which makes the report far larger than it needs to be. `CallWithinISR()` waits without a bound. `sp20` does not flush its report, so the last part stays in the stream buffer when the system shuts down. Found while running the full test suite on eleven simulators. This description was created with Claude Code assistance. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/work_items/5710 You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/sent_notifications/5-a3qlhxhz54wnm22bvbnednjcu-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
