Comment 1 Sarika Sinha 2016-02-24 02:11:25 EST

Added a temporary test case to resolve local host. As observing these test failure since last couple of days. 

http://git.eclipse.org/c/jdt/eclipse.jdt.debug.git/commit/?id=af70e1a85f9a3e80899bcdd28f59856ab9cd70e9

Comment 2 David Williams 2016-02-24 11:38:17 EST

(In reply to Sarika Sinha from comment #1)
> Added a temporary test case to resolve local host. As observing these test
> failure since last couple of days. 
> 
> http://git.eclipse.org/c/jdt/eclipse.jdt.debug.git/commit/
> ?id=af70e1a85f9a3e80899bcdd28f59856ab9cd70e9

See bug 487915 for changes to infrastructure that *might* improve results for this tests. (Doesn't hurt to leave the "sanity check" test in there, but *might* be harder to reproduce the error now.) If you still get the error, though, that might be good data for the webmasters (such as if a DNS issue).

Comment 3 Sarika Sinha 2016-02-26 02:49:42 EST

Working fine since last 2 builds. If works ok for another couple of days, will remove the extra testcase.

Comment 4 David Williams 2016-02-26 08:35:28 EST

(In reply to Sarika Sinha from comment #3)
> Working fine since last 2 builds. If works ok for another couple of days,
> will remove the extra testcase.

Why remove it? If is does measure "infrastructure health" seems worth leaving in, 
just in case there are issues in the future.

Comment 5 Sarika Sinha 2016-02-26 11:45:56 EST

(In reply to David Williams from comment #4)
> (In reply to Sarika Sinha from comment #3)
> > Working fine since last 2 builds. If works ok for another couple of days,
> > will remove the extra testcase.
> 
> Why remove it? If is does measure "infrastructure health" seems worth
> leaving in, 
> just in case there are issues in the future.

Ok.

Comment 6 Sarika Sinha 2016-02-28 21:35:01 EST

Failed for a different test for Cannot connect to VM
testAnonTypeC1	Error	Cannot connect to VM

org.eclipse.core.runtime.CoreException: Cannot connect to VM
at org.eclipse.jdt.launching.AbstractVMRunner.abort(AbstractVMRunner.java:53)
at org.eclipse.jdt.internal.launching.StandardVMDebugger.run(StandardVMDebugger.java:376)
at org.eclipse.jdt.launching.JavaLaunchDelegate.launch(JavaLaunchDelegate.java:102)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
at org.eclipse.jdt.debug.tests.AbstractDebugTest.launchAndWait(AbstractDebugTest.java:1035)
at org.eclipse.jdt.debug.tests.AbstractDebugTest.launchAndWait(AbstractDebugTest.java:1019)
at org.eclipse.jdt.debug.tests.AbstractDebugTest.launchToBreakpoint(AbstractDebugTest.java:1181)
at org.eclipse.jdt.debug.tests.AbstractDebugTest.launchToBreakpoint(AbstractDebugTest.java:1153)
at org.eclipse.jdt.debug.tests.AbstractDebugTest.launchToBreakpoint(AbstractDebugTest.java:1138)
at org.eclipse.jdt.debug.tests.sourcelookup.TypeResolutionTests.resolve(TypeResolutionTests.java:136)
at org.eclipse.jdt.debug.tests.sourcelookup.TypeResolutionTests.testAnonTypeC1(TypeResolutionTests.java:80)
at org.eclipse.jdt.debug.tests.AbstractDebugTest.runBare(AbstractDebugTest.java:2469)
at org.eclipse.jdt.debug.tests.DebugSuite$1.run(DebugSuite.java:57)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.sun.jdi.connect.TransportTimeoutException
at org.eclipse.jdi.internal.connect.SocketTransportService.accept(SocketTransportService.java:105)
at org.eclipse.jdi.internal.connect.SocketTransportImpl.accept(SocketTransportImpl.java:60)
at org.eclipse.jdi.internal.connect.SocketListeningConnectorImpl.accept(SocketListeningConnectorImpl.java:157)
at org.eclipse.jdt.internal.launching.StandardVMDebugger$ConnectRunnable.run(StandardVMDebugger.java:112)

http://download.eclipse.org/eclipse/downloads/drops4/N20160227-1500/testresults/html/org.eclipse.jdt.debug.tests_macosx.cocoa.x86_64_8.0.html

Comment 7 Sarika Sinha 2016-02-28 21:40:49 EST

3 tests failed with same error:
http://download.eclipse.org/eclipse/downloads/drops4/N20160226-2000/testresults/html/org.eclipse.jdt.debug.tests_macosx.cocoa.x86_64_8.0.html

Comment 8 David Williams 2016-02-28 22:58:12 EST

I did try to look a little closer and Hudson's mactest2 log, to see if it displayed anything that might be related. I did end up opening bug 488656 for "anomalies", but not sure any of them would account for this particular failure. 

One was related to it's "internet time" being in the future by 8 seconds, and the other was logged messages about "native mac processes" failing (the latter sounds serious, but did not seem to correlate very closely to the times our tests would be running). 

= = = = = = 

A couple of comments. I doubt any will be too helpful. 

- Are you running the "performance tests" all the time? Even when doing unit tests? I only ask since I tried running in the debugger, and saw a few things that appeared to be related to "performance" -- but did not look very closely. (But, if you are, I suspect the performance tests are quite a stress test!) 
I never did get the tests to run very well, not sure why. (It has been sitting at 12/7567 with 1 error for a while now). But, I do not give it "focus" or anything, if it needs that. 

- There is a lot of exceptions in the test log, at 
http://download.eclipse.org/eclipse/downloads/drops4/N20160227-1500/testresults/macosx.cocoa.x86_64_8.0/org.eclipse.jdt.debug.tests.AutomatedSuite.txt

Those may be expected -- part of what you are testing -- but assume you've looked? I was surprised not to see anything about "failed to connect". 
Is there any way you can print more data when it "fails to connect"? Such as the literal 'ip' (not just "localhost' and port number?). It would not do me much good :) but might be good data for webmasters? 

- Just a thought, but if we think this is due to a tiny problem with intranet, or similar, is there any way you can "retry" a few times? Or, is that done already? I would think you could "in code" or "in test". (If you need to do "in code, but only when tests are running, there are a few other places where in our code, we have some logic that basically says "if (testFramework.isActive()) then {do something extra only for test-mode}". 

- If you think it would help, we can always ask the webmasters to reboot that machine ... or look at its logs, or similar (especially if you knew what we were looking for :) 

Bummer.

Comment 9 David Williams 2016-02-29 00:13:16 EST

(In reply to David Williams from comment #8)

> - Are you running the "performance tests" all the time? Even when doing unit
> tests? 

I see my mistake now. I selected the bundle and selected "run as JUnit Plugin Test". 

After not getting much further than I mentioned before, I looked in your test.xml file, I figured out I should select only the main JUnit test class: 
org.eclipse.jdt.debug.tests.AutomatedSuite
and now it is running better, and running only 902 tests total.

Comment 10 Sarika Sinha 2016-02-29 01:53:49 EST

Right now we retry if we get InterruptedIOException and Status Handle suggests to retry. I will change it to retry for 5 times by default and see how it behaves.

Comment 11 Sarika Sinha 2016-02-29 04:26:18 EST

Added 5 retry attempts
http://git.eclipse.org/c/jdt/eclipse.jdt.debug.git/commit/?id=567542cd1df099bb451325df6eed77d21f13d71f

Comment 12 Markus Keller 2016-03-02 06:38:39 EST

*** Bug 444797 has been marked as a duplicate of this bug. ***

Comment 13 Sarika Sinha 2016-03-08 02:18:25 EST

After a long time no failure today
http://download.eclipse.org/eclipse/downloads/drops4/N20160307-2000/testResults.php

Comment 14 Sarika Sinha 2016-03-13 01:25:24 EST

Not much to do now.

Comment 15 Sarika Sinha 2016-08-22 02:02:57 EDT

After a long time failure
http://download.eclipse.org/eclipse/downloads/drops4/N20160820-1459/testResults.php

Comment 16 Sarika Sinha 2017-02-19 22:57:30 EST

Happened again!
http://download.eclipse.org/eclipse/downloads/drops4/I20170217-2000/testresults/html/org.eclipse.jdt.debug.tests_ep47I-unit-mac64_macosx.cocoa.x86_64_8.0.html

Comment 17 Sarika Sinha 2017-06-01 23:17:23 EDT

On Y build
http://download.eclipse.org/eclipse/downloads/drops4/Y20170601-1000/testresults/html/org.eclipse.jdt.debug.tests_ep47Y-unit-mac64_macosx.cocoa.x86_64_8.0.html

Comment 18 Sarika Sinha 2017-06-13 00:18:42 EDT

Happening again!!

http://download.eclipse.org/eclipse/downloads/drops4/I20170612-0950/testresults/html/org.eclipse.jdt.debug.tests_ep47I-unit-mac64_macosx.cocoa.x86_64_8.0.html

Comment 19 Sarika Sinha 2017-06-13 00:31:23 EDT

testTerminateAll_01	Failure	expected:<2> but was:<3>

junit.framework.AssertionFailedError: expected:<2> but was:<3>
at org.eclipse.jdt.debug.tests.console.ConsoleTerminateAllActionTests.testTerminateAll_01(ConsoleTerminateAllActionTests.java:76)
at org.eclipse.jdt.debug.tests.AbstractDebugTest.runBare(AbstractDebugTest.java:2528)
at org.eclipse.jdt.debug.tests.DebugSuite$1.run(DebugSuite.java:57)
at java.lang.Thread.run(Thread.java:745)

Same cause!! Both happen together.

Comment 20 Sarika Sinha 2017-06-21 06:08:53 EDT

http://download.eclipse.org/eclipse/downloads/drops4/I20170620-2000/testresults/html/org.eclipse.jdt.debug.tests_ep48I-unit-mac64_macosx.cocoa.x86_64_8.0.html

Both together !!

Comment 21 Sarika Sinha 2017-06-23 00:07:56 EDT

Looks like a daily affair with new setup !!
http://download.eclipse.org/eclipse/downloads/drops4/I20170622-0950/testresults/html/org.eclipse.jdt.debug.tests_ep48I-unit-mac64_macosx.cocoa.x86_64_8.0.html

Comment 22 Sarika Sinha 2017-06-26 23:36:39 EDT

Again!!
http://download.eclipse.org/eclipse/downloads/drops4/I20170623-2000/testresults/html/org.eclipse.jdt.debug.tests_ep48I-unit-mac64_macosx.cocoa.x86_64_8.0.html

Comment 23 Sarika Sinha 2018-07-25 05:16:53 EDT

Moving out of M2.

Not seen it failing in last month.

Comment 24 Sarika Sinha 2018-09-17 00:44:51 EDT

http://download.eclipse.org/eclipse/downloads/drops4/I20180914-0620/testresults/html/org.eclipse.jdt.debug.tests_ep410I-unit-cen64-gtk3_linux.gtk.x86_64_8.0.html

testSetterFilters	Error	Cannot connect to VM

org.eclipse.core.runtime.CoreException: Cannot connect to VM
at org.eclipse.jdt.launching.AbstractVMRunner.abort(AbstractVMRunner.java:57)
at org.eclipse.jdt.internal.launching.StandardVMDebugger.run(StandardVMDebugger.java:448)
at org.eclipse.jdt.launching.JavaLaunchDelegate.launch(JavaLaunchDelegate.java:159)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:862)
at org.eclipse.jdt.debug.tests.AbstractDebugTest.launchAndWait(AbstractDebugTest.java:1067)
at org.eclipse.jdt.debug.tests.AbstractDebugTest.launchAndWait(AbstractDebugTest.java:1051)
at org.eclipse.jdt.debug.tests.AbstractDebugTest.launchToLineBreakpoint(AbstractDebugTest.java:1329)
at org.eclipse.jdt.debug.tests.AbstractDebugTest.launchToLineBreakpoint(AbstractDebugTest.java:1312)
at org.eclipse.jdt.debug.test.stepping.StepFilterTests.testSetterFilters(StepFilterTests.java:274)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at junit.framework.TestCase.runBare(TestCase.java:141)
at org.eclipse.jdt.debug.tests.AbstractDebugTest.runBare(AbstractDebugTest.java:2557)
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:129)
at junit.framework.TestSuite.runTest(TestSuite.java:252)
at junit.framework.TestSuite.run(TestSuite.java:247)
at junit.framework.TestSuite.runTest(TestSuite.java:252)
at org.eclipse.jdt.debug.tests.DebugSuite$1.run(DebugSuite.java:60)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.sun.jdi.connect.TransportTimeoutException
at org.eclipse.jdi.internal.connect.SocketTransportService.accept(SocketTransportService.java:103)
at org.eclipse.jdi.internal.connect.SocketTransportImpl.accept(SocketTransportImpl.java:63)
at org.eclipse.jdi.internal.connect.SocketListeningConnectorImpl.accept(SocketListeningConnectorImpl.java:167)
at org.eclipse.jdt.internal.launching.StandardVMDebugger$ConnectRunnable.run(StandardVMDebugger.java:116)
... 1 more

Comment 25 Sarika Sinha 2018-11-21 04:17:11 EST

Not seeing this error now.

Comment 26 Eclipse Genie 2020-11-11 13:16:48 EST

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.

Comment 27 Sarika Sinha 2021-11-18 23:09:48 EST

https://download.eclipse.org/eclipse/downloads/drops4/I20211117-1830/testresults/html/org.eclipse.jdt.debug.tests_ep422I-unit-mac64-java17_macosx.cocoa.x86_64_17.html

3 tests failed.

Comment 28 Sarika Sinha 2022-05-19 13:44:41 EDT

*** Bug 566643 has been marked as a duplicate of this bug. ***

Comment 29 Eclipse Genie 2024-05-09 04:09:23 EDT

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.