This patch increases the timeout for the start barrier.
It used to be 30 seconds. When executing the netperf test on two machines of different specs, the most powerful one would have the time to finish compiling and timeout on the barrier while the other was still compiling. 600 seconds should leave ample tolerance at the cost of a longer wait if there is indeed something that goes wrong.
From: Benjamin Poirier <poirier@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@612 592f7852-d20e-0410-864c-8624ca9c26a4
diff --git a/client/tests/netperf2/netperf2.py b/client/tests/netperf2/netperf2.py
index 52e4129..ea4c8c7 100755
--- a/client/tests/netperf2/netperf2.py
+++ b/client/tests/netperf2/netperf2.py
@@ -29,14 +29,14 @@
self.server_start()
try:
job.barrier(server_tag, 'start',
- 30).rendevous(*all)
+ 600).rendevous(*all)
job.barrier(server_tag, 'stop',
3600).rendevous(*all)
finally:
self.server_stop()
elif (role == 'client'):
os.environ['NETPERF_CMD'] = self.client_path
- job.barrier(client_tag, 'start', 30).rendevous(*all)
+ job.barrier(client_tag, 'start', 600).rendevous(*all)
self.client(script, server_ip, args)
job.barrier(client_tag, 'stop', 30).rendevous(*all)
else: