JDK-8158760 : java/lang/management/MemoryMXBean/PendingAllGC.sh: Unexpected finalized objects: Current finalized = 51 Current pending = 55 but expected = 0
  • Type: Bug
  • Component: core-svc
  • Sub-Component: java.lang.management
  • Affected Version: 9
  • Priority: P4
  • Status: Resolved
  • Resolution: Duplicate
  • Submitted: 2016-06-06
  • Updated: 2016-11-17
  • Resolved: 2016-06-24
Related Reports
Duplicate :  
JDK-8158837 - java/lang/management/MemoryMXBean/Pending.java fails with -limitmods
Relates :  
JDK-8169836 - ProblemList update for java/lang/management/MemoryMXBean/PendingAllGC.sh
Relates :  
JDK-8158837 - java/lang/management/MemoryMXBean/Pending.java fails with -limitmods
Description
jdk9 VM PIT.

java/lang/management/MemoryMXBean/PendingAllGC.sh:

----------System.out:(5/285)----------
runOne Pending
Number of objects pending for finalization:
   Before creating object: Current finalized = 0 Current pending = 0
   Afer creating objects with no ref: Current finalized = 0 Current pending = 0
   Afer creating objects with ref: Current finalized = 0 Current pending = 0
----------System.err:(4/265)----------
Exception in thread "main" java.lang.RuntimeException: Unexpected finalized objects: Current finalized = 51 Current pending = 55 but expected = 0
	at Pending.checkFinalizerCount(Pending.java:146)
	at Pending.test(Pending.java:113)
	at Pending.main(Pending.java:71)
----------------------------
Failed two times on Linux-x86 on two different hosts.
Comments
RULE "java/lang/management/MemoryMXBean/PendingAllGC.sh" Exception java.lang.RuntimeException: Unexpected finalized objects: Current finalized = ... Current pending = ... but expected = ...
05-07-2016
Same issue as JDK-8158837 as this test script only runs with varying options, the Pending.java test failing due to JDK-8158837
24-06-2016
Quarantined together with JDK-8158837 http://hg.openjdk.java.net/jdk9/hs/jdk/rev/9cd02dc23e0b
22-06-2016
This test failure mode was reported 2 weeks ago. Why hasn't this test been quarantined?
20-06-2016
I knew I'd seen this test mentioned recently - see JDK-8158837.
07-06-2016
Seems to me to be a test issue - moving to core-svc -> java.lang.management
07-06-2016
This is actually an intermittent failure. It passed in the rerun. But needs to be fixed ASAP, as it will start to create noise in mach5
06-06-2016
Sanity testing before pushing last week jdk9/hs snapshot into jdk9/dev shows that this test will fail in mach5 after I push the snapshot: http://scaaa637.us.oracle.com//archive/2016/06/2016-06-06-165814.amurillo.jdk9-dev-09_26_24-sanity/logs/linux_i586_3.8-product-c2-jdk_management.log so it needs to be excluded in jdk9/dev as well. Who's is the owner of that test?
06-06-2016