Community
Participate
Working Groups
https://download.eclipse.org/eclipse/downloads/drops4/I20211117-1830/testresults/html/org.eclipse.jdt.debug.tests_ep422I-unit-macM1-java17_macosx.cocoa.aarch64_17.html Line tracker did not receive init notification junit.framework.AssertionFailedError: Line tracker did not receive init notification at junit.framework.Assert.fail(Assert.java:57) at junit.framework.Assert.assertTrue(Assert.java:22) at junit.framework.Assert.assertNotNull(Assert.java:256) at junit.framework.TestCase.assertNotNull(TestCase.java:399) at org.eclipse.jdt.debug.tests.core.ArgumentTests$ConsoleArgumentOutputRetriever.getOutput(ArgumentTests.java:124) at org.eclipse.jdt.debug.tests.core.ArgumentTests.testOutput(ArgumentTests.java:400) at org.eclipse.jdt.debug.tests.core.ArgumentTests.testWithVMArg(ArgumentTests.java:321) at org.eclipse.jdt.debug.tests.core.ArgumentTests.testVMArgStandardQuotes(ArgumentTests.java:173) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at junit.framework.TestCase.runTest(TestCase.java:177) at junit.framework.TestCase.runBare(TestCase.java:142) at org.eclipse.jdt.debug.tests.AbstractDebugTest.runBare(AbstractDebugTest.java:2672) at junit.framework.TestResult$1.protect(TestResult.java:122) at junit.framework.TestResult.runProtected(TestResult.java:142) at junit.framework.TestResult.run(TestResult.java:125) at junit.framework.TestCase.run(TestCase.java:130) at junit.framework.TestSuite.runTest(TestSuite.java:241) at junit.framework.TestSuite.run(TestSuite.java:236) at junit.framework.TestSuite.runTest(TestSuite.java:241) at org.eclipse.jdt.debug.tests.DebugSuite$1.run(DebugSuite.java:61) at java.base/java.lang.Thread.run(Thread.java:833)
Looking at the test case, it appears that the ConsoleLineTracker#init(IConsole) is never invoked. Without a thorough examination, it appears unrelated to ticket 577265. Are there any other clues to what happens in the console log from the Jenkins job?
(In reply to Torbjörn Svensson from comment #1) > Looking at the test case, it appears that the > ConsoleLineTracker#init(IConsole) is never invoked. > Without a thorough examination, it appears unrelated to ticket 577265. > Are there any other clues to what happens in the console log from the > Jenkins job? https://download.eclipse.org/eclipse/downloads/drops4/I20211117-1830/testresults/ep422I-unit-mac64-java17_macosx.cocoa.x86_64_17/org.eclipse.jdt.debug.tests.AutomatedSuite.txt This is the link to the console log.
(In reply to Sarika Sinha from comment #2) > (In reply to Torbjörn Svensson from comment #1) > > Looking at the test case, it appears that the > > ConsoleLineTracker#init(IConsole) is never invoked. > > Without a thorough examination, it appears unrelated to ticket 577265. > > Are there any other clues to what happens in the console log from the > > Jenkins job? > > https://download.eclipse.org/eclipse/downloads/drops4/I20211117-1830/ > testresults/ep422I-unit-mac64-java17_macosx.cocoa.x86_64_17/org.eclipse.jdt. > debug.tests.AutomatedSuite.txt > > This is the link to the console log. Unfortunately, this log does not help narrow down what happened. Was this a onetime failure or can it be reproduced reliably on macos?
https://download.eclipse.org/eclipse/downloads/drops4/I20220302-1800/testresults/html/org.eclipse.jdt.debug.tests_ep423I-unit-cen64-gtk3-java11_linux.gtk.x86_64_11.html
(In reply to Sarika Sinha from comment #4) > https://download.eclipse.org/eclipse/downloads/drops4/I20220302-1800/ > testresults/html/org.eclipse.jdt.debug.tests_ep423I-unit-cen64-gtk3- > java11_linux.gtk.x86_64_11.html In this run it is testProgramArgEmbeddedQuotes that fails. The tests are pretty similar.
I have spent some time looking at this and I can't figure out why it is failing. I have searched to find a race condition between the init call and I cannot find it.
Bug 576999 also many similar tests keep failing for console mismatch.
(In reply to Sarika Sinha from comment #7) > Bug 576999 also many similar tests keep failing for console mismatch. That one isn't a console issue - but I think I have a fix for it anyway.
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.
