tests/thread_apis: Allow 20µs slop in k_busy_wait test

When testing k_busy_wait(100), don't require that at least 100µs of CPU
time be consumed by the thread itself; some of that time may be used
elsewhere in the system. Instead, just make sure that at least 80µs is
accounted to the thread and allow 20µs to get used elsewhere.

Signed-off-by: Keith Packard <[email protected]>

tests/kernel/threads/thread_apis/src/main.c

@@ -572,7 +572,13 @@ ZTEST(threads_lifecycle, test_k_busy_wait)
 
 	/* execution_cycles increases correctly */
 	dt = test_stats.execution_cycles - cycles;
-	zassert_true(dt >= k_us_to_cyc_floor64(100));
+
+	/* execution cycles may not increase by the full 100µs as the
+	 * system may be doing something else during the busy
+	 * wait. Experimentally, we see at least 80% of the cycles
+	 * consumed in the busy wait loop on current test targets.
+	 */
+	zassert_true(dt >= k_us_to_cyc_floor64(80));
 }
 
 static void tp_entry(void *p1, void *p2, void *p3)