Bug 547779

Summary: ParameterNamesCodeMiningTest.testMultiLines() failed
Product: [Eclipse Project] JDT Reporter: Noopur Gupta <noopur_gupta>
Component: UIAssignee: JDT-UI-Inbox <jdt-ui-inbox>
Status: NEW --- QA Contact:
Severity: normal    
Priority: P3    
Version: 4.12   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard: stalebug
Bug Depends on: 546706    
Bug Blocks:    

Description Noopur Gupta CLA 2019-05-30 06:28:20 EDT 
ParameterNamesCodeMiningTest.testMultiLines() failed on Windows and Mac in I20190529-2005.

expected:<2> but was:<0> 

junit.framework.AssertionFailedError: expected:<2> but was:<0>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:159)
at junit.framework.Assert.assertEquals(Assert.java:166)
at junit.framework.TestCase.assertEquals(TestCase.java:324)
at org.eclipse.jdt.text.tests.codemining.ParameterNamesCodeMiningTest.testMultiLines(ParameterNamesCodeMiningTest.java:167)
...

The test passes on running locally on Windows machine.
Comment 1 Eclipse Genie CLA 2021-05-20 18:09:42 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.
Comment 2 Eclipse Genie CLA 2023-05-12 07:38:29 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.