The testOneEvent() fails spuriously. Either the wrong event is
retrieved from the trace, or the analysis module is somehow not
ready when it should be.
This extra check will allow us to determine which one of those
two causes is the problem.
Refs bug 506868.
Change-Id: Ie6646a734fcf07a21c810d15c708db3a460c8765
Signed-off-by: Alexandre Montplaisir <alexmonthy@efficios.com>
Reviewed-on: https://git.eclipse.org/r/85187
Reviewed-by: Hudson CI
Reviewed-by: Marc-André Laperle <marc-andre.laperle@ericsson.com>
Tested-by: Marc-André Laperle <marc-andre.laperle@ericsson.com>
Reviewed-by: Matthew Khouzam <matthew.khouzam@ericsson.com>
Tested-by: Matthew Khouzam <matthew.khouzam@ericsson.com>
ustEvent = (CtfTmfEvent) TmfTraceUtils.getNextEventMatching(experiment, rank, eventFinder, null);
assertNotNull(ustEvent);
+ /* Make sure the correct event was retrieved */
assertEquals(ustTrace, ustEvent.getTrace());
+ assertEquals(1450193715128075054L, ustEvent.getTimestamp().toNanos());
Integer tidFromKernel = KernelThreadInformationProvider.getThreadOnCpu(module,
ustEvent.getCPU(), ustEvent.getTimestamp().toNanos());