RTEMS | testsuites/sptests: Edit spclock_err02 for post-2100 validation (!1103)

[SHIVAM DEOLANKAR (@D3athSkulll)]

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.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260307/2ddc87c5/attachment.htm>