JDK-8158276 : [TESTBUG] Two defmeth tests fail with ICCE
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 9
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2016-05-31
  • Updated: 2016-07-19
  • Resolved: 2016-07-19
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 9
9Fixed
Related Reports
Relates :  
JDK-8143320 - Many vm/runtime/defmeth/scenarios/ConflictingDefaults_v50_none_direct_noredefine fail with ICCE, ExitCode: 97
Relates :  
JDK-8145148 - InterfaceMethod CP entry pointing to a class should cause ICCE
Sub Tasks
JDK-8159981 :  
Quarantine vm/runtime/defmeth/scenarios/Stress_* tests - Closed
Description
RULE "vm/runtime/defmeth/scenarios/Stress_noredefine" Exception nsk.share.TestFailure: Some of the worker threads failed. 

RULE "vm/runtime/defmeth/scenarios/Stress_noredefine" ExitCode 1 

RULE "vm/runtime/defmeth/scenarios/Stress_redefine" Exception nsk.share.TestFailure: Some of the worker threads failed. 

RULE "vm/runtime/defmeth/scenarios/Stress_redefine" ExitCode 1

Fixing these separately from 8143320.
Comments
Worker #1/5: FAILED: StaticMethodsTest{ver=51; flags=0; redefine=false; execMode=INVOKE_GENERIC} (executed: 11) Worker #3/5: FAILED: StaticMethodsTest{ver=51; flags=2048; redefine=false; execMode=INVOKE_EXACT} (executed: 15) Worker #4/5: FAILED: StaticMethodsTest{ver=51; flags=32; redefine=false; execMode=INVOKE_EXACT} (executed: 1) Investigating StaticMethodsTest test
19-07-2016
I will take a look at this bug
18-07-2016
Not really, Leonid has fixed the vmtestbase build so my change has been applied and this two tests have been finally quarantined until I or someone else will provide the fix
08-07-2016
Is Leonid fixing this bug in the tests?
08-07-2016
These test failures were reported back on 2016.05.31. Can someone explain why these test failures have not been quarantined yet? It's been almost 2 months.
20-06-2016
Have not looked on it yet
16-06-2016
Any progress on this? It's failing every night
16-06-2016
I think [~stsmirno] said he was going to fix these. I couldn't find the code.
02-06-2016