aa41c309dd
This was supposed to be just a cherry-pick of the referenced commit. However there were two problems: 1. kill code was moved out to its own file 2. strtosig() had a latent bug where signal numbers were not converted to names. Original note: kill -lHUP would work correctly, but kill -l HUP would not. The list option in kill was hit by a quirk of getopt_long where an option with an optional argument would not attempt to get the argument beyond the space, even though a mandatory argument would do that. The fix is a kludge to scan to the next argument and if it looks like something we can use, use it. Lucky for us, the list option is one where parsing can stop immediately. Thanks to Brian Vandenberg for the way forward. References: http://stackoverflow.com/questions/1052746/getopt-does-not-parse-optional-arguments-to-parameters https://bugs.debian.org/854407 commit 537cea324b121f54744369425332c256aa84a181 |
||
|---|---|---|
| .. | ||
| 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.