SHIVAM DEOLANKAR commented on a discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1103#note_144755 rtems_clock_set() currently validates years only up to 2099. Although the internal time representation and conversion logic introduced in !339 support dates well beyond 2100 (up to about 4095), the API still rejects years ≥2100 and returns RTEMS_INVALID_CLOCK. The added tests verify this validation behavior for representative years beyond 2100 without increasing test runtime. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1103#note_144755 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
