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

Restored the missing licence headers on the ThreadX SMP regression tests

2026-09-19T16:19:41Z

109 of the 110 tracked files in test/smp/regression carry no copyright notice and no licence text at all. The one that does was added this month. Everything else in the repository -- common/src, common_smp/src, the ports, the samples -- carries the standard header, so this is an oversight in one directory rather than a deliberate exemption, and it has been there since the tests were first published. The monoprocessor tree had the same gap and was fixed the same way. The header added here is byte identical to the one in common_smp/src, including its SPDX identifier. Nothing else in these files changes: every hunk is ten added lines and none removed. There is deliberately no "Eclipse ThreadX contributors" line and no AI disclosure paragraph -- this commit contributes no code, it records the licence the files were always under. A later change that does contribute code to one of these files adds the contributor line and its own attribution at that point, which is when there is something to attribute. Verified: all eight build configurations build clean and pass 109 of 109, and the coverage figure is unmoved at 5386/5450 lines and 2807/3610 branches over the union of the eight. Assisted-by: Claude Code (Opus 5)

Allowed the SMP mutex suspension timeout test a late observation

2026-09-17T23:03:03Z

threadx_mutex_suspension_timeout_test's ThreadX SMP copy clears the clock, suspends on a mutex with a 33 tick timeout and then requires the clock to read exactly 33. The lower bound is the kernel property being checked: the suspension must not end early. The upper bound is not. The clock is read after this thread has been given a core again, and on this port the tick comes from a host timer thread rather than from hardware, so the read can land a tick or two past the expiry with nothing wrong. The equality fails on that latency alone, once in ninety configuration runs. The check now requires the clock to be no earlier than 33 and no later than 35, and reads it once into a local rather than twice, so a tick arriving between two reads cannot decide the result. Verified in default_build_coverage: passes as before, and with the requested timeout cut from 33 ticks to 20 it reports ERROR #3 and exits 1. Assisted-by: Claude Code (Opus 5)

Release ThreadX regression system

2023-04-04T09:40:54Z