Covered the event flags services' trace inserts and the zero-flag request

2026-09-15T19:08:46Z

The six in-line trace inserts in the event flags services were reached in one system state only, so each scored one or five of the twelve branch outcomes the macro carries. A new regression test walks the six services once per condition the macro distinguishes: thread context with every event enabled, the event flags trace event class filtered out, interrupt context through the test ISR dispatch, initialization context, the state an interrupt presents, and a positioned buffer wrap with and without a buffer-full notification registered. The forced-state passes drive the internal entry points, because the error checking shell rejects a create from an interrupt and a delete from any caller that is not a thread, so the inserts behind those two cannot be reached through the published ones. A second test covers the remaining arm of the get service's suspension check. A request for no flags at all cannot be satisfied under any option, so a thread that suspended on it would never be resumed and the service refuses the suspension instead. The companion arm, a suspension requested while preemption is disabled, is already driven by the test control preempt-disable safeguard. Every event flags insert now scores twelve of twelve, and the subsystem is at 396/396 lines and 421/421 branches. Merged over the six build configurations: 4304/4339 lines and 4418/4627 branches, up 60 outcomes, with the branch gate raised to 95.00 to hold them. Assisted-by: Claude Code (Opus 5)

threadx.git/test/tx/regression/threadx_event_flag_zero_request_test.c, branch v6.4.1_cert

Covered the event flags services' trace inserts and the zero-flag request