Community
Participate
Working Groups
We got the first failure like this in the I20111018-0850 build. It is possible that the test has a timing issue in properly waiting for the framework to update (restart) before performing the tests. The suspect code looks like this: try { // delay hack to allow waitForUpdate thread to block on waitForStop before we update. Thread.sleep(100); } catch (InterruptedException e) { fail("unexpected interuption", e); } Perhaps sleeping 100 ms is not enough if the test machine is under a heavy load. Failed to get bundle entries: junit.framework.AssertionFailedError: No manifest for: bundle-b1084_0.0.0 [1085] junit.framework.AssertionFailedError: Failed to get bundle entries: junit.framework.AssertionFailedError: No manifest for: bundle-b1084_0.0.0 [1085] at org.eclipse.core.tests.harness.CoreTest.fail(CoreTest.java:67) at org.eclipse.osgi.tests.bundles.SystemBundleTests.openAllBundleFiles(SystemBundleTests.java:1048) at org.eclipse.osgi.tests.bundles.SystemBundleTests.doMRUBundleFileList(SystemBundleTests.java:990) at org.eclipse.osgi.tests.bundles.SystemBundleTests.testMRUBundleFileList(SystemBundleTests.java:928) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:501) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:259) 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:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:352) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:624) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:579) at org.eclipse.equinox.launcher.Main.run(Main.java:1431) at org.eclipse.equinox.launcher.Main.main(Main.java:1407) at org.eclipse.core.launcher.Main.main(Main.java:34) Caused by: junit.framework.AssertionFailedError: No manifest for: bundle-b1084_0.0.0 [1085] at org.eclipse.osgi.tests.bundles.SystemBundleTests.openAllBundleFiles(SystemBundleTests.java:1043)
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.
