procps/testsuite
Craig Small a7aaeaef65 sysctl: print dotted keys again
When the globbing update was put into sysctl, you could no longer
simply use the keys because one key could potentially be
multiple paths once the glob expansion occured.  Using the path
instead gave a unique output.

Except certain programs, such as salt, expected the output to use
the dotted path "kernel.hostname" and not "kernel/hostname".

We can no longer use the original key, so now for each path:
  Copy the path
  strip off /proc/
  convert all / to .

The sysctl testsuite was also updated to check for a few different
types of conversion failures.

References:
 commit 6389deca5b
 https://www.freelists.org/post/procps/some-procpsn4400-fixes,4
 https://repo.saltproject.io/

Signed-off-by: Craig Small <csmall@dropbear.xyz>
2022-04-09 14:33:34 +10:00
..
config sysctl: Support systemd glob patterns 2021-09-13 22:07:37 +10:00
free.test
kill.test build-sys: Enable testing of sigqueue 2020-04-28 19:47:39 +10:00
lib.test
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 ps: Add NEWS and test for exe output 2020-12-22 15:31:39 +11:00
pwait.test build-sys: Make pwait test dependent on pwait built 2020-12-22 15:21:39 +11:00
pwdx.test
slabtop.test
sysctl.test sysctl: print dotted keys again 2022-04-09 14:33:34 +10:00
uptime.test
vmstat.test
w.test
.gitignore
Makefile.am
README
sysctl_glob_test.conf sysctl: Support systemd glob patterns 2021-09-13 22:07:37 +10:00
sysctl_slash_test.conf sysctl: print dotted keys again 2022-04-09 14:33:34 +10:00

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.