procps/testsuite
Craig Small 4090fa711b build-sys: Enable testing of sigqueue
The referenced commits enavled both pkill and kill to send an integer to
the killed or signalled process. The test_process now will report on the
integer if sent and the testsuite changes take advantage of this
new feature.

Another process make/destroy set had to be made as using spawn
instead of exec changes both the SID and TTY for the underlying
process, making other tests fail.

References:
 commit 7d55409b82
 commit 2b804a532a
2020-04-28 19:47:39 +10:00
..
config build-sys: Enable testing of sigqueue 2020-04-28 19:47:39 +10:00
free.test free: Update tests and fix for previous patch 2018-01-13 16:09:54 +11:00
kill.test build-sys: Enable testing of sigqueue 2020-04-28 19:47:39 +10:00
lib.test misc: testsuite to source aux scripts correctly 2016-07-10 09:04:44 +10:00
pgrep.test testsuite: pgrep: Provide test for matching a more than 4k command line; beware as TCL does not seem to match on strings >4k 2019-09-21 16:39:13 +10:00
pkill.test build-sys: Enable testing of sigqueue 2020-04-28 19:47:39 +10:00
pmap.test
ps.test misc: fix ps etime tests 2018-04-10 22:09:40 +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 Consolidated patch of previously merged CYGWIN support 2017-09-03 20:59:23 +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.