<feed xmlns='http://www.w3.org/2005/Atom'>
<title>threadx.git/test/tx/regression/threadx_thread_delayed_suspension_test.c, branch v6.4.1_cert</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/threadx.git/atom/test/tx/regression/threadx_thread_delayed_suspension_test.c?h=v6.4.1_cert</id>
<link rel='self' href='http://cgit.235523.xyz/threadx.git/atom/test/tx/regression/threadx_thread_delayed_suspension_test.c?h=v6.4.1_cert'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/threadx.git/'/>
<updated>2026-09-15T15:05:26Z</updated>
<entry>
<title>Restored the missing licence headers on the ThreadX regression tests</title>
<updated>2026-09-15T15:05:26Z</updated>
<author>
<name>Frédéric Desbiens</name>
<email>frederic.desbiens@eclipse-foundation.org</email>
</author>
<published>2026-09-15T15:05:26Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/threadx.git/commit/?id=7efc2a8c992b91bf466904f8cb098137157a2e29'/>
<id>urn:sha1:7efc2a8c992b91bf466904f8cb098137157a2e29</id>
<content type='text'>
96 of the 98 files in test/tx/regression carry no copyright notice and no
licence text at all. The two that do are a generated file and one added this
week. 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 header added here is byte identical to the one in common/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 current year contributor line and its own attribution at that point,
which is when there is something to attribute.

Verified: all six build configurations build clean and pass 96 of 96, and the
merged coverage is unmoved.

Two places with the same gap are left alone. test/tx/cmake/samples/fake.c is a
build stub rather than a test. The SMP regression tree has it too and should be
fixed the same way, but not in a commit whose subject says ThreadX.

Assisted-by: Claude Code (Opus 5) &lt;noreply@anthropic.com&gt;
</content>
</entry>
<entry>
<title>Bounded threadx_thread_delayed_suspension_test's wait for its race window</title>
<updated>2026-09-15T12:36:45Z</updated>
<author>
<name>Frédéric Desbiens</name>
<email>frederic.desbiens@eclipse-foundation.org</email>
</author>
<published>2026-09-15T12:36:45Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/threadx.git/commit/?id=a565d7f54a03dea884da1b803ec26e631f0e59ff'/>
<id>urn:sha1:a565d7f54a03dea884da1b803ec26e631f0e59ff</id>
<content type='text'>
The test waits for an interrupt to land while thread 2 is part way through
suspending, and waits for it with no bound. It is the same construction as
threadx_thread_wait_abort_and_isr_test, one scale smaller.

Measured across the five configurations on this branch it ranges from 0.31 to
7.72 seconds, a 25x spread, against 1.84 on the CI runner. That is the largest
ratio in the whole monoprocessor suite, and every other test outside these two
is reproducible to within about half a per cent. The absolute worst case is
small today, so nothing has failed because of it; the shape is what is being
fixed, not an observed failure.

Backported from upstream. A wall clock budget for the same reason as the last
one: a tick is delivered only when the port's timer thread runs, so the tick
clock falls behind real time under exactly the load and instrumentation that
make the wait long.

The check after the loop needed care the other one did not. It compares
thread_2_counter against thread_2_counter_capture, and the capture is taken
inside the interrupt handler at the moment the window is hit, so leaving it in
place after a run that never reached the window would compare a live counter
against the zero it was initialised to and report a defect that is not there.
The check is skipped when the window was not reached and the run says so.

The hunks are byte identical to upstream's, monoprocessor copy only, for the
reason given in the previous commit.

Verified both ways: the window is reached as it always was and the test passes,
and with the budget forced to zero the test reports the window not reached and
passes without the dependent check firing.

Assisted-by: Claude Code (Opus 5) &lt;noreply@anthropic.com&gt;
</content>
</entry>
<entry>
<title>Release ThreadX regression system</title>
<updated>2023-04-04T09:40:54Z</updated>
<author>
<name>Tiejun Zhou</name>
<email>tizho@microsoft.com</email>
</author>
<published>2023-04-03T07:24:52Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/threadx.git/commit/?id=ebeb02b95828ca100c3f24de5f9603a41049f8ff'/>
<id>urn:sha1:ebeb02b95828ca100c3f24de5f9603a41049f8ff</id>
<content type='text'>
</content>
</entry>
</feed>
