f8e98b65ae
Free always used 1024 based units but used the confusing old style kilo,mega etc. This change changes the names to kibi,mebi for 1024 based divisors and kilo,mega for 1000 based divisors or IEC units. It also checks if you try to set two units, e.g free -k -m Petabyte and Pebibyte have been added. If you used to use the long options such as --mega these will now actually print megabytes (they previously printed mebibytes). The short options are being used on the IEC units References: https://www.gitorious.org/procps/procps/merge_requests/38 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.