Bug 298064

Summary:	[compiler] LookupTest.test048 failed in M20091216-0800 build
Product:	[Eclipse Project] JDT	Reporter:	Frederic Fusier <frederic_fusier>
Component:	Core	Assignee:	Olivier Thomann <Olivier_Thomann>
Status:	VERIFIED INVALID	QA Contact:
Severity:	normal
Priority:	P3	CC:	Olivier_Thomann, srikanth_sankaran
Version:	3.6
Target Milestone:	3.6 M5
Hardware:	PC
OS:	Linux
Whiteboard:

Description Frederic Fusier

2009-12-17 06:57:26 EST

LookupTest.test048 failed in last M20091216-0800 maintenance build although we did not contribute in this build and that test passed in previous build.

Here's the stack trace:
Unexpected output running resulting class file for X.java: --[START]-- ---[END]---

junit.framework.AssertionFailedError: Unexpected output running resulting class file for X.java:
--[START]--
---[END]---

at org.eclipse.jdt.core.tests.compiler.regression.AbstractRegressionTest.runTest(AbstractRegressionTest.java:2264)
at org.eclipse.jdt.core.tests.compiler.regression.AbstractRegressionTest.runTest(AbstractRegressionTest.java:2043)
at org.eclipse.jdt.core.tests.compiler.regression.AbstractRegressionTest.runConformTest(AbstractRegressionTest.java:1248)
at org.eclipse.jdt.core.tests.compiler.regression.LookupTest.test048(LookupTest.java:1635)

Comment 1 Olivier Thomann

2009-12-17 10:10:46 EST

The reason of the failure is:
org.eclipse.jdt.core.tests.compiler.regression.LookupTest#test048 - 1.5
[ERR]:Exception in thread "main" java.net.BindException: Address already in use
	at java.net.PlainSocketImpl.socketBind(Native Method)
	at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
	at java.net.ServerSocket.bind(ServerSocket.java:319)
	at java.net.ServerSocket.<init>(ServerSocket.java:185)
	at java.net.ServerSocket.<init>(ServerSocket.java:97)
	at org.eclipse.jdt.core.tests.util.VerifyTests.run(VerifyTests.java:175)
	at org.eclipse.jdt.core.tests.util.VerifyTests.main(VerifyTests.java:172)

There is nothing we can do to fix this.

Comment 2 Olivier Thomann

2009-12-17 10:34:58 EST

Closing as INVALID.
For some reason the ServerSocket could not be closed properly. There is nothing we can do as we do call a close() on it.

Comment 3 Srikanth Sankaran

2010-01-25 06:21:53 EST

Verified for 3.6M5