From 8615fe8a854370e0d2b0cf0ba284730018abbc25 Mon Sep 17 00:00:00 2001 From: Joseph Hickey Date: Wed, 7 Jul 2021 12:34:22 -0400 Subject: [PATCH] Update #1083, correct comment in timebase callback Per review feedback, removes comment that was stale and no longer valid, and describe why only POSIX_OS is enabled here on this check. --- src/tests/time-base-api-test/time-base-api-test.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/tests/time-base-api-test/time-base-api-test.c b/src/tests/time-base-api-test/time-base-api-test.c index 7cf35913d..dc72656f8 100644 --- a/src/tests/time-base-api-test/time-base-api-test.c +++ b/src/tests/time-base-api-test/time-base-api-test.c @@ -43,10 +43,10 @@ static uint32 UT_TimerSync(osal_id_t timer_id) { /* * Calls to time base configuration from the context of a sync function - * should be rejected with OS_ERR_INCORRECT_OBJ_STATE. However because - * UtAssert is not fully thread-safe, this does not assert here, it just - * calls the various functions on the first time through and stores the - * result, which is checked/asserted in the main task. + * should be rejected with OS_ERR_INCORRECT_OBJ_STATE. Note that only the + * POSIX provides the mechanism for this error check to actually work - On + * other platforms the error checking may not be possible, depending on how + * OS_TaskGetId_Impl() responds when called from a non-OSAL task. */ #ifdef _POSIX_OS_ if (NumSyncs == 0)