Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 462636

Summary:	[test][model]JavaIndexTests.testPlatformJarIndexFile failed
Product:	[Eclipse Project] JDT	Reporter:	Sasikanth Bharadwaj <sasikanth.bharadwaj>
Component:	Core	Assignee:	JDT-Core-Inbox <jdt-core-inbox>
Status:	CLOSED WONTFIX	QA Contact:	Manoj N Palat <manoj.palat>
Severity:	normal
Priority:	P3	CC:	jarthana, manoj.palat
Version:	4.5
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	stalebug

Description Sasikanth Bharadwaj

2015-03-20 04:51:06 EDT

build Id : I20150319-1640
platform: win32

details: ----------- Expected ------------ platform:/resource/ForIndex/Test.index.zip!/Test.index ------------ but was ------------ file:/C:/hb/workspace/ep45I-unit-win32/workarea/I20150319-1640/eclipse-testing/test-eclipse/eclipse/jdt_model_folder/data/.metadata/.plugins/org.eclipse.jdt.core/3770488089.index --------- Difference is ---------- expected:<[platform:/resource/ForIndex/Test.index.zip!/Test].index> but was:<[file:/C:/hb/workspace/ep45I-unit-win32/workarea/I20150319-1640/eclipse-testing/test-eclipse/eclipse/jdt_model_folder/data/.metadata/.plugins/org.eclipse.jdt.core/3770488089].index>

stacktrace: junit.framework.ComparisonFailure: 
----------- Expected ------------
platform:/resource/ForIndex/Test.index.zip!/Test.index
------------ but was ------------
file:/C:/hb/workspace/ep45I-unit-win32/workarea/I20150319-1640/eclipse-testing/test-eclipse/eclipse/jdt_model_folder/data/.metadata/.plugins/org.eclipse.jdt.core/3770488089.index
--------- Difference is ----------
 expected:<[platform:/resource/ForIndex/Test.index.zip!/Test].index> but was:<[file:/C:/hb/workspace/ep45I-unit-win32/workarea/I20150319-1640/eclipse-testing/test-eclipse/eclipse/jdt_model_folder/data/.metadata/.plugins/org.eclipse.jdt.core/3770488089].index>
	at org.eclipse.jdt.core.tests.junit.extension.TestCase.assertStringEquals(TestCase.java:259)
	at org.eclipse.jdt.core.tests.junit.extension.TestCase.assertEquals(TestCase.java:235)
	at org.eclipse.jdt.core.tests.junit.extension.TestCase.assertEquals(TestCase.java:232)
	at org.eclipse.jdt.core.tests.model.JavaIndexTests.testPlatformJarIndexFile(JavaIndexTests.java:855)
	at org.eclipse.jdt.core.tests.model.SuiteOfTestCases$Suite.runTest(SuiteOfTestCases.java:105)
	at org.eclipse.jdt.core.tests.model.SuiteOfTestCases$Suite.superRun(SuiteOfTestCases.java:89)
	at org.eclipse.jdt.core.tests.model.SuiteOfTestCases$Suite$1.protect(SuiteOfTestCases.java:77)
	at org.eclipse.jdt.core.tests.model.SuiteOfTestCases$Suite.run(SuiteOfTestCases.java:86)
	at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:657)
	at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:310)
	at org.eclipse.test.CoreTestApplication.runTests(CoreTestApplication.java:36)
	at org.eclipse.test.CoreTestApplication.run(CoreTestApplication.java:32)
	at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
	at org.eclipse.core.launcher.Main.main(Main.java:34)

Comment 1 Jay Arthanareeswaran

2015-03-23 04:47:43 EDT

Could this be a stale data issue from other tests run before? Manoj, please take a look.

Comment 2 Manoj N Palat

2015-03-23 04:58:30 EDT

(In reply to Jay Arthanareeswaran from comment #1)
> Could this be a stale data issue from other tests run before? Manoj, please
> take a look.

Jay: I checked that sequence of run - prima facie this issue is not related to stale data of old tests. Most probable hypothesis at this point of time is that IClasspathAttribute.INDEX_LOCATION_ATTRIBUTE_NAME usage at some point of time returns null and computes the default index. Will update once I have more info.

Comment 3 Jay Arthanareeswaran

2015-10-27 00:06:04 EDT

JavaIndexTests.testIndexInJar failed in the latest build and the symptom appears same.

http://download.eclipse.org/eclipse/downloads/drops4/I20151026-0800/testresults/html/org.eclipse.jdt.core.tests.model_win32.win32.x86_8.0.html

Comment 4 Eclipse Genie

2019-09-01 14:07:19 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.