JDK-8024634 : gc/startup_warnings tests can fail due to unrelated warnings
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: hs25
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2013-09-11
  • Updated: 2013-10-22
  • Resolved: 2013-10-15
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.

To download the current JDK release, click here.
JDK 8 Other
8Fixed hs25Fixed
Related Reports
Relates :  
JDK-8006398 - Add regression tests for deprectated GCs
Description
Test:
gc/startup_warnings/TestParNewCMS.java

Failure:
Test threw exception: java.lang.RuntimeException: 'warning' found in stderr


 stderr: [Java HotSpot(TM) 64-Bit Server VM warning: failed to remove stale attach pid file at /tmp/.java_pid26357
java version "1.8.0-ea-fastdebug"
Comments
Will adjust the tests to avoid catching random warnings.
23-09-2013
This warning is generated when the attach mechanism is blocked by stale pid-files which it cannot remove, unfortunately this is a limitation in the current design of the attach mechanism. I agree with John, the test must be updated to handle warnings.
23-09-2013
Giving this to svc since they introduced the warning in the attach code.
20-09-2013
GC startup_warnings testing can be easily modified. But it's better off let runtime take a look the failure first. Transferring to rt.
20-09-2013
All the startup_warnings tests should be changed to fail only when a warning directly related to the condition being checked occurs; other warnings should be ignored.
11-09-2013
This is not the warning the test is looking for. The intention of the test is to look for a warning about the ParNew being used together CMS, which is a valid combination. In this case, the warning is because the function AttachListener::vm_start in os/solaris/vm/attachListener_linux.cpp got -1 from the call to unlink. Unfortunately, the code does not print the errno in the warning, so it is hard to say why the call to unlink the fail. There is most likely a problem with the host burgc09. Anyway, this is not a GC bug and has nothing to do with the test.
11-09-2013