commit | c1e74d6fe68f0b3c23ed9ba8f9d36e43523c23d8 | [log] [tgz] |
---|---|---|
author | Sandeep Patil <sspatil@google.com> | Tue Jan 23 14:38:44 2018 -0800 |
committer | Sandeep Patil <sspatil@google.com> | Tue Jan 23 16:31:52 2018 -0800 |
tree | b7906affc10956071b0993e9dd5333d798d60c55 | |
parent | 499bb2df2aecbc8b6931e35b9e338ff84028a94d [diff] | |
parent | 731cd34e682d297b207668be8b1d15320a9ac1b1 [diff] |
Upgrade to LTP 20180118 A short log of commits merged as part of this is available in Merge list Bug: 72110041 No new disabled tests due to failure to build. New configuration(s) added in android/include/config.h: HAVE_ATOMIC_MEMORY_MODEL HAVE_BUILTIN_CLEAR_CACHE HAVE_LIBCRYPTO HAVE_LINUX_IF_ETHER_H HAVE_LINUX_IF_PACKET_H HAVE_PROFIL HAVE_STRUCT_TPACKET_REQ3 No new test suites were added in this release Tests Diff: Deleted Added --------------------------------------------------------- syscalls.setrlimit04 syscalls.setrlimit05 syscalls.keyctl06 syscalls.add_key03 syscalls.add_key04 syscalls.fallocate05 syscalls.keyctl08 syscalls.setsockopt02 syscalls.ioctl07 syscalls.keyctl07 syscalls.sigwaitinfo01 syscalls.ptrace07 syscalls.request_key03 fs.fs_fill commands.unshare01 Change-Id: Ieb8ec5291b7b4ec57e63fe6adda334eadb07c961 Signed-off-by: Sandeep Patil <sspatil@google.com>
Linux Test Project is a joint project started by SGI, OSDL and Bull developed and maintained by IBM, Cisco, Fujitsu, SUSE, Red Hat, Oracle and others. The project goal is to deliver tests to the open source community that validate the reliability, robustness, and stability of Linux.
The LTP testsuite contains a collection of tools for testing the Linux kernel and related features. Our goal is to improve the Linux kernel and system libraries by bringing test automation to the testing effort. Interested open source contributors are encouraged to join.
Project pages are located at: http://linux-test-project.github.io/
The latest image is always available at: https://github.com/linux-test-project/ltp/releases
The discussion about the project happens at ltp mailing list: http://lists.linux.it/listinfo/ltp
The git repository is located at GitHub at: https://github.com/linux-test-project/ltp
Be careful with these tests!
Don't run them on production systems. Growfiles, doio, and iogen in particular stress the I/O capabilities of systems and while they should not cause problems on properly functioning systems, they are intended to find (or cause) problems.
If you have git, autoconf, automake, m4, the linux headers and the common developer packages installed, the chances are the following will work.
$ git clone https://github.com/linux-test-project/ltp.git $ cd ltp $ make autotools $ ./configure $ make $ make install
This will install LTP to /opt/ltp
.
doc/mini-howto-building-ltp-from-git.txt
.INSTALL
and ./configure --help
.Some tests will be disabled if the configure script can not find their build dependencies.
TCONF
due to a missing component, check the ./configure
output.INSTALL
.To run all the test suites
$ cd /opt/ltp $ ./runltp
Note that many test cases have to be executed as root.
To run a particular test suite
$ ./runltp -f syscalls
To run all tests with madvise
in the name
$ ./runltp -f syscalls -s madvise
Also see
$ ./runltp --help
Test suites (e.g. syscalls) are defined in the runtest directory. Each file contains a list of test cases in a simple format, see doc/ltp-run-files.txt.
Each test case has its own executable or script, these can be executed directly
$ testcases/bin/abort01
Some have arguments
$ testcases/bin/fork13 -i 37
The vast majority of test cases accept the -h (help) switch
$ testcases/bin/ioctl01 -h
Many require certain environment variables to be set
$ LTPROOT=/opt/ltp PATH="$PATH:$LTPROOT/testcases/bin" testcases/bin/wc01.sh
Most commonly, the path variable needs to be set and also LTPROOT
, but there are a number of other variables, runltp
usually sets these for you.
Note that all shell scripts need the PATH
to be set. However this is not limited to shell scripts, many C based tests need environment variables as well.
Before you start you should read following documents:
doc/test-writing-guidelines.txt
doc/build-system-guide.txt
There is also a step-by-step tutorial:
doc/c-test-tutorial-simple.txt
If something is not covered there don't hesitate to ask on the LTP mailing list. Also note that these documents are available online at:
https://github.com/linux-test-project/ltp/wiki/Test-Writing-Guidelines https://github.com/linux-test-project/ltp/wiki/BuildSystem https://github.com/linux-test-project/ltp/wiki/C-Test-Case-Tutorial