| Commit message (Collapse) | Author | Files | Lines |
|
The test source code is generated from specification items
by the "./spec2modules.py" script contained in the
git://git.rtems.org/rtems-central.git Git repository.
Please read the "How-To" section in the "Software Requirements Engineering"
chapter of the RTEMS Software Engineering manual to get more information about
the process.
Update #3716.
|
|
In the action requirements, some pre-conditions are not applicable
depending on the state of other pre-conditions. There is no particular
order in the pre-conditions, so we have to check the N/A status
individually.
|
|
Since there are already excessive NULL pointer checks in the Classic
API, do this also in rtems_task_construct().
Update #3959.
|
|
Use a common wording for the tests. Use the new templates for action
requirements described in the RTEMS Software Engineering manual.
|
|
Run the task create/construct tests also on validation test suite 1
which has exactly one processor configured.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Close the thread object if a thread create extension fails. Also call
the delete extension to avoid resource leaks in early extensions if a
late extension fails.
Close #4270.
|
|
Unify the state names across tests and make sure the state names have a
similar length.
|
|
|
|
|
|
|
|
Check the name followed by the id check in all create directives.
Compare pointers against NULL. Fix formatting.
|
|
This is the first test case generated from a specification item in the
rtems-central repository.
Update #3959.
|