Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
As reported by Pontus Amberg in the mailing list:
"I've encountered random test failures in the
org.apache.sling.launchpad.base.impl.SlingFelixTest.test_start_stop()
test where "this.notifiable.stoppedCalled" is false. I'm not sure but does
super.stop() in SlingFelix set m_shutdownGate in Felix to null and is there
a possibility that it will do so before the Notifier instance in SlingFelix is
run?
Take a look at the stop() methods in SlingFelix where the Notifier
is started and super.stop() is invoked."
Attachments
Issue Links
- blocks
-
SLING-3234 Sling buildbot continuous integration
- Resolved
- is related to
-
SLING-3259 SlingFelixTest fails semi-randomly, "Timed out waiting for framework to stop"
- Resolved