Covered the semaphore trace inserts in every state the macro tests

2026-09-20T04:57:41Z

Each of the eight semaphore services carries one in-line trace insert, and the macro scores twelve branch outcomes from six conditions: whether tracing is enabled, whether the event class is filtered, what system state the caller is in, whether the entry wraps the trace buffer, and whether a buffer-full notification is registered. One test of 117 enabled tracing, so six of the eight sites had never run the macro body at all and the create and the delete reached five outcomes of twelve. A new test walks the services once per condition, in an order that leaves the system as it found it. The create and the delete are driven through their internal entry points in the forced-state passes, because the error checking shell rejects them from a non-thread caller and the insert sits behind it. The positioning and the call are held under one SMP protection, so the boundary entry is the service's own by construction rather than by being quick enough, and the pass asserts a wrap per service so that a service whose slot was taken by something else fails here instead of losing coverage quietly. One entry short is the right distance: every one of these inserts sits ahead of its own counting and suspension logic, so nothing the service goes on to do writes in front of it. All eight semaphore sites read twelve of twelve, and the twelve tx_semaphore_ files are at 280/280 lines and 194/194 branch outcomes on the union basis. 123/123 tests pass in each of the eight configurations, and the new test passes fifty standalone repeats in every one of them. Assisted-by: Claude Code (Opus 5)

threadx.git/test/smp/regression/threadx_semaphore_trace_test.c, branch v6.4.1_cert

Covered the semaphore trace inserts in every state the macro tests