Fixed a race between the two clock readings in the timer trace test

2026-09-20T00:47:03Z

The test checks the published tx_time_get() against _tx_time_get() once, because the SMP header remaps the macro to a direct read of the system clock and every pass below then drives the service rather than the macro. The two readings were taken with the tick running between them, so a tick landing there made them differ and failed the test. Measured at one run in two hundred. Both readings now happen inside one SMP protection, which is what the check always meant: the same value taken twice rather than two calls into the same function. 1,200 standalone runs green -- fifty repeats of each of the three new timer tests in each of the eight configurations -- against one failure in two hundred before. 116/116 in each of eight configurations, twice from clean, with retries disabled. Assisted-by: Claude Code (Opus 5)

Covered every timer and time trace insert with a new trace test

2026-09-20T00:03:13Z

One test of the ThreadX SMP regression suite enables event tracing, so the in-line trace insert each timer and time service carries ran almost everywhere with a null trace buffer pointer and scored one of its twelve branch outcomes. Eight sites sat at one or five of twelve, 80 uncovered outcomes in all. A new test walks the eight services once per condition the macro distinguishes: thread context, both event classes filtered out, interrupt context, initialization context, the state an interrupt presents, and a positioned buffer wrap with and without a full notification registered. The timer services and the time services score against different event classes, so the filtered pass filters both. One entry is the right wrap distance for all eight: no timer or time service writes an event buffer entry ahead of its own insert, and every service in the notified pass has to report a wrap of its own, so a boundary entry taken by something else fails the test rather than quietly losing coverage. One service is driven through its internal entry point in every pass rather than only in the forced-state ones, and that is the SMP path rather than the monoprocessor's. tx_api.h remaps tx_time_get() to a direct read of the system clock unless TX_MISRA_ENABLE is defined, so in six of the eight configurations the published macro never enters _tx_time_get and the insert inside it is unreachable from above. The test checks the macro against the service and then drives the service. The monoprocessor header has no such remapping. All eight sites read twelve of twelve, taking the tx_timer_ and tx_time_ group from 170 to 250 of its 252 branch outcomes on the union of eight configurations. 116/116 tests pass in each of the eight, twice from a clean tree, with retries disabled. Assisted-by: Claude Code (Opus 5)

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

Fixed a race between the two clock readings in the timer trace test

Covered every timer and time trace insert with a new trace test