/
githubmirror
/
procps
ОбзорДокументацияВойти
/
githubmirror
/
procps
Код
Запросы
0
Пакеты
0
Релизы
0
Аналитика
Безопасность
ДокументацияПоддержка
Политика конфиденциальностиПользовательское соглашениеПолитика использования «cookies»Согласие субъекта персональных данных
2026 ©
procps/
testsuite/
..
config

testsuite/test_shm: make the address of shmem available to test cases

5 месяцев назад
free.test

free: Show single line statistics

3 года назад
hugetop.test

misc: eliminated even more useless trailing whitespace

год назад
kill.test

build-sys: Update tests to new binary locations

4 года назад
lib.test

testsuite: Update the library tests for new location

4 года назад
pgrep.test

pgrep: Don't treat empty list as 0

2 месяца назад
pkill.test

testsuite: Remove trailing whitespace

4 года назад
pmap.test

testsuite: Fix pmap for alpha

месяц назад
ps.test

ps: Fix table option handling and -ad

9 месяцев назад
pwait.test

pgrep: Support matching on the presence of a userspace signal handler

4 года назад
pwdx.test

build-sys: Update tests to new binary locations

4 года назад
skill.test

skill: Restore the -p flag functionality

4 года назад
slabtop.test

testsuite: Fix slabtop tests

год назад
sysctl.test

testsuite: Remove sysctl hangs

5 месяцев назад
uptime.test

uptime: add raw option

3 года назад
vmstat.test

vmstat: Print guest time

3 года назад
w.test

w: Do not crash with -pt

7 месяцев назад
.gitignore

ps: Zombies get <defunct> on command name again

2 года назад
Makefile.am

testsuite: only test hugetop if we built it

год назад
README

docs: add testsuite readme file

14 лет назад
sysctl_glob_test.conf

sysctl: Add support for systemd glob excludes

3 года назад
sysctl_slash_test.conf

sysctl: print dotted keys again

4 года назад
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.