JDK-8210106 : sun/tools/jps/TestJps.java timed out
Type:Bug
Component:core-svc
Sub-Component:tools
Affected Version:12
Priority:P4
Status:Resolved
Resolution:Fixed
OS:linux
CPU:x86_64
Submitted:2018-08-28
Updated:2019-03-07
Resolved:2018-12-10
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed. Resolved: Release in which this issue/RFE has been resolved. Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
Last entry in log:
linux-x64-debug.jdk/jdk-12/fastdebug/bin/jps -J-XX:+UsePerfData -m -V]
Timeout refired 1200 times
Comments
This fix did not work and now the timeout is probably much longer than it should be. See JDK-8220295.
07-03-2019
The default jtreg timeout is set to 2 minutes.
On a local linux-x64-debug build this test is taking ~ 40 seconds.
I'll try 3X the default timeout and see what the mach5 test machines report.
diff --git a/test/jdk/sun/tools/jps/TestJps.java b/test/jdk/sun/tools/jps/TestJps.java
--- a/test/jdk/sun/tools/jps/TestJps.java
+++ b/test/jdk/sun/tools/jps/TestJps.java
@@ -27,7 +27,7 @@
* @modules jdk.jartool/sun.tools.jar
* @build LingeredAppForJps
* @build LingeredApp
- * @run main/othervm TestJps
+ * @run main/othervm/timeout=360 TestJps
*/
05-12-2018
Running this test locally 8 java processes are identified by the jps command.
When run on the mach5 system there are 20 processes.
Running the test locally the maximum jtreg output is exceeded.
Since the test runs through 44 combinations of command line flags there could be
even more buffered output dropped on the mach5 test system.
There might be some merit in increasing the default jtreg timeout for this test.