|
The six in-line trace inserts in the mutex 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 mutex 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, a get and a put from an interrupt and a delete from any caller that is
not a thread, so the inserts behind those four cannot be reached through the
published ones. The resident mutex carries no priority inheritance, so a release
with nothing suspended on it takes the simple path and the pass leaves the
calling thread's priority alone.
Every mutex insert now scores twelve of twelve, and the subsystem is at 517/517
lines and 513/517 branches. The four outcomes left are the exit arms of the four
TX_MISRA_ENABLE release loops, whose condition is produced unconditionally.
Merged over the six build configurations: 4304/4339 lines and 4358/4627
branches, up 58 outcomes, with the branch gate raised to 94.00 to hold them.
Assisted-by: Claude Code (Opus 5) <[email protected]>
|
