8230052: MLVM findDeadlock test timed out

Add logging for debugging for the next timeout Reviewed-by: iignatyev, iklam, pchilanomate, dholmes
openjdk · Aug 31, 2020 · d4ef7fae99b8c3595cc28a08744403a2905c6ddd · d4ef7fa
1 parent b8d14fc
commit d4ef7fae99b8c3595cc28a08744403a2905c6ddd
Showing with 1 addition and 1 deletion.

+1 −1 test/hotspot/jtreg/vmTestbase/vm/mlvm/mixed/stress/java/findDeadlock/TestDescription.java
diff --git a/test/hotspot/jtreg/vmTestbase/vm/mlvm/mixed/stress/java/findDeadlock/TestDescription.java b/test/hotspot/jtreg/vmTestbase/vm/mlvm/mixed/stress/java/findDeadlock/TestDescription.java
@@ -44,6 +44,6 @@
  * @build vm.mlvm.mixed.stress.java.findDeadlock.INDIFY_Test
  * @run driver vm.mlvm.share.IndifiedClassesBuilder
  *
- * @run main/othervm vm.mlvm.mixed.stress.java.findDeadlock.INDIFY_Test
+ * @run main/othervm -Xlog:gc,safepoint vm.mlvm.mixed.stress.java.findDeadlock.INDIFY_Test
  */