JDK-8130638 : sun/tools/jps/* tests java.lang.RuntimeException: The line '' does not match pattern '^\\d+\\s+.*': expected true, was false
  • Type: Bug
  • Component: core-svc
  • Affected Version: 9
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: solaris
  • CPU: sparc
  • Submitted: 2015-07-06
  • Updated: 2015-08-26
  • Resolved: 2015-08-26
Related Reports
Duplicate :  
Relates :  
Relates :  
Relates :  
Description
sun/tools/jps/TestJpsClass.java
sun/tools/jps/TestJpsJar.java

JDK under test: (/export/local/aurora/CommonData/JDK_DIR)
java version "1.9.0-internal-fastdebug"
Java(TM) SE Runtime Environment (build 1.9.0-internal-fastdebug-20150703142024.ddaugher.merge_main_to_rt-b00)
Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-internal-fastdebug-20150703142024.ddaugher.merge_main_to_rt-b00, mixed mode)

Exception in thread "main" java.lang.RuntimeException: The line '' does not match pattern '^\\d+\\s+.*': expected true, was false
	at jdk.testlibrary.Asserts.fail(Asserts.java:536)
	at jdk.testlibrary.Asserts.assertTrue(Asserts.java:486)
	at jdk.testlibrary.OutputAnalyzer.shouldMatchByLine(OutputAnalyzer.java:526)
	at jdk.testlibrary.OutputAnalyzer.stdoutShouldMatchByLine(OutputAnalyzer.java:503)
	at jdk.testlibrary.OutputAnalyzer.stdoutShouldMatchByLine(OutputAnalyzer.java:451)
	at JpsHelper.verifyJpsOutput(JpsHelper.java:186)
	at JpsBase.main(JpsBase.java:121)

 stderr: [Exception in thread "main" java.lang.RuntimeException: The line '' does not match pattern '^\\d+\\s+.*': expected true, was false
	at jdk.testlibrary.Asserts.fail(Asserts.java:536)
	at jdk.testlibrary.Asserts.assertTrue(Asserts.java:486)
	at jdk.testlibrary.OutputAnalyzer.shouldMatchByLine(OutputAnalyzer.java:526)
	at jdk.testlibrary.OutputAnalyzer.stdoutShouldMatchByLine(OutputAnalyzer.java:503)
	at jdk.testlibrary.OutputAnalyzer.stdoutShouldMatchByLine(OutputAnalyzer.java:451)
	at JpsHelper.verifyJpsOutput(JpsHelper.java:186)
	at JpsBase.main(JpsBase.java:121)
]
 exitValue = 1

java.lang.RuntimeException: Expected to get exit value of [0]

	at jdk.testlibrary.OutputAnalyzer.shouldHaveExitValue(OutputAnalyzer.java:353)
	at TestJpsClass.main(TestJpsClass.java:62)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:502)
	at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:92)
	at java.lang.Thread.run(Thread.java:745)

JavaTest Message: Test threw exception: java.lang.RuntimeException: Expected to get exit value of [0]

log: 
http://aurora.ru.oracle.com/slot-gw/986534.JAVASE.NIGHTLY.VM.RT_Baseline.2015-07-03-240/results/workDir/sun/tools/jps/TestJpsClass.jtr
http://aurora.ru.oracle.com/slot-gw/986534.JAVASE.NIGHTLY.VM.RT_Baseline.2015-07-03-240/results/workDir/sun/tools/jps/TestJpsJar.jtr

http://aurora.ru.oracle.com/functional/faces/RunDetails.xhtml?names=986534.JAVASE.NIGHTLY.VM.RT_Baseline.2015-07-03-240

Comments
My suspicion, as we have seen with other jps testing issues, is that there are other Java instances running on the machine and jps detects them as well as, or instead of the intended VM. Solaris in particular seems prone to this due to: a) emc agent ~ > pargs 1261 1261: /oem/app/oracle/product/12c/core/12.1.0.4.0/jdk/bin/amd64/java -Xmx128M -XX:Max argv[0]: /oem/app/oracle/product/12c/core/12.1.0.4.0/jdk/bin/amd64/java argv[1]: -Xmx128M argv[2]: -XX:MaxPermSize=96M argv[3]: -server argv[4]: -Djava.security.egd=file:///dev/./urandom argv[5]: -Dsun.lang.ClassLoader.allowArraySyntax=true argv[6]: -XX:-DoEscapeAnalysis argv[7]: -XX:+UseConcMarkSweepGC argv[8]: -XX:+CMSClassUnloadingEnabled argv[9]: -XX:+UseCompressedOops argv[10]: -XX:-UseLWPSynchronization argv[11]: -Dsun.security.pkcs11.enable-solaris=false argv[12]: -Dwatchdog.pid=1255 argv[13]: -cp argv[14]: /oem/app/oracle/product/12c/core/12.1.0.4.0/jdbc/lib/ojdbc5.jar:/oem/app/oracle/product/12c/core/12.1.0.4.0/ucp/lib/ucp.jar:/oem/app/oracle/product/12c/core/12.1.0.4.0/modules/oracle.http_client_11.1.1.jar:/oem/app/oracle/product/12c/core/12.1.0.4.0/lib/xmlparserv2.jar:/oem/app/oracle/product/12c/core/12.1.0.4.0/lib/jsch.jar:/oem/app/oracle/product/12c/core/12.1.0.4.0/lib/optic.jar:/oem/app/oracle/product/12c/core/12.1.0.4.0/modules/oracle.dms_11.1.1/dms.jar:/oem/app/oracle/product/12c/core/12.1.0.4.0/modules/oracle.odl_11.1.1/ojdl.jar:/oem/app/oracle/product/12c/core/12.1.0.4.0/modules/oracle.odl_11.1.1/ojdl2.jar:/oem/app/oracle/product/12c/core/12.1.0.4.0/sysman/jlib/log4j-core.jar:/oem/app/oracle/product/12c/core/12.1.0.4.0/jlib/gcagent_core.jar:/oem/app/oracle/product/12c/core/12.1.0.4.0/sysman/jlib/emagentSDK-intg.jar:/oem/app/oracle/product/12c/core/12.1.0.4.0/sysman/jlib/emagentSDK.jar argv[15]: oracle.sysman.gcagent.tmmain.TMMain b) if running a GUI, the sysmon app ~ > pargs 2351 2351: java -Djava.security.policy=/usr/share/vpanels/java.policy com.oracle.solaris.v argv[0]: java argv[1]: -Djava.security.policy=/usr/share/vpanels/java.policy argv[2]: com.oracle.solaris.vp.client.swing.App argv[3]: sysmon ~ > jps 14647 Jps 1261 TMMain 2351 App
26-08-2015

This reliably fails intermittently :) during mach 5 testing on solaris-x64 and solaris-sparc http://java.se.oracle.com/mach5/view/All/job/9-dev-tier2-solaris-x64-failuresHistory/Failure_History/ http://java.se.oracle.com/mach5/view/All/job/9-dev-tier2-solaris-x64-failuresHistory/Failure_History/
25-08-2015

Test is being run with PrintGCDetails so it may be that is messing up the output parsing.
07-07-2015