forked from Imagelibrary/rtems
258bda306b
- 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.
This directory contains the RTEMS POSIX Timing Test Suite. The tests in this directory are used to measure the execution time of RTEMS directive and some critical internal functions. The results of these test are useful for comparison of RTEMS performance + between versions of RTEMS + between different boards + across different architectures These tests attempt to benchmark RTEMS as the user would. They measure the execution time for a directive (under various circumstances) from the time RTEMS is entered until it is executed. Where possible, the time is the average of at least 100 invocations of the directive. The accuracy of the times reported by these benchmarks is very dependent on the resolution of the timer being used. It is also important to insure that all sources of hardware interrupts are disabled during execution of the tests. This insures that the directive time reported does not include any interrupt time. The file psxtmtests_plan.csv contains the development plan for this test suite. It is a PLAN which indicates which tests are to contain which test cases, the test name, and which template in rtems-testing/rtems-test-templates are to be used for their construction. This is just a plan. There may need to be more test cases for a particular service to effectively measure all interesting non-error use cases.