Extend the status logging mechanism to handled multiple tests in
parallel on a single machine without interleaving the status logs from
each test. This introduces some delay into the processing of these
logs since the status logging has to delay writing out the status
logs until it can impose a serial order on them.
However, it does NOT delay the writing of the logs to stdout; since
stdout is intended for human consumption and not machine processing it
is much more convenient for the logging to be visible in the logs at
the point in time where the event occured.
This implementation tries to avoid introducing a sitation where logs
are dropped on the floor because their being held back from the status
log. In the worst case on the client side the logs if autotest fails
before accumulating the logs in status then the intermediate logs will
still be available in individual status.* files, and on the server side
the server will automatically write out whatever logs it has
accumulated so far in the case of a failure (under the assumption that
it is still possible to write to status.log).
Signed-off-by: John Admanski <jadmanski@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@1089 592f7852-d20e-0410-864c-8624ca9c26a4
diff --git a/client/bin/harness.py b/client/bin/harness.py
index 22ddd4c..0d0180e 100755
--- a/client/bin/harness.py
+++ b/client/bin/harness.py
@@ -65,12 +65,12 @@
pass
- def test_status(self, status):
+ def test_status(self, status, tag):
"""A test within this job is completing"""
pass
- def test_status_detail(self, code, subdir, operation, status):
+ def test_status_detail(self, code, subdir, operation, status, tag):
"""A test within this job is completing (detail)"""
pass