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

[Gedare Bloom (@gedare)]

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

 > -  directive_failed( status, "rtems_clock_set" );
 > +  directive_failed(status, "rtems_clock_set"); // expect SUCCESS
 >    print_time( "TA1 - rtems_clock_set - ", &time, " - RTEMS_SUCCESSFUL\n" );
 >    status = rtems_task_wake_after( rtems_clock_get_ticks_per_second() );
 >    status = rtems_clock_get_tod( &time );
 >    directive_failed( status, "rtems_clock_get_tod" );
 >    print_time( "TA1 - rtems_clock_get_tod - ", &time, " - RTEMS_SUCCESSFUL\n" );
 >  
 > +  build_time( &time, 3, 1, 2400, 0, 0, 0, 0 );
 > +  status = rtems_clock_set( &time );
 > +  directive_failed(status, "rtems_clock_set"); // expect SUCCESS
 > +  print_time( "TA1 - rtems_clock_set - ", &time, " - RTEMS_SUCCESSFUL\n" );
 > +  status = rtems_task_wake_after( rtems_clock_get_ticks_per_second() );
 > +  status = rtems_clock_get_tod( &time );
 > +  directive_failed( status, "rtems_clock_get_tod" );
 > +  print_time( "TA1 - rtems_clock_get_tod - ", &time, " - RTEMS_SUCCESSFUL\n" );

Add the asserts to the other blocks also. At that point, we can probably reduce the printed output of this test also. We prefer to have tests that print less (and assert more).

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