- relates to
-
JDK-8193639 tests failing intermittently with Error attaching to process: Can't create thread_db agent! on Solaris
- Open
-
JDK-8202884 SA: Attach/detach might fail on Linux if debugee application create/destroy threads during attaching
- Resolved
-
JDK-8204994 SA might fail to attach to process with "Windbg Error: WaitForEvent failed"
- Resolved
-
JDK-8203364 Some serviceability/sa/ tests intermittently fail with java.io.IOException: LingeredApp terminated with non-zero exit code 3
- Resolved
-
JDK-8210558 serviceability/sa/TestJhsdbJstackLock.java fails to find '^\s+- waiting to lock <0x[0-9a-f]+> \(a java\.lang\.Class ...'
- Resolved
-
JDK-8197591 Tests failing with App waiting timeout
- Closed
-
JDK-8200217 SA: serviceability/sa/ClhsdbJstack.java fails with Test ERROR java.lang.RuntimeException: 'LingeredApp.main' missing from stdout/stderr
- Closed
-
JDK-8211923 [Testbug] serviceability/sa/ClhsdbFindPC.java ArrayIndexOutOfBoundsException: Index 1 out of bounds for length 1
- Closed
-
JDK-8203836 Test serviceability/sa/ClhsdbWhere.java fails to find stacktrace for main
- Closed
-
JDK-8204757 SA: Jstack might fail read stacktrace because of incorrect parameter in codeNMethod.getMetadataAt(int)
- Closed
-
JDK-8207914 TestClhsdbJstackLock.java fails intermittently
- Closed
-
JDK-8212209 Test serviceability/sa/ClhsdbCDSCore.java fails because core file size = 0
- Closed
Umbrella bug for all SA failures in tier1
SA tests are very unstable on all platforms and should not be part of tier1 testing. See linked bugs for details.
(7 relates to)