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

[SHIVAM DEOLANKAR (@D3athSkulll)]

SHIVAM DEOLANKAR commented on a discussion on testsuites/sptests/spclock_err02/init.c: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1103#note_149125

 >    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 );

these tests are validating years after 2100.

I can add the functionality for leap year checking too.

3rd march 0000 hrs was kept as standard date for testing so I went with this

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