Bug 426763 - SecurityAdminUnitTests.testEncodingInfos01 had an error
Summary: SecurityAdminUnitTests.testEncodingInfos01 had an error
Status: RESOLVED WORKSFORME
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Framework (show other bugs)
Version: 3.10.0 Luna   Edit
Hardware: PC Linux-GTK
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: equinox.framework-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: test
Depends on:
Blocks:
 
Reported: 2014-01-28 02:46 EST by Dani Megert CLA
Modified: 2019-10-23 13:51 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dani Megert CLA 2014-01-28 02:46:43 EST
N20140127-2000.

http://download.eclipse.org/eclipse/downloads/drops4/N20140127-2000/testresults/html/org.eclipse.osgi.tests_linux.gtk.x86_6.0.html

Unable to acquire the state change lock for the module: osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.N20140127-2000"; singleton:="true" [id=0] STARTED [STOPPED]

org.osgi.framework.BundleException: Unable to acquire the state change lock for the module: osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.N20140127-2000"; singleton:="true" [id=0] STARTED [STOPPED]
at org.eclipse.osgi.container.Module.lockStateChange(Module.java:328)
at org.eclipse.osgi.container.SystemModule.init(SystemModule.java:35)
at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle.init(EquinoxBundle.java:207)
at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle.init(EquinoxBundle.java:199)
at org.eclipse.osgi.launch.Equinox.init(Equinox.java:168)
at org.eclipse.osgi.tests.securityadmin.SecurityAdminUnitTests.testEncodingInfos01(SecurityAdminUnitTests.java:884)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:657)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:310)
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:109)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:80)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:372)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:226)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1462)
at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
at org.eclipse.core.launcher.Main.main(Main.java:34)
Comment 1 Thomas Watson CLA 2014-01-28 09:18:16 EST
This is interesting in that it shows the framework is still trying to shutdown, similar to what we expect for the failures in bug 423146.  This time it fails on init() after we have tried to shutdown the framework.  Init cannot obtain the necessary lock because the shutdown process still holds the lock.
Comment 2 Eclipse Genie CLA 2019-10-23 13:39:30 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 3 Thomas Watson CLA 2019-10-23 13:51:05 EDT
The osgi tests seem to be stable for a while now.