Add control file vars to a handful of tests.

Signed-off-by: Jeremy Orlow <[email protected]>

aborttest/control

@@ -1,11 +1,14 @@
-AUTHOR = "Autotest Team"
+AUTHOR = "Martin Bligh <[email protected]>"
+EXPERIMENTAL = 'True'  # Not really, but this is only for testing autotest...
+                       # not testing _with_ autotest.
 NAME = "Abort test"
 TEST_TYPE = "client"
 TEST_CLASS = "General"
 TEST_CATEGORY = "Functional"
 TIME = "SHORT"
 DOC = """\
-Raise a JobError to simulate a test aborting
+Raise a JobError to simulate a test aborting.  This is for testing Autotest
+itself.
 """
 
 job.run_test('aborttest')

aio_dio_bugs/control

@@ -1,5 +1,5 @@
 NAME = "aio dio bugs"
-AUTHOR = "Autotest Team"
+AUTHOR = "Rafal Wijata <[email protected]>"
 TEST_TYPE = "client"
 TEST_CLASS = "Kernel"
 TEST_CATEGORY = "Functional"

aiostress/control

@@ -1,4 +1,4 @@
-AUTHOR = "Autotest Team"
+AUTHOR = "Masoud S <[email protected]>"
 NAME = "aio stress"
 TEST_CATEGORY = "Stress"
 TEST_CLASS = "Kernel"
@@ -16,4 +16,5 @@ to reads
 
 io buffers are aligned in case you want to do raw io
 """
+
 job.run_test('aiostress')

barriertest/control

@@ -1,9 +1,14 @@
-AUTHOR = "Autotest Team"
+AUTHOR = "Colby Ranger <[email protected]>"
+EXPERIMENTAL = 'True'  # This isn't actually experimental, but it only tests
+                       # autotest itself.
 TIME = "MEDIUM"
 NAME = "Barrier Test"
 TEST_TYPE = "client"
 TEST_CATEGORY = "Functional"
 TEST_CLASS = "Stress"
 DOC = """\
-Stub information needs to be updated!
+This tests barriers which can be used for multiple threads/processes/hosts
+to coordinate within a test.  This is for testing Autotest itself.
 """
+
+job.run_test('barriertest')

bash_shared_mapping/control

@@ -1 +1,12 @@
+AUTHOR = "Martin Bligh <[email protected]>"
+EXPERIMENTAL = 'True'  # Change if you use this and it works.  :-)
+NAME = "bash shared mapping"
+TIME = "SHORT"
+TEST_CLASS = "Kernel"
+TEST_CATEGORY = "Functional"
+TEST_TYPE = "client"
+DOC = """\
+Who knows...
+"""
+
 job.run_test('bash_shared_mapping')

bonnie/control

@@ -1 +1,15 @@
+AUTHOR = "Martin Bligh <[email protected]>"
+NAME = "bonnie"
+TIME = "MEDIUM"
+TEST_CLASS = "Kernel"
+TEST_CATEGORY = "Functional"
+TEST_TYPE = "client"
+DOC = """\
+Bonnie is a benchmark which measures the performance of Unix file system
+operations. Bonnie is concerned with identifying bottlenecks; the name is a
+tribute to Bonnie Raitt, who knows how to use one.
+
+For more info, see http://www.textuality.com/bonnie/
+"""
+
 job.run_test('bonnie')

btreplay/control

@@ -1 +1,20 @@
+AUTHOR = "Joshua Root <[email protected]>"
+EXPERIMENTAL = 'True'  # Change if you use this and it works.  :-)
+NAME = "btreplay"
+TIME = "short"
+TEST_CLASS = "Kernel"
+TEST_CATEGORY = "Functional"
+TEST_TYPE = "client"
+DOC = """\
+Here's a test that takes a trace produced by blktrace, and uses btreplay
+to replay it against a device. Output consists of wall clock time,
+system time, and average request completion latency.
+
+A spare device or partition is required for the test to trash. If this
+is unacceptable, it can easily be changed to be read-only by default.
+
+The trick, of course, will be choosing one or more traces that are
+generally "interesting enough" to include.
+"""
+
 job.run_test('btreplay')