Community
Participate
Working Groups
I20130503-2000. The underlying problem in either the code or test does not yet seem to be properly fixed (see bug 78422 and bug 252609). http://download.eclipse.org/eclipse/downloads/drops4/I20130503-2000/testresults/html/org.eclipse.jdt.debug.tests_win32.win32.x86_7.0.html Wrong number of lines output expected:<11> but was:<0> junit.framework.AssertionFailedError: Wrong number of lines output expected:<11> but was:<0> at org.eclipse.jdt.debug.tests.core.LineTrackerTests.testSimpleLineCounter(LineTrackerTests.java:96) at org.eclipse.jdt.debug.tests.AbstractDebugTest.runBare(AbstractDebugTest.java:2378) at org.eclipse.jdt.debug.tests.DebugSuite$1.run(DebugSuite.java:55) at java.lang.Thread.run(Thread.java:722)
Failed again in N20141014-2000: Wrong number of lines output expected:<11> but was:<0> junit.framework.AssertionFailedError: Wrong number of lines output expected:<11> but was:<0> at org.eclipse.jdt.debug.tests.core.LineTrackerTests.testSimpleLineCounter(LineTrackerTests.java:96) at org.eclipse.jdt.debug.tests.AbstractDebugTest.runBare(AbstractDebugTest.java:2458) at org.eclipse.jdt.debug.tests.DebugSuite$1.run(DebugSuite.java:55) at java.lang.Thread.run(Thread.java:744)
Failed again http://download.eclipse.org/eclipse/downloads/drops4/N20150717-2000/testresults/html/org.eclipse.jdt.debug.tests_win32.win32.x86_7.0.html testSimpleLineCounter Failure Wrong number of lines output expected:<11> but was:<0> junit.framework.AssertionFailedError: Wrong number of lines output expected:<11> but was:<0> at org.eclipse.jdt.debug.tests.core.LineTrackerTests.testSimpleLineCounter(LineTrackerTests.java:96) at org.eclipse.jdt.debug.tests.AbstractDebugTest.runBare(AbstractDebugTest.java:2466) at org.eclipse.jdt.debug.tests.DebugSuite$1.run(DebugSuite.java:57) at java.lang.Thread.run(Thread.java:744)
Fialed again http://download.eclipse.org/eclipse/downloads/drops4/N20150724-2000/testresults/html/org.eclipse.jdt.debug.tests_win32.win32.x86_7.0.html
Again! http://download.eclipse.org/eclipse/downloads/drops4/M20150729-1000/testresults/html/org.eclipse.jdt.debug.tests_win32.win32.x86_7.0.html
I'm seeing this error with IBM SDK with the below java version. Java version: -------------------- java version "1.8.0" Java(TM) SE Runtime Environment (build pwa6480sr4-20160608_04(SR4)) IBM J9 VM (build 2.8, JRE 1.8.0 Windows Server 2008 R2 amd64-64 Compressed References 20160607_306990 (JIT enabled, AOT enabled) J9VM - R28_20160607_0202_B306990 JIT - tr.r14.java.green_20160606_118883 GC - R28_20160607_0202_B306990_CMPRSS J9CL - 20160607_306990) JCL - 20160529_01 based on Oracle jdk8u91-b14 Error seen: ---------------------- ECL (eclipse) recordError type=AssertionFailed org.eclipse.jdt.debug.tests.core.LineTrackerTests testSimpleLineCounter Wrong number of lines output expected:<11> but was:<0> ECL (eclipse) junit.framework.AssertionFailedError: Wrong number of lines output expected:<11> but was:<0> ECL at org.eclipse.jdt.debug.tests.core.LineTrackerTests.testSimpleLineCounter(LineTrackerTests.java:96) ECL at org.eclipse.jdt.debug.tests.AbstractDebugTest.runBare(AbstractDebugTest.java:2466) ECL at org.eclipse.jdt.debug.tests.DebugSuite$1.run(DebugSuite.java:57) ECL at java.lang.Thread.run(Thread.java:785) ECL
When I only run that test (or the test class) on Windows, it always fails with: junit.framework.AssertionFailedError: Never received 'stopped' notification Sarika, it looks like you also see this. Please take a look for M2.
Will look at it in M3.
Moving it out of M3 as it needs more time to understand the problem. findings till now - 1. Tests run locally when run as part of AutomatedSuite (even if other test suites are moved out) 2. When Test suite is run individually as plugin test, all the tests in the suite fail to receive the stop notification which is the notification sent by console on close. 3. No notification for console line append happens, so number of reads is always 0 4. It works when run in debug mode
Not seen it recently.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
Not seen since long.
