e981f2bbd2
Right now the test case is both testing it (expect_pass "$test") and marking it as untested (untested "$test"), it should do either one or the other, so stop marking it as untested. Before this change, these lines appear in testsuite/ps.log or the output of `make check RUNTESTFLAGS="--all"`: PASS: ps SCHED_BATCH scheduler UNTESTED: ps SCHED_BATCH scheduler Note that the second line is confusing, it's implying that the test is untested, right after having tested it and indicated it passes. After this change, only the first line will appear. Tested that both `make check` and `make distcheck` continue working with this commit. Signed-off-by: Filipe Brandenburger <filbranden@google.com> Signed-off-by: Craig Small <csmall@enc.com.au> |
||
---|---|---|
.. | ||
config | ||
free.test | ||
kill.test | ||
lib.test | ||
pgrep.test | ||
pkill.test | ||
pmap.test | ||
ps.test | ||
pwdx.test | ||
slabtop.test | ||
sysctl.test | ||
uptime.test | ||
vmstat.test | ||
w.test | ||
.gitignore | ||
Makefile.am | ||
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.