diff options
| author | Frank Kühndel <frank.kuehndel@embedded-brains.de> | 2021-07-23 10:47:35 +0200 |
|---|---|---|
| committer | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2021-07-23 16:16:09 +0200 |
| commit | fc3586fe37824e51d47840bb97df827916ddd4d3 (patch) | |
| tree | 74b8766b52f4ed20dfa15353813854cb291ff218 /spec/c | |
| parent | spec: Remove always enabled interrupt attribute (diff) | |
| download | rtems-central-fc3586fe37824e51d47840bb97df827916ddd4d3.tar.bz2 | |
spec: Fix unstable test of clock manager
The tests of specification get-tod.yml and set.yml were expecting
that no more than five ticks pass between consecutive calls to
rtems_clock_set() and rtems_clock_get_tod(). Yet, in coverage tests
this limit was exceeded.
* All tests are placed in a test suite without clock driver so that
all ticks must be triggered by the test suite.
* The grace period of five ticks has been removed.
* Test which require that the realtime clock has not been set
manipulate RTEMS internal data with `_TOD.is_set = false`.
The old function get_tod_before_set_tod() has been removed
in favor of this new solution.
Diffstat (limited to 'spec/c')
| -rw-r--r-- | spec/c/req/clock-nanosleep.yml | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/spec/c/req/clock-nanosleep.yml b/spec/c/req/clock-nanosleep.yml index fbec98d1..912bc1d0 100644 --- a/spec/c/req/clock-nanosleep.yml +++ b/spec/c/req/clock-nanosleep.yml @@ -359,6 +359,8 @@ test-prepare: | test-setup: brief: null code: | + rtems_time_of_day now = { 1988, 1, 1, 0, 0, 0, 0 }; + T_rsc_success( rtems_clock_set( &now ) ); SetSelfPriority( PRIO_NORMAL ); ctx->worker_id = CreateTask( "WORK", PRIO_HIGH ); StartTask( ctx->worker_id, Worker, ctx ); |