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

Bug 462918

Summary: [test][model]NamingConventionTests.testSuggestFieldName002 (and 27 others) failed
Product: [Eclipse Project] JDT Reporter: Sasikanth Bharadwaj <sasikanth.bharadwaj>
Component: CoreAssignee: Manoj N Palat <manoj.palat>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: jarthana, manoj.palat
Version: 4.5   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard: stalebug

Description Sasikanth Bharadwaj CLA 2015-03-24 04:49:47 EDT
Build Id N20150323-2000
http://download.eclipse.org/eclipse/downloads/drops4/N20150323-2000/testresults/html/org.eclipse.jdt.core.tests.model_win32.win32.x86_7.0.html

Total 28 tests failing with similar result

----------- Expected ------------ oneClass class1 ------------ but was ------------ _oneClass _class oneClass class1 --------- Difference is ---------- expected:<[]oneClass class1> but was:<[_oneClass _class ]oneClass class1>

junit.framework.ComparisonFailure:
----------- Expected ------------
oneClass
class1
------------ but was ------------
_oneClass
_class
oneClass
class1
--------- Difference is ----------
expected:<[]oneClass
class1> but was:<[_oneClass
_class
]oneClass
class1>
at org.eclipse.jdt.core.tests.junit.extension.TestCase.assertStringEquals(TestCase.java:268)
at org.eclipse.jdt.core.tests.junit.extension.TestCase.assumeEquals(TestCase.java:288)
at org.eclipse.jdt.core.tests.junit.extension.TestCase.assumeEquals(TestCase.java:278)
at org.eclipse.jdt.core.tests.model.NamingConventionTests.testSuggestFieldName002(NamingConventionTests.java:144)
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 Manoj N Palat CLA 2015-03-24 04:57:26 EDT
I will take a look
Comment 2 Manoj N Palat CLA 2015-03-24 06:45:31 EDT
Tried the following:

- ran locally with win32 and win32/64
- Checked the previous commits (no breakpoint hit for these tests)
- executed the tests as per the order (testSuggestFieldName009 testSuggestFieldName008 testSuggestFieldName007 testSuggestFieldName006 testSuggestFieldName005 testSuggestFieldName004 testSuggestFieldName003   testSuggestFieldName002   testSuggestFieldName001)

tests passed in all the cases. Would wait for today's results
Comment 3 Eclipse Genie CLA 2020-04-06 19:39:21 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.