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

Closed the two tick-exact assertions the first sweep for them missed

2026-09-18T04:33:07Z

threadx_timer_information_test carries the same check as threadx_timer_simple_test, character for character -- expiration counter exactly 23 and clock exactly 120 after a sleep of 120 -- and threadx_semaphore_timeout_test carries the same check as threadx_mutex_suspension_timeout_test, a clock of exactly 33 after a suspension with a 33 tick timeout. Neither was in the inventory this step started from, and the first pass fixed only the copy of each that had been seen to fail. A campaign of ninety configuration runs then caught the timer information test twice. Both now get the fix their twin already has. The timer counter is bounded above by the clock it was read beside, which is exact and catches a timer expiring too often, and below by a floor of twenty. The semaphore timeout keeps its lower bound of 33, which is the kernel property, and is allowed two ticks above it for the latency of being given a core again. The suite was swept for the rest of the class rather than fixed instance by instance. The only other exact comparison against tx_time_get here is in threadx_time_get_set_test, where the clock is read on the line after it is set: that window is a handful of instructions against a ten millisecond tick, and a range there would remove the only thing the check asserts. Verified in default_build_coverage: both pass, and with the timer's reschedule period changed from one tick to two and the semaphore's requested timeout from 33 ticks to 20, they report ERROR #9 and ERROR #7 and exit 1. Assisted-by: Claude Code (Opus 5)

Release ThreadX regression system

2023-04-04T09:40:54Z