I'm also wondering how fast this test runs on other platforms and when passing on solaris-sparc. 5 minutes already seems like a long time for this test. There could be an underlying issue that needs to be addressed.

Chris

On 6/25/18 11:00 AM, serguei.spit...@oracle.com wrote:
Hi Gary,

It looks Okay.
But I'm curious when this started failing and what triggered it to fail?

Thanks,
Serguei


On 6/25/18 10:20, Gary Adams wrote:
The exclude001 test times out on solaris sparc debug builds.

Basically, this test is all about tracing method calls and introduces
exclude filters to reduce the callbacks to a select set of packages.
The time spent tracing/filtering method callbacks is purely a function
of the number of methods that are processed. On this particularly slow
target platform, more time is needed before issuing a timeout.

  Issue: https://bugs.openjdk.java.net/browse/JDK-8205508

Proposed fix:
diff --git a/test/hotspot/jtreg/vmTestbase/nsk/jdb/exclude/exclude001/exclude001.javab/test/hotspot/jtreg/vmTestbase/nsk/jdb/exclude/exclude001/exclude001.java
--- a/test/hotspot/jtreg/vmTestbase/nsk/jdb/exclude/exclude001/exclude001.java
+++ b/test/hotspot/jtreg/vmTestbase/nsk/jdb/exclude/exclude001/exclude001.java
@@ -63,7 +63,7 @@
  * nsk.jdb.exclude.exclude001.exclude001a
  * @run main/othervm PropertyResolvingWrapper nsk.jdb.exclude.exclude001.exclude001
  * -arch=${os.family}-${os.simpleArch}
- * -waittime=5
+ * -waittime=7
  * -debugee.vmkind=java
  * -transport.address=dynamic
  * -jdb=${test.jdk}/bin/jdb




Reply via email to