eclipse-xtext / eclipse-xtext/xtext
TypeResourceUnloaderTest is flaky
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 831
- Forks
- 330
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 12
Description
The org.eclipse.xtext.common.types.ui.notification.TypeResourceUnloaderTest.testCloseEditorAndDiscardWorkingCopy test is flaky, sometimes it is failing on Jenkins but succeeds on my local Windows computer.
See also https://github.com/eclipse/xtext-eclipse/pull/1400#issuecomment-615279534
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with org.eclipse.xtext.common.types.ui.notification.TypeResourceUnloaderTest.testCloseEditorAndDiscardWorkingCopy and reproduce the failure in Jenkins, comparing it with the successful Windows run. Done means the test executes reliably without intermittent failures; the linked pull request discussion may provide additional context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100