eclipse-jdt / eclipse-jdt/eclipse.jdt.ui

Random RenamePackageTests failure in I-build

Open
#1,608 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
59
Forks
127
Avg merge
23h 30m
Merged PRs (30d)
35

Description

I20240822-0100
org.eclipse.jdt.ui.tests.refactoring.RenamePackageTests
testImportFromMultiRoots5

The above test failed on gtk3-java17.

```
invalid update in file ATest.java [in q [in srcTest [in RenamePack2]]] package q class ATest A t A t2 expected: but was:

org.junit.ComparisonFailure: invalid update in file ATest.java [in q [in srcTest [in RenamePack2]]]
package q
class ATest
A t
A t2 expected: but was:
at org.junit.Assert.assertEquals(Assert.java:117)
at org.eclipse.jdt.ui.tests.refactoring.GenericRefactoringTest.assertEqualLines(GenericRefactoringTest.java:648)
at org.eclipse.jdt.ui.tests.refactoring.RenamePackageTests.helperMultiProjects(RenamePackageTests.java:488)
at org.eclipse.jdt.ui.tests.refactoring.RenamePackageTests.testImportFromMultiRoots5(RenamePackageTests.java:1387)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
```

Contributor guide

Open the contributing guide

Research direction

Start with RenamePackageTests.testImportFromMultiRoots5 and its helperMultiProjects call, then inspect GenericRefactoringTest.assertEqualLines around the reported failure. Run the test on gtk3-java17 and compare the expected and actual ATest.java updates. Done means the intermittent failure is understood and the test passes consistently with the expected import update.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.