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

[Gedare Bloom (@gedare)]

Gedare Bloom started a new discussion on testsuites/sptests/spclock_err02/init.c: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1103#note_149077

 >    directive_failed( status, "rtems_clock_get_tod" );
 >    print_time( "TA1 - rtems_clock_get_tod - ", &time, " - RTEMS_SUCCESSFUL\n" );
 >  
 > -  build_time( &time, 1, 1, 4096, 0, 0, 0, 0 );
 > +  /* Additional future year checks */
 > +
 > +  build_time( &time, 3, 1, 2100, 0, 0, 0, 0 );

Should this be set to the last tick of February 28, and then check that the leap year is calculated properly after sleeping? It's not clear to me what these tests are validating.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1103#note_149077
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/20260427/d87b5749/attachment-0001.htm>