I also run into this issue when running hibernate testsuite

To be clear... Strong runs into the same symptom: builds hanging during test execution. Hibernate build is not swapping security managers during tests.

I'm seeing the same issue with OpenJFX. I have a unit test which installs a security manager, and this causes gradle to hang while executing tests.

http://hg.openjdk.java.net/openjfx/8/master/rt/file/0b33c9c1d41e/javafx-concurrent/test/javafx/concurrent/ServiceWithSecurityManagerTest.java

Reproduced with a test: https://github.com/gradle/gradle/commit/8be958eeb418b4107053d76a55e0dd022288cdbf

I think I run into the same problem with current Gradle when I upgrade my project from Elasticsearch <= 2.1.x to >= 2.2.0. Elasticsearch added some SecurityManager functionality which kicks in during tests and this also seems to cause hanging test-execution in Gradle as described here.

An Elasticsearch-related workaround for this seems to be:

test {
    systemProperties = System.properties

    // see https://github.com/elastic/elasticsearch/issues/16459
    // and also https://issues.gradle.org/browse/GRADLE-2170
    systemProperty 'tests.security.manager', 'false'
}

That particular workaround for Elasticsearch is only going to last another few months I think. I believe the security manager will be non-optional in the next major release of Elasticsearch.

That very same release Elasticsearch switched to gradle as its build system. I suspect the reason this works for Elasticsearch is because it doesn't use the builtin support for running tests and instead uses the stuff in here which it has so that it can use Carrot search's Randomized Testing. I can't speculate why that works and the builtin doesn't.

I don't know if that helps anyone.

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

• Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
• Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.