1 <assertions> 2 <assertion id="1" tag="pt:CS" files=""> 3 The clock time can be set to 0, a large number, Y2K critical dates, 4 and times around daylight savings. 5 </assertion> 6 <assertion id="2" tag="pt:CS" files=""> 7 clock_gettime() with CLOCK_REALTIME is monotonically increasing in both 8 seconds and nanoseconds. 9 </assertion> 10 <assertion id="3" tag="pt:CS" files=""> 11 Clock time for clocks: 12 CLOCK_REALTIME 13 CLOCK_MONOTONIC 14 is equivalent to some known good clock over time, even if the time 15 is reset. 16 </assertion> 17 <assertion id="4" tag="pt:CS" files=""> 18 Having a call to clock_settime() interrupted with a signal does not 19 affect the setting of the clock. 20 </assertion> 21 <assertion id="5" tag="pt:CS" files=""> 22 Killing a process setting the clock does not affect the clock time in 23 an unpredictable fashion. 24 </assertion> 25 <assertion id="6" tag="pt:CS" files=""> 26 If clocktime is set as a timer expires, the time is still set correctly. 27 </assertion> 28 <assertion id="7" tag="pt:CS" files="clocks/twopsetclock.c"> 29 Two processes can attempt to set the clock at (nearly) the same time and 30 both sets will succeed, with the later one taking effect. 31 </assertion> 32 <assertion id="8" tag="pt:TMR" files=""> 33 The a timer can be set to expire at 0, a large number, Y2K critical dates, 34 and times around daylight savings with no unpredictable results. 35 </assertion> 36 <assertion id="9" tag="pt:TMR" files=""> 37 Timers (relative and absolute) expire at the POSIX-defined times when the 38 clock changes. 39 </assertion> 40 <assertion id="10" tag="pt:TMR" files=""> 41 Multiple relative timers set up in a particular order (possibly with a small 42 delay between each) expire in the order set up. [Not required by POSIX, 43 though, so this should not fail if it does not work.] 44 </assertion> 45 <assertion id="11" tag="pt:TMR" files=""> 46 All possible events can be sent on timer expirations. 47 </assertion> 48 <assertion id="12" tag="pt:TMR" files="timers/twoevtimers.c"> 49 Two timers in one process can expire at the same time, but with 50 different events. 51 </assertion> 52 <assertion id="13" tag="pt:TMR" files="timers/twoptimers.c"> 53 Timers in two different processes which are set to expire at the same time 54 are able to expire at the same time. 55 </assertion> 56 <assertion id="14" tag="pt:TMR" files=""> 57 A repeating timer set to expire at time X and a non-repeating set to 58 expire at 2X will both expire at the same time at 2X. 59 </assertion> 60 <assertion id="15" tag="pt:TMR" files=""> 61 A repeating timer will expire at the correct time for at least ten 62 expirations. 63 </assertion> 64 <assertion id="16" tag="pt:TMR" files=""> 65 For multiple repeating timers with different intervals blocked, the 66 overrun count for each is correct. 67 </assertion> 68 <assertion id="17" tag="pt:TMR" files=""> 69 Overrun count and timer_gettime() return correct values when 70 SIGEV_NONE is used in ev.sigev_notify. 71 </assertion> 72 <assertion id="18" tag="pt:TMR" files=""> 73 Calling timer_getoverrun() as an overrun is happening returns the 74 correct value. 75 </assertion> 76 <assertion id="19" tag="pt:TMR" files=""> 77 A process can sleep until 0, a large number, Y2K critical dates, 78 and times around daylight savings with no unpredictable results. 79 </assertion> 80 <assertion id="20" tag="pt:TMR" files=""> 81 Sleeps (relative and absolute) expire at the POSIX-defined times when the 82 clock changes. 83 </assertion> 84 <assertion id="21" tag="pt:TMR" files=""> 85 Sleeps in two different processes which are set to end at the same time 86 are able to end at the same time. 87 </assertion> 88 </assertions> 89
