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

Stopped the thread priority change test leaving core 0 to a finished thread

2026-09-15T00:36:44Z

The SMP suite failed this test in CI on disable_notify_callbacks_build, and it is the same defect upstream diagnosed and fixed on its own branch. The test ends with thread_0.tx_thread_inherit_priority = 0; _tx_thread_smp_simple_priority_change(&thread_0, 16); stating the intent of reaching the branch where the new priority is below the inheritance priority. Zero cannot reach it, because 16 is not less than 0. The other branch runs instead, and that branch records the inheritance priority as the thread's priority while the code after it links the thread into the list for the new priority regardless, so thread 0 came away claiming priority 0 while living in the priority 16 list. Both halves hurt. Priority 0 ties with the control thread, so resuming the control thread raised no preemption and left the execute pointer alone; and completing thread 0 then removed it from a list it was never in, leaving core 0 owned by a completed thread with the control thread ready and unschedulable. The test prints SUCCESS and the process never exits, so ctest kills it at the thousand second timeout, twice, and the log carries nothing past the result line. The inheritance priority is now above the new priority, which is what the branch the comment names actually requires, and is put back to TX_MAX_PRIORITIES afterwards so nothing downstream reasons about an inheritance that is not there. Protection is held across the call, since the routine is internal and expects it and was being called in the open. Assisted-by: Claude Code (Opus 5)

Release ThreadX regression system

2023-04-04T09:40:54Z