Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 438507 - ClasspathTests.testMissingClasspath failed on all platforms
Summary: ClasspathTests.testMissingClasspath failed on all platforms
Status: RESOLVED DUPLICATE of bug 378787
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.4   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Manoj N Palat CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-29 23:22 EDT by Manoj N Palat CLA
Modified: 2014-07-22 00:36 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Manoj N Palat CLA 2014-06-29 23:22:29 EDT
http://download.eclipse.org/eclipse/downloads/drops4/N20140628-1500/testresults/html/org.eclipse.jdt.core.tests.model_linux.gtk.x86_64_8.0.html

Unexpected markers. ----------- Expected ------------ Unable to read '.classpath' file of project 'P' ------------ but was ------------ --------- Difference is ---------- expected:<[Unable to read '.classpath' file of project 'P']> but was:<[]> 

junit.framework.ComparisonFailure: Unexpected markers.
----------- Expected ------------
Unable to read '.classpath' file of project 'P'
------------ but was ------------

--------- Difference is ----------
expected:<[Unable to read '.classpath' file of project 'P']> but was:<[]>
at org.eclipse.jdt.core.tests.junit.extension.TestCase.assertStringEquals(TestCase.java:258)
at org.eclipse.jdt.core.tests.junit.extension.TestCase.assertEquals(TestCase.java:234)
at org.eclipse.jdt.core.tests.model.AbstractJavaModelTests.assertMarkers(AbstractJavaModelTests.java:731)
at org.eclipse.jdt.core.tests.model.AbstractJavaModelTests.assertMarkers(AbstractJavaModelTests.java:704)
at org.eclipse.jdt.core.tests.model.ClasspathTests.testMissingClasspath(ClasspathTests.java:4083)
at org.eclipse.jdt.core.tests.model.SuiteOfTestCases$Suite.runTest(SuiteOfTestCases.java:104)
at org.eclipse.jdt.core.tests.model.SuiteOfTestCases$Suite.superRun(SuiteOfTestCases.java:88)
at org.eclipse.jdt.core.tests.model.SuiteOfTestCases$1.protect(SuiteOfTestCases.java:76)
at org.eclipse.jdt.core.tests.model.SuiteOfTestCases$Suite.run(SuiteOfTestCases.java:85)
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:382)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
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 2 Manoj N Palat CLA 2014-06-29 23:34:47 EDT
Jay, can you take a quick look - as per the history this test has been commented out by your commit sometime back.
Comment 3 Manoj N Palat CLA 2014-06-30 00:19:03 EDT
Enabling was not intentional as it was an oversight when individual test additions were replaced by the general setupSuite. Would disable the test.
Comment 5 Markus Keller CLA 2014-06-30 06:56:16 EDT
The test is a regression test for bug 39877, and the implementation looks valid to me. It would be good to know why the test fails. It is green locally, even when I add an explicit
		preferences.setAutoBuilding(...);
with false or true.

Commenting it out for now is OK, but we should keep a bug open.
Comment 6 Manoj N Palat CLA 2014-07-14 04:15:26 EDT
(In reply to Markus Keller from comment #5)

> Commenting it out for now is OK, but we should keep a bug open.

See Bug 378787

*** This bug has been marked as a duplicate of bug 378787 ***