| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Update #3938.
|
|
|
|
|
|
|
| |
- The archive command lists archives, symbols and any duplicate
symbols.
- Change the RTL shell commands to the rtems_printer to allow
the output to be captured.
|
|
|
|
|
| |
- Add a small memory test config file.
- Update the small memory PowerPC BSPs to use the new test config.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
errors.
- Add a top level test configuration file for test states that are common
to all BSPs. This saves adding a test configuration (tcfg) file for
every BSP.
- Add the test states 'user-input' and 'benchmark'. This
lets 'rtems-test' stop the test rather than waiting for a timeout or
letting a benchmark run without the user asking for it to run.
- Implement rtems-test-check in Python to make it faster. The shell script
had grown to a point it was noticably slowing the build down.
- Fix the configure.ac and Makefile.am files for a number of the
test directories. The files are difficiult to keep in sync with the
number of tests and mistakes can happen such as tests being left
out of the build. The test fsrofs01 is an example. Also a there was
a mix of SUBDIRS and _SUBDIRS being used and only _SUBDIRS should be
used.
- Fix the test fsrofs01 so it compiles.
Closes #2963.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Change the testsuite configuration files to hold state information about
a test. The states are:
exclude - Do not build the test
expected-fail - The test is expected to fail
indeterminate - The test may pass or may fail
A message is printed just after the test's BEGIN message to indicate
there is a special state for the test. No state message means the test
is expected to pass.
This support requires tests are correctly written to the use standard
support to begin and end a test.
|
| |
|
|
|
|
|
|
| |
This file contains the list of interrupt critical section tests.
There are some simulators these are unreliable on so they should
just be ignored.
|
| |
|
| |
|
|
BSPs for simulators which do not include a clock tick interrupt source
are incapable of running some tests successfully. This is a common
characteristic of some BSPs and a fixed set of tests. There is no point
in duplicating this list of tests in those BSPs test configuration.
Read testsuites/testdata/require-tick-isr.tcfg for details.
|