threadx.git/test/smp/cmake/coverage.sh, branch v6.4.1_cert

Excluded the SMP regression-test hook code from the coverage figure

2026-09-23T13:42:51Z

Every SMP build configuration is compiled with -DTX_REGRESSION_TEST, which opens a block in the Linux SMP port header defining ten macros that expand to live code -- flag tests, state changes and calls -- at eleven sites in common_smp/src. An application defines none of them and tx_api.h expands them all to nothing, but gcov attributes a macro expansion to the file that invokes it, so the harness's own scaffolding was being counted as certified source. coverage_union.py now drops those sites and prints what it dropped, covered and total on both axes, so the exclusion can be audited rather than inferred. One site keeps its line: tx_api.h defines TX_TIMER_INITIALIZE_EXTENSION as a real statement under TX_MISRA_ENABLE, so that line ships and only its branches come out. A listed site that no longer matches the report is a hard failure naming the macro, not a silent skip. The branch gate moves 99.05 to 99.04 because the margin is ten outcomes rather than a percentage, and a smaller denominator buys nine at the old value; the line gate is unchanged. The excluded code measured 10 lines and 36 branch outcomes, every one of them covered, so the uncovered set is untouched: the same 24 outcomes at the same 22 sites in the same 13 files, over the same 194 files. Eight configurations from a wiped tree, 136/136 tests in each, 0 failed. The union goes from 5449/5450 lines and 3588/3612 branch outcomes to 5439/5440 and 3552/3576, re-derived key by key against the previous measurement. gcovr's merged report is published unchanged. Assisted-by: Claude Code (Opus 5)

Corrected the gate comment's count of single-carrier outcomes

2026-09-21T12:36:35Z

The comment added in the previous commit said six outcomes in the figure have no configuration to cover for them. That was the count of outcomes that both have a single carrier and were seen moving between runs, not the count of single-carrier outcomes, and as written it is wrong. Measured over sixteen runs at two commits: thirty-five outcomes are compiled by two configurations and covered by only one of them in at least one run, almost all TX_THREAD_STACK_CHECK fence ordinals that stack_checking_build holds alone because its random-fill sibling short-circuits before them. A further 894 are compiled by exactly one configuration at all, which is structural rather than fragile, the racing outcome excepted. The margin's justification is restated on the figure that actually sizes it: the largest movement observed in any one configuration is eight outcomes, and the margin is ten. No threshold changes. The gate stays at 99.79 line and 99.05 branch, and sixteen runs read 5449/5450 lines and 3588/3612 branch outcomes on the union basis with an empty unstable set on both axes. Assisted-by: Claude Code (Opus 5)

Settled the SMP coverage gate margin on the evidence measurement

2026-09-21T12:18:43Z

The gate's comment left open whether the ten-line, ten-outcome margin could be removed once the unstable set closed, and deferred the answer to the coverage evidence work. It has now been measured. The thresholds do not move, and the comment records why. Read per configuration over eight CI runs at one commit, eight branch outcomes and four lines move between runs, and six outcomes in the published figure are compiled by only one configuration that covers them: five TX_THREAD_STACK_CHECK arms that stack_checking_build carries alone in most runs, because stack_checking_rand_fill_build misses them in seven and four runs of eight, and the trace race outcome, which only trace_build compiles. The union figure is stable because the eight configurations cover for each other, not because the suite is deterministic, so a zero-margin gate would read a runner's timing as a regression. Eight runs at the preceding commit read 5449/5450 lines and 3588/3612 branch outcomes identically on the union basis, unstable set empty on both axes, 136/136 tests in each of the 64 configuration-runs. gcovr's merged report over those same runs reads 6561, 6563 and 6564 of 6601, which is the same movement seen through a denominator that does not collapse it. Assisted-by: Claude Code (Opus 5)

Raised the SMP gate onto the floor the trace race test lifted

2026-09-21T04:01:02Z

The coverage ratchet sat at 99.03 branch, set below the 3587 outcomes every run of the previous sample reached. Covering the user event insert's disabled-buffer arm moves that floor by one. Raised to 99.05, still ten outcomes below the set covered in every run, which is now 3588 of 3612. The line gate is unchanged at 99.79: neither the line total nor its denominator moved. The comment above the thresholds gains the one thing about this figure a later reader has to know -- a single outcome in it is reached by two cores racing rather than by a thread doing something in order, and it is counted in the always-covered set on a measurement over ten runs on two machines rather than on one sample. Seven CI runs at the test head, all green, 136/136 in each of eight configurations, 5449/5450 and 3588/3612 in every one. Two clean local cycles read the same two totals. Assisted-by: Claude Code (Opus 5)

Raised the SMP gate onto the new denominator and floor

2026-09-21T00:09:11Z

The coverage ratchet sat at 99.79 line and 98.97 branch against a branch denominator of 3610. The port hook's new clause adds two covered outcomes to tx_byte_allocate.c, so the denominator is 3612, and the sweep closed two further outcomes on top of that. The branch gate goes to 99.03, still ten outcomes below the 3587 of 3612 covered in every run of the sample. The line gate is unchanged at 99.79: neither the line total nor its denominator moved. The comment above the thresholds records why the denominator moved, and that the unstable set is now empty in two consecutive samples on two different trees rather than one. The margin stays for the reason it was kept before -- five earlier samples moved an outcome in every direction there is -- and whether it can go is the evidence step's question. Seven CI runs at the sweep head, all green, 135/135 in each of eight configurations, 5449/5450 and 3587/3612 in every one. Two clean local cycles read the same two totals. Assisted-by: Claude Code (Opus 5)

Raised the SMP gate onto the floor the trace batch lifted

2026-09-20T22:40:57Z

The coverage ratchet sat at 99.32 line and 97.42 branch, set below the 5423 lines and 3527 branch outcomes every run of the previous sample reached. The initialize, trace and MISRA shim batch has moved both floors. Raised to 99.79 and 98.97, still ten lines and ten outcomes below the set covered in every run of the sample, which is now 5449 lines and 3583 outcomes of 5450 and 3610. The comment above the thresholds is rewritten around the fact that made this sample different: all seven runs read the same two totals, so the unstable set is empty for the first time and the always-covered floor and the worst observation coincide. The margin stays, because five earlier samples moved an outcome in every direction there is, twice on the pair this batch has just closed; whether it can go is the evidence step's question and not this one's. Seven CI runs at the batch head, all green, 134/134 in each of eight configurations, 5449/5450 and 3583/3610 in every one. Two clean local cycles read the same two totals. Assisted-by: Claude Code (Opus 5)

Raised the SMP gate onto the floor the pool batch lifted

2026-09-20T17:47:34Z

The byte pool and block pool batch moved the union figure from 5398 lines and 3399 branch outcomes to 5423 and 3531, and the gate was still set for the figure before it. A gate that trails the work by a whole batch stops being a ratchet. Set from the set of lines and outcomes covered in every one of seven CI runs -- 5423 and 3527 -- ten lines and ten outcomes below it, which is the basis the comment above the thresholds describes and the same margin the last four raises used. The always-covered branch total went 3395 to 3527; the line total, 5398 to 5423. Seven runs at this tree read 5423 lines in every one of them and between 3527 and 3531 outcomes. Four outcomes at two sites remain unstable and both sites belong to the trace batch that has not run yet; the line axis has now been stable across thirty-five runs in five samples. Assisted-by: Claude Code (Opus 5)

Raised the SMP gate onto the floor the semaphore batch lifted

2026-09-20T05:13:43Z

Closing the trace inserts, the zero-request refusal and the two prioritize retry arms across the semaphore, mutex and event flags sources took the set of branch outcomes covered in every run from 3195 to 3395, and the set of lines from 5396 to 5398, so the gate no longer sits ten below either. Re-derived on the union basis over a fourth sample of seven CI runs: 5398 of 5450 lines and 3395 of 3610 outcomes are covered in every one, and the gate is set ten below each, at 98.86 and 93.76. What is left unstable is four outcomes at two sites, up from two at one, and the comment above the thresholds records why that is not a regression to chase: the buffer-wrap arm of the ISR enter insert was unstable over fourteen runs, covered in all seven of the next sample with nothing touching it, and is missed in one run of seven again here. Four samples have now moved an outcome in every direction the three columns allow. Seven CI runs at this commit's parent, all green, 123/123 tests in each of eight configurations, retries disabled, and two clean workstation runs besides. The line axis did not move within the sample at all. Assisted-by: Claude Code (Opus 5)

Raised the SMP branch gate onto the floor the walk test lifted

2026-09-20T03:55:13Z

Closing the ready-list walk in the time-slice rebalance took the set of branch outcomes covered in every run from 3194 to 3195, so the gate no longer sits ten outcomes below it. Re-derived on the union basis over a third sample of seven CI runs: 5396 of 5450 lines and 3195 of 3610 outcomes are covered in every one, and the gate is set ten below each, at 98.82 and 88.22. The line threshold does not move. What is left unstable is two outcomes at one site, the buffer-wrap arm of the ISR exit trace insert, down from five at three sites. The comment above the thresholds records all three samples, including an outcome that came back covered in every run of the third with nothing touching it. Twenty-one CI runs across the three samples, all green, 117/117 tests in each of eight configurations, retries disabled. The margin earned itself immediately: the first clean workstation run after it was set read 3194, one outcome below the CI floor, on a stack check covered in all twenty-one CI runs. Assisted-by: Claude Code (Opus 5)

Recorded the second variance sample behind the SMP coverage gate

2026-09-20T01:01:50Z

The gate's thresholds were derived from one sample of seven CI runs, taken a commit before the one they ship with. A second sample of seven has since been taken at the head, and it puts the same 5396 lines and 3194 branch outcomes in the always-covered column and the same five outcomes in the unstable one. The comment above the thresholds now states both samples and the fact that they agree. The thresholds themselves do not move: a floor two independent samples report identically is the one the gate was already set ten lines and ten outcomes below. Fourteen CI runs, all green, 116/116 tests in each of eight configurations, retries disabled. Assisted-by: Claude Code (Opus 5)