DeadlockDetectionTest.java fails due to expected output missing

The test serviceability/sa/DeadlockDetectionTest.java started failing in the hs nightly of 2016-03-23. The reason of the failure is that the output expected by the test is not found. Please see the excerpt below:

Attaching to process ID 83984, please wait...
Debugger attached successfully.
Server compiler detected.
JVM version is 9-internal+0-2016-03-23-043254.amurillo.jdk9-hs-jigsaw-m3-snapshot
Not available on Darwin

Attaching to process ID 83984, please wait...
Debugger attached successfully.
Server compiler detected.
JVM version is 9-internal+0-2016-03-23-043254.amurillo.jdk9-hs-jigsaw-m3-snapshot
Not available on Darwin

----------System.err:(25/1284)----------
 stdout: [Attaching to process ID 83984, please wait...
Debugger attached successfully.
Server compiler detected.
JVM version is 9-internal+0-2016-03-23-043254.amurillo.jdk9-hs-jigsaw-m3-snapshot
Not available on Darwin
];
 stderr: []
 exitValue = 0

java.lang.RuntimeException: 'Found a total of 1 deadlock.' missing from stdout/stderr

at jdk.test.lib.OutputAnalyzer.shouldContain(OutputAnalyzer.java:138)
at DeadlockDetectionTest.main(DeadlockDetectionTest.java:105)
at sun.reflect.NativeMethodAccessorImpl.invoke0(java.base@9-internal/Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(java.base@9-internal/NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(java.base@9-internal/DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(java.base@9-internal/Method.java:531)
at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:110)
at java.lang.Thread.run(java.base@9-internal/Thread.java:804)

JavaTest Message: Test threw exception: java.lang.RuntimeException: 'Found a total of 1 deadlock.' missing from stdout/stderr

JavaTest Message: shutting down test


The failure appears only on macosx. The likely cause of the failure is that the the functionality necessary to perform the deadlock analysis is not available. Maybe changing the test to not execute on macosx is sufficient to solve the problem.