I'll need a sponsor for the attached
patch.
It probably should wait for the rdp repos to be forked.
I'll file two followup bugs based on the discussions.
- one to continue investigation of why the exclude001 test
takes so long
- one to improve the vmTestbase/nsk tests setting of the
jtreg /timeout arg
On 6/25/18 1:20 PM, 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:
|
--- 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