summaryrefslogtreecommitdiff
path: root/testsuite/pkill.test
Commit message (Collapse)AuthorAgeFilesLines
* testsuite: Remove trailing whitespaceCraig Small2023-01-251-2/+2
|
* build-sys: Update tests to new binary locationsCraig Small2022-08-291-2/+2
|
* build-sys: Enable testing of sigqueueCraig Small2020-05-111-1/+16
| | | | | | | | | | | | | | | 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 7d55409b82602dac540c011000c9c5abedb5158a commit 2b804a532a90a98bccc5255a728da9076a5e4f4f
* testsuite: check for trailing garbage in pkillCraig Small2015-10-141-0/+4
| | | | | | | | | Previous commit fixed pkill for trailing garbage on pkill signal when it was an integer. This check now ensures that pkill complains about it. References: commit a3975a9c6098218decf2d79b01c7a70512eded9e
* Create test processCraig Small2015-06-131-96/+0
| | | | | | | | | For the test suite, procps used to use sleep which would just create a process or two to test the tools against. Some setups coreutils creates all programs including sleep into one blob which means a lot of the tests fail, see issue #2 procps has its own sleep program now.
* Fix some sched and tty testsCraig Small2015-05-091-2/+1
| | | | | | | | The ps sched test has been disabled. There are too many odd build farms this fails in strange ways. Other odd build farms have no tty and so some tests check for no tty and skip if not found.
* Reliably kill test processesCraig Small2014-07-011-9/+1
| | | | | | | | | | | | | | | It seems command -v also includes built-ins so checking for kill is useless because it finds the built-in and those machines or environments that have no /bin/kill fail at the check stage. Oh and then TCL exec doesn't spawn a shell. After reading way too many TCL websites, I believe this should fix the problem. TCL quoting is... different to say the least but it works reliably here. The script now even picked up a typo elsewhere which was nice. This change should stop the intermittent FTBFS bugs from the Debian pbuilders, I hope! You'd think kill $var wouldn't be this difficult.
* Skip some tests if kill cannot be foundCraig Small2013-10-091-6/+12
| | | | | | | | | | Some Debian pbuilders error out on some of the tests because they cannot find kill to kill the test processes. Now if we cannot find kill we skip those lot of tests. Still need to work out why the S390 doesn't like test_sched References: http://bugs.debian.org/725743
* Run pgrep and pkill tests whithout host psGilles Espinasse2012-06-281-1/+2
| | | | | | | When ps is not available (like it may happen in a chroot), pgrep.exp and pkill.exp tests fail. Use just build ps instead. Signed-off-by: Gilles Espinasse <g.esp@free.fr>
* tests: add pkill test to catch signal option order regressionsSami Kerola2012-06-241-0/+4
| | | | Signed-off-by: Sami Kerola <kerolasa@iki.fi>
* tests: enable basic pkill testSami Kerola2012-06-241-14/+13
| | | | Signed-off-by: Sami Kerola <kerolasa@iki.fi>
* Updated testsuite files for new NLS outputCraig Small2012-01-021-1/+1
|
* More testing added for procpsCraig Small2011-11-301-0/+127