Skip to content

Commit

Permalink
Fix control file variables for client/tests adding required variables as
Browse files Browse the repository at this point in the history
described in: http://test.kernel.org/autotest/ControlRequirements

Signed-off-by: Scott Zawalski <[email protected]>
  • Loading branch information
Scott Zawalski committed Jul 8, 2008
1 parent 6f8134d commit eee73fb
Show file tree
Hide file tree
Showing 7 changed files with 86 additions and 4 deletions.
20 changes: 20 additions & 0 deletions scrashme/control
Original file line number Diff line number Diff line change
@@ -1 +1,21 @@
NAME='scrashme'
AUTHOR='Yi Yang <[email protected]>'
TEST_CATEGORY='Stress'
TEST_CLASS='Kernel'
TEST_TYPE='client'
EXPERIMENTAL='True'
DEPENDENCIES='GCC'
TIME='MEDIUM'
DOC='''\
Runs the scrashme suite located at:
http://www.codemonkey.org.uk/projects/git-snapshots/scrashme/
o Now tests all syscalls, not just 256
o Certain syscalls made things get out of hand too quickly.
Forkbombing a box with this app kills it very quickly.
(An alternative would be to only run this with strict rlimits, but
there are a few other syscalls we also take care of..)
o Do the syscall in a child process so if something hangs, we can continue.
o Printing of the syscall name/return code.
o Several extra modes of attack.
'''
job.run_test('scrashme')
8 changes: 5 additions & 3 deletions selftest/control
Original file line number Diff line number Diff line change
@@ -1,9 +1,11 @@
AUTHOR = "Autotest Team"
AUTHOR = "Andy Whitcroft <[email protected]>"
EXPERIMENTAL = "True"
TIME = "MEDIUM"
NAME = "Self Test"
TEST_TYPE = "client"
TEST_CATEGORY = "Functional"
TEST_CLASS = "Stress"
TEST_CLASS = "Software"
DOC = """\
Stub information needs to be updated!
Run a selftest on the autotest installed branch
"""
job.run_test('selftest', 1)
2 changes: 1 addition & 1 deletion selftest/selftest.py
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
import os
import os, sys
from autotest_lib.client.bin import test
from autotest_lib.client.common_lib import error

Expand Down
11 changes: 11 additions & 0 deletions signaltest/control
Original file line number Diff line number Diff line change
@@ -1 +1,12 @@
NAME='Signal Test'
EXPERIMENTAL = "True"
AUTHOR='Michal Piotrowski <[email protected]>'
TIME='SHORT'
TEST_TYPE='client'
TEST_CLASS='Kernel'
TEST_CATEGORY='Functional'
DEPENDENCIES='GCC'
DOC='''\
Test signal passing to processes
'''
job.run_test('signaltest')
22 changes: 22 additions & 0 deletions sparse/control
Original file line number Diff line number Diff line change
@@ -1,2 +1,24 @@
NAME='Sparse Kernel Test'
EXPERIMENTAL='True'
TIME='MEDIUM'
TEST_TYPE='client'
TEST_CATEGORY='Functional'
TEST_CLASS='Kernel'
DEPENDENCIES='GCC'
AUTHOR='Martin Bligh <[email protected]>'
DOC='''\
Sparse is a semantic parser of source files: it's neither a compiler
(although it could be used as a front-end for one) nor is it a
preprocessor (although it contains as a part of it a preprocessing
phase).

It is meant to be a small - and simple - library. Scanty and meager,
and partly because of that easy to use. It has one mission in life:
create a semantic parse tree for some arbitrary user for further
analysis. It's not a tokenizer, nor is it some generic context-free
parser. In fact, context (semantics) is what it's all about - figuring
out not just what the grouping of tokens are, but what the _types_ are
that the grouping implies.
'''
job.run_test('sparse', '/usr/local/src/linux-2.6.14.tar.bz2', '/usr/local/src/patch-2.6.14-git6.bz2', 'http://ftp.kernel.org/pub/linux/kernel/people/mbligh/config/config.up')

16 changes: 16 additions & 0 deletions spew/control
Original file line number Diff line number Diff line change
@@ -1 +1,17 @@
NAME='Spew'
AUTHOR='Martin Bligh <[email protected]>'
EXPERIMENTAL='True'
TEST_TYPE='client'
DEPENDENCIES='GCC'
TEST_CATEGORY='Benchmark'
TEST_CLASS='Hardware'
TIME='MEDIUM'
DOC='''\
The spew package is used to test I/O performance and to generate load
on character devices, block devices, and file systems. It is similar
to the lmdd program found in the lmbench test-suite
(http://www.bitmover.com/lmbench). It is a bit easier to use than lmdd
and has some added functionality. For example, it can test both
random and sequential I/O.
'''
job.run_test('spew')
11 changes: 11 additions & 0 deletions stress/control
Original file line number Diff line number Diff line change
@@ -1 +1,12 @@
NAME='Stress'
AUTHOR='Yi Yang <[email protected]>'
EXPERIMENTAL='True'
TEST_TYPE='client'
TIME='MEDIUM'
TEST_CATEGORY='Functional'
DEPENDENCIES='GCC'
TEST_CLASS='Software'
DOC='''\
stress is not a benchmark, but is rather a tool designed to put given subsytems under a specified load. Instances in which this is useful include those in which a system administrator wishes to perform tuning activities, a kernel or libc programmer wishes to evaluate denial of service possibilities, etc.
'''
job.run_test('stress')

0 comments on commit eee73fb

Please sign in to comment.