Fix: Add arbitrary wait period for kernel streaming test
authorDavid Goulet <dgoulet@efficios.com>
Wed, 3 Oct 2012 16:29:24 +0000 (12:29 -0400)
committerDavid Goulet <dgoulet@efficios.com>
Wed, 3 Oct 2012 16:29:24 +0000 (12:29 -0400)
commitdf29d3c3f9f97585a3efbe1ffe699ce4cdfa6c46
tree84c922016bc2e541a56c04dcb53eaa02582db5d6
parent7a57cf92a463031c8cb668900f9215e3773a15c3
Fix: Add arbitrary wait period for kernel streaming test

Once the trace has been destroy, there is a race condition between
reading the trace and the trace being completely written on disk.

We don't have anyway of telling if the streamed trace has been completed
so we have to add an arbitrary wait period so the test can successfully
parse and validate the trace.

I never hit that problem until this morning with my Linux 3.6.0 kernel.
Maybe related or not, still the trace can occur on slower systems.

Signed-off-by: David Goulet <dgoulet@efficios.com>
tests/tools/streaming/run-kernel
This page took 0.031266 seconds and 4 git commands to generate.