Community
Participate
Working Groups
The test (for the first time to my knowledge) failed with the following trace: File leaked during build: L/testLeaksOnCleanBuild/test.jar java.lang.IllegalStateException: File leaked during build: L/testLeaksOnCleanBuild/test.jar at org.eclipse.jdt.core.tests.builder.AbstractLeakTest.tryRemoveFile(AbstractLeakTest.java:156) at org.eclipse.jdt.core.tests.builder.AbstractLeakTest.assertNotLeaked(AbstractLeakTest.java:135) at org.eclipse.jdt.core.tests.builder.AbstractLeakTest.internalTestUsedLibraryLeaks(AbstractLeakTest.java:85) at org.eclipse.jdt.core.tests.builder.AbstractLeakTest.testLeaksOnCleanBuild(AbstractLeakTest.java:63) at org.eclipse.jdt.core.tests.builder.LeakTestsBefore9.testLeaksOnCleanBuild(LeakTestsBefore9.java:36) https://download.eclipse.org/eclipse/downloads/drops4/I20190605-1800/testresults/html/org.eclipse.jdt.core.tests.builder_ep412I-unit-win32-java8_win32.win32.x86_64_8.0.html
Andrey, any idea what might be happening?
(In reply to Jay Arthanareeswaran from comment #1) > Andrey, any idea what might be happening? No. This is first time this test failed AFAIK, and there were no changes in platform resources or JDT core that could be related (or no at all in the recent few builds). I guess this is not JDT specific.
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.