procps/testsuite
Craig Small 898e3cc3cf testsuite: fix ps signals test
On some setups the signals count can change and be truncated. You
will notice this because the number will have "<" prepended. The
testsuite didn't handle this.
You could either get:
         BLOCKED          BLOCKED          BLOCKED           CAUGHT
CAUGHT          CATCHED
0000000000000000 0000000000000000 0000000000000000 00000001f3d1fef9 00000001f3d1fef9 00000001f3d1fef9

or
  BLOCKED   BLOCKED   BLOCKED    CAUGHT    CAUGHT   CATCHED
 00000000  00000000  00000000 <f3d1fef9 <f3d1fef9 <f3d1fef9
2015-06-14 15:20:48 +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 skip kill test too if running runtest 2013-05-26 07:25:55 +10:00
lib.test
pgrep.test Create test process 2015-06-13 15:04:31 +10:00
pkill.test Create test process 2015-06-13 15:04:31 +10: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
vmstat.test Skip tests where /proc/vmstat unreadable 2015-06-13 15:13:39 +10:00
w.test
.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.