threadx.git/test/smp/regression/threadx_time_get_set_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)

Gave the time get and set test's post-sleep read a one-tick band

2026-09-18T10:04:00Z

threadx_time_get_set_test clears the clock, sleeps 35 ticks and requires the clock to read exactly 35. That is the same shape as the two sites fixed earlier in this batch: the read happens once this thread has been given a core again, and on this port that is a host timer thread and four emulated cores rather than hardware, so it can land a tick late with nothing wrong. The check now requires the clock to be no earlier than 35 and no later than 36. The lower bound is the property -- a sleep that ends early is a real fault -- and the upper is scheduling latency. The same band is already in threadx_thread_simple_sleep_test and its non-clear twin, both of which accept 18 or 19 after sleeping 18, so this is the suite's own precedent. The second comparison in the same file, tx_time_get() against 7 on the line after tx_time_set(7), is left exact. Its window is a handful of instructions against a ten millisecond tick, and a band there would remove the only fault it can catch. This corrects the record as well. The commit that closed the other two sites said this file's only exact comparison was the one read on the line after it is set. There are two, and the one it missed is the more exposed: that sweep matched tx_time_get() against a literal and skipped the site assigning into a variable first. Re-swept on every form of clock read, nothing else exact remains. Verified in default_build_coverage: passes, and with the sleep shortened to 30 ticks it reports ERROR #2 and exits 1. Assisted-by: Claude Code (Opus 5)

Release ThreadX regression system

2023-04-04T09:40:54Z