tmf: Disable scheduler executionOrder test
authorAlexandre Montplaisir <alexmonthy@voxpopuli.im>
Wed, 27 Nov 2013 00:17:50 +0000 (19:17 -0500)
committerAlexandre Montplaisir <alexmonthy@voxpopuli.im>
Wed, 27 Nov 2013 16:31:19 +0000 (11:31 -0500)
That unit test has always been prone to multi-threaded uncertainty,
but recently it has been failing a lot more, which is very annoying
for the CI. I suspect it's because of the recent changes to the CTF
parser, some requests may end up finishing faster than they did before,
and before another request could be scheduled.

I suggest disabling it until we rewrite it to be more permissive (or
better, add testing mechanisms to the scheduler, and test the order
of requests being *sent*, not the order in which they finish).

Change-Id: I70db04feb9f86534f5d12623cf33f06d56b3a737
Signed-off-by: Alexandre Montplaisir <alexmonthy@voxpopuli.im>
Reviewed-on: https://git.eclipse.org/r/18942
Tested-by: Hudson CI
Reviewed-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
Reviewed-by: Matthew Khouzam <matthew.khouzam@ericsson.com>
IP-Clean: Matthew Khouzam <matthew.khouzam@ericsson.com>

org.eclipse.linuxtools.tmf.core.tests/src/org/eclipse/linuxtools/tmf/core/tests/request/TmfSchedulerTest.java

index 31cb73c565a4d3b153c0f6a0c396480c31472049..1523259652c5da58673f5d0f9c9ab12abf7d5931 100644 (file)
@@ -36,6 +36,7 @@ import org.eclipse.linuxtools.tmf.core.timestamp.TmfTimeRange;
 import org.eclipse.linuxtools.tmf.core.timestamp.TmfTimestamp;
 import org.junit.After;
 import org.junit.Before;
+import org.junit.Ignore;
 import org.junit.Test;
 
 /**
@@ -328,6 +329,7 @@ public class TmfSchedulerTest {
     /**
      * Test if the scheduler is working as expected
      */
+    @Ignore
     @Test
     public void executionOrder() {
         List<String> expectedOrder = new LinkedList<String>();
This page took 0.028516 seconds and 5 git commands to generate.