procps/testsuite
Craig Small 6eb4726e6f testsuite: kill test fails on signal names
Some archs have + and - in their signal names, such as hppa
which comes with signals such as RTMIN+-9 RTMIN+-8
The kill -l test failed because of this, we now accept these
odd names.

References:
 https://bugs.debian.org/762764
 https://buildd.debian.org/status/fetch.php?pkg=procps&arch=hppa&ver=1%3A3.3.10-1&stamp=1411601407
2016-04-11 22:12:58 +10:00
..
config Do not link test process to libprocps 2015-06-14 08:54:59 +10:00
free.test free: Use IEC units 2015-04-03 19:18:58 +11:00
kill.test testsuite: kill test fails on signal names 2016-04-11 22:12:58 +10:00
lib.test lib: add fileutils file with stream error checking facility 2012-03-23 15:57:41 +01:00
pgrep.test Create test process 2015-06-13 15:04:31 +10:00
pkill.test testsuite: check for trailing garbage in pkill 2015-10-14 21:31:56 +11:00
pmap.test Update help files 2014-02-02 18:13:01 +11:00
ps.test testsuite: fix ps signals test 2015-06-14 15:20:48 +10:00
pwdx.test Create test process 2015-06-13 15:04:31 +10:00
slabtop.test
sysctl.test
uptime.test test for previous commit 2012-12-26 23:21:44 +11:00
vmstat.test Skip tests where /proc/vmstat unreadable 2015-06-13 15:13:39 +10:00
w.test Fix w tests when no user is logged in 2012-05-08 22:51:19 +10:00
.gitignore
Makefile.am procps-ng testsuite : simplify DEJAGNU workaround 2013-05-26 07:32:02 +10:00
README

How to use check suite
----------------------

You need DejaGNU package.  Assuming you have it all you need to do is

make check


Something failed now what
-------------------------

First determine what did not work.  If only one check failed you can
run it individually in debugging mode.  For example

runtest -a -de -v w.test/w.exp
Expect binary is /usr/bin/expect
Using /usr/share/dejagnu/runtest.exp as main test driver
[...]

Do not bother capturing screen output, it is in testrun.log which
test suite generated.

$ ls  testrun.* dbg.log
dbg.log  testrun.log  testrun.sum

The reason why test failed should be in dbg.log.  Assuming you
figured out the reason you could write a patch fixing w.test/w.exp
and send it to upstream.

If you do not know how, or have time, to fix the issue create tar.gz
file containing test run logs and submit it to upstream maintainers.
Notice that in later case upstream sometimes has to ask clarifying
questions about environment where problem occurred.