liblitmus.git/tests/fdso.c, branch 2012.1 [ARCHIVE] The userspace library for LITMUS^RT 2010. Now on GitHub. add test cases for the FMLP and SRP under GSN- and PSN-EDF 2011-02-03T22:40:16+00:00 Bjoern B. Brandenburg bbb@cs.unc.edu 2011-01-30T00:16:24+00:00 5ec8a4d481017390da5ae4de027e937bc04c21ec 






switch to generic locking system calls
2011-02-03T22:40:16+00:00

Bjoern B. Brandenburg
bbb@cs.unc.edu

2011-01-29T19:53:21+00:00

c4128b99e1206d03d15c5d2e1b6af164bf261c40

The new generic lock layer in LITMUS^RT does away with per-protocol
system calls. Change accordingly.





The new generic lock layer in LITMUS^RT does away with per-protocol
system calls. Change accordingly.







Silence warning due to missing header file.
2010-11-09T21:35:32+00:00

Bjoern B. Brandenburg
bbb@cs.unc.edu

2010-11-06T20:15:46+00:00

b8c51805f5c71d1921ac7315125723b1e175ca5e












Add tests for invalid object types and od_open().
2010-02-26T00:41:14+00:00

Bjoern B. Brandenburg
bbb@cs.unc.edu

2010-02-26T00:41:14+00:00

173c328f23f5c8b3519068f731a6db35488bbd25












Introduce test framework for LITMUS^RT.
2010-02-21T02:48:29+00:00

Bjoern B. Brandenburg
bbb@cs.unc.edu

2010-02-21T02:48:29+00:00

f3d21c128e5b40acd1f15e3ddcd7fd54ca3a9bed

This is the beginning of the LITMUS^RT testsuite.
The main design goals are flexibility and ease of test writing.

To create a new test, simply write a test case in any C file in the
tests/ subdirectory. The buildsystem will find the test and hook it
up with the testrunner.

Have a look at tests/fdso.c and include/tests.h to get an idea for what
tests look like.

Tests can be executed with the 'runtests' tool. Each testcase is executed
in a separate process in order to ensure that tests do not influence
each other.





This is the beginning of the LITMUS^RT testsuite.
The main design goals are flexibility and ease of test writing.

To create a new test, simply write a test case in any C file in the
tests/ subdirectory. The buildsystem will find the test and hook it
up with the testrunner.

Have a look at tests/fdso.c and include/tests.h to get an idea for what
tests look like.

Tests can be executed with the 'runtests' tool. Each testcase is executed
in a separate process in order to ensure that tests do not influence
each other.