Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / ltp / 0499d20bbae56d98f9be4ef9717384486bcdf71e
commit0499d20bbae56d98f9be4ef9717384486bcdf71e[log] [tgz]
authorSteve Muckle <smuckle@google.com>Fri Jan 25 17:17:56 2019 -0800
committerSteve Muckle <smuckle@google.com>Fri Feb 01 15:32:21 2019 -0800
tree4eb19233e4f23449374c6807f900f7df449d521c
parente99c01e405b71cc34d2c38c08e155153ae7cf110 [diff]
ANDROID: enable syscalls.vhangup tests

These tests have been fixed upstream to work on Android.

Bug: 112484150
Test: run vts-kernel -m VtsKernelLtpStaging
Change-Id: Ib6bc085ea5c4205bd60d06faa30efd403014be4e
Signed-off-by: Steve Muckle <smuckle@google.com>
3 files changed
tree: 4eb19233e4f23449374c6807f900f7df449d521c
  1. android/
  2. doc/
  3. include/
  4. lib/
  5. m4/
  6. pan/
  7. runtest/
  8. scenario_groups/
  9. scripts/
  10. testcases/
  11. testscripts/
  12. tools/
  13. travis/
  14. utils/
  15. .gitignore
  16. .travis.yml
  17. Android.bp
  18. Android.mk
  19. build.sh
  20. configure.ac
  21. COPYING
  22. execltp.in
  23. gen.bp
  24. IDcheck.sh
  25. INSTALL
  26. ltpmenu
  27. Makefile
  28. Makefile.release
  29. MODULE_LICENSE_GPL
  30. NOTICE
  31. OWNERS
  32. README.kernel_config
  33. README.md
  34. runltp
  35. TODO
  36. ver_linux
  37. VERSION
README.md

Linux Test Project

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

The patchwork instance is at: https://patchwork.ozlabs.org/project/ltp/list/

Warning!

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.

Quick guide to running the tests

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

Now you can continue either with compiling and running a single test or with compiling and installing the whole testsuite.

Shortcut to running a single test

If you need to execute a single test you actually does not need to compile whole LTP, if you want to run a syscall testcase following should work.

$ cd testcases/kernel/syscalls/foo
$ make
$ PATH=$PATH:$PWD ./foo01

Shell testcases are a bit more complicated since these need a path to a shell library as well as to compiled binary helpers, but generally following should work.

$ cd testcases/lib
$ make
$ cd ../commands/foo
$ PATH=$PATH:$PWD:$PWD/../../lib/ ./foo01.sh

Open Posix Testsuite has it's own build system which needs Makefiles to be generated first, then compilation should work in subdirectories as well.

$ cd testcases/open_posix_testsuite/
$ make generate-makefiles
$ cd conformance/interfaces/foo
$ make
$ ./foo_1-1.run-test

Compiling and installing all testcases

$ make
$ make install

This will install LTP to /opt/ltp.

  • If you have a problem see doc/mini-howto-building-ltp-from-git.txt.
  • If you still have a problem see INSTALL and ./configure --help.
  • Failing that, ask for help on the mailing list or Github.

Some tests will be disabled if the configure script can not find their build dependencies.

  • If a test returns TCONF due to a missing component, check the ./configure output.
  • If a tests fails due to a missing user or group, see the Quick Start section of 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.

Developers corner

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:

Although we accept GitHub pull requests, the preferred way is sending patches to our mailing list.