SpringApplicationHierarchyTests was originally added as part of some changes to make actuator play nicely with context hierarchies. Since then, a growing list of auto-configurations have been excluded but the tests continue to be flaky as they auto-configure all sorts of things that don't seem to be specifically relevant to a context hierarchy. For example, the most recent failure was on Windows CI due to Hazelcast trying to establish a connection to another Hazelcast node on the same subnet. Furthermore, Actuator has undergone significant changes since the tests were added in 0.5.x. At this point, I think we'd be better off removing them and adding more focussed tests in the future should the need arise.