sched_process_free may not be called during the tracing session if there
is very little activity on the machine the test is run on. We change
this validate to sched_process_fork since we are sure there will be
atleast one generated by the final lttng stop.
Signed-off-by: Francis Deslauriers <francis.deslauri...@efficios.com>
---
tests/regression/kernel/test_event_basic | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/regression/kernel/test_event_basic
b/tests/regression/kernel/test_event_basic
index aeca02b..584bfc8 100755
--- a/tests/regression/kernel/test_event_basic
+++ b/tests/regression/kernel/test_event_basic
@@ -32,14 +32,14 @@ function test_event_basic()
lttng_enable_kernel_event $SESSION_NAME "sched_switch"
lttng_enable_kernel_event $SESSION_NAME "sched_process_exit"
- lttng_enable_kernel_event $SESSION_NAME "sched_process_free"
+ lttng_enable_kernel_event $SESSION_NAME "sched_process_fork"
start_lttng_tracing_ok
stop_lttng_tracing_ok
validate_trace "sched_switch" $TRACE_PATH
validate_trace "sched_process_exit" $TRACE_PATH
- validate_trace "sched_process_free" $TRACE_PATH
+ validate_trace "sched_process_fork" $TRACE_PATH
destroy_lttng_session_ok $SESSION_NAME
--
2.7.4
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
