Bug 506868 - Intermittent failure in UstKernelSyncTest
Summary: Intermittent failure in UstKernelSyncTest
Status: NEW
Alias: None
Product: Tracecompass
Classification: Tools
Component: LTTng (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Project Inbox CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 486207
  Show dependency tree
 
Reported: 2016-11-01 22:50 EDT by Matthew Khouzam CLA
Modified: 2016-11-16 19:45 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matthew Khouzam CLA 2016-11-01 22:50:57 EDT 
19:25:27  java.lang.AssertionError: null
19:25:27  	at org.junit.Assert.fail(Assert.java:86)
19:25:27  	at org.junit.Assert.assertTrue(Assert.java:41)
19:25:27  	at org.junit.Assert.assertNotNull(Assert.java:712)
19:25:27  	at org.junit.Assert.assertNotNull(Assert.java:722)
19:25:27  	at org.eclipse.tracecompass.lttng2.kernel.core.tests.synchronization.UstKernelSyncTest.testOneEvent(UstKernelSyncTest.java:167)
19:25:27  
19:25:27  Running org.eclipse.tracecompass.lttng2.kernel.core.tests.ActivatorTest
19:25:27  Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 sec - in org.eclipse.tracecompass.lttng2.kernel.core.tests.ActivatorTest
19:25:27  testStartBundleContext(org.eclipse.tracecompass.lttng2.kernel.core.tests.ActivatorTest)  Time elapsed: 0.001 sec
19:25:27  testActivator(org.eclipse.tracecompass.lttng2.kernel.core.tests.ActivatorTest)  Time elapsed: 0 sec
19:25:27  testStopBundleContext(org.eclipse.tracecompass.lttng2.kernel.core.tests.ActivatorTest)  Time elapsed: 0 sec
19:25:27  testGetDefault(org.eclipse.tracecompass.lttng2.kernel.core.tests.ActivatorTest)  Time elapsed: 0 sec
19:25:27  
19:25:27  Results :
19:25:27  
19:25:27  Failed tests: 
19:25:27    UstKernelSyncTest.testOneEvent:167 null
Comment 1 Marc-André Laperle CLA 2016-11-02 09:33:48 EDT 
which build? I'd like to attach the console log, etc.
Comment 2 Marc-André Laperle CLA 2016-11-15 10:54:40 EST 
I see this is still happening (easier to see on http://ci.lttng.org/). Alex, do you have an idea why this is happening?
Comment 3 Alexandre Montplaisir CLA 2016-11-16 19:45:54 EST 
Hmm, I see two possibilities, either the wrong event is retrieved (or somehow the trace is not correlated correctly, and the event doesn't end at the expected timestamp relative to the kernel trace), OR it's the analysis module that does not return the expected information.

I've added https://git.eclipse.org/r/#/c/85187/ which adds another check, which should tell us which one of the two problems it is next time it fails.