Central | spec/rtems/clock: remove TOD tests assuming y2100 (!16)

[Frank Kuehndel (@frank_k)]

Frank Kuehndel commented: https://gitlab.rtems.org/rtems/prequal/rtems-central/-/merge_requests/16#note_142818


Today, the names `Youngest` and `Oldest` sound non-logical to me. Not sure why I did choose them when `set.yml` was created years ago.

Anyway, if you just want that dates above 2100 are accepted, you could leave the `Oldest` and re-use it as soon as you know what is the "last date in the future still supported". Alternatively, you could just rename `Oldest` to something like `LastDay2099`.

I managed to build this patch and run the resulting test with QEMU successfully (after working around some troubles not related to this patch).

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/prequal/rtems-central/-/merge_requests/16#note_142818
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/20260216/9fa3565f/attachment.htm>