Describe the bug
Occasionally the "condvar" functional test fails with an unexpected result, snippet of the test log here:

[ PASS] 02.017 condvar-test.c:170 - curr_condition (5) != ALL_RUN_CONDITION (7)
[ PASS] 02.018 condvar-test.c:171 - curr_condition (5) != 0 (0)
[ FAIL] 02.019 condvar-test.c:172 - task_states[i].run_count (0) == 1 (1)

The test case is expecting that the tasks will wake up in the same order on which they started pending on the condvar, but in this run, the second task woke up before the first task did.

To Reproduce
Intermittent issue, not directly reproducible. Not seen running locally, seems to occur only on cloud hosts where perhaps timing is not as accurate and system load is not predictable.

Expected behavior
Tests should pass

System observed on:
Github workflow

Additional context
As POSIX does not specifically guarantee an execution order here, this test case should be relaxed and not assume that tasks will execute work in the order they started.

Reporter Info
Joseph Hickey, Vantage Systems, Inc.