JDK-8039450 : [TESTBUG] Integrate tests on VM access checks into regular test execution
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 8
  • Priority: P3
  • Status: Closed
  • Resolution: Won't Fix
  • Submitted: 2013-06-18
  • Updated: 2017-05-15
  • Resolved: 2017-05-15
Related Reports
Relates :  
JDK-8145148 - InterfaceMethod CP entry pointing to a class should cause ICCE
Relates :  
JDK-8087223 - InterfaceMethod CP entry pointing to a class should cause ICCE
Relates :  
JDK-8025592 - vm invocation tests assert: initialized <= length
Description
Need to integrate existing tests on VM access checks into VM testbase.

There are 3 sets of tests:
  - invokevirtual 
  - invokeinterface
  - invokespecial

How to run:
  $ export JDK=<path_to_tested_jdk>
  $ export CLASSFILE_VER=52

  $ bash run.sh invokevirtual.Generator
  $ bash run.sh invokeinterface.Generator
  $ bash run.sh invokespecial.Generator

It is sensible to test all major class file versions:
 - 45.3 (1.1)
 - 46 (1.2)
 - 47(1.3)
 - 48 (1.4)
 - 49 (1.5)
 - 50 (1.6)
 - 51 (1.7)
 - 52 (1.8).

Archive: 
  http://vmsqe.ru.oracle.com/home/vi158347/INVOKE_2009-02-10.tgz
Comments
As per David Holmes' comments, closing as WNF because there are several additional test suites that are more directed.
15-05-2017
FYI the invokevirtual tests have some failures when run against current JDK and Classfile version <=50.
05-04-2017
These tests seem to be a "work in progress" and are 7 years old! It would be very difficult to determine the exact coverage these tests provide and what gaps still exist. Simply porting them to the existing test frameworks (e.g. jtreg) would take a good 7-10 days of solid work IMHO. There is also a tension between a fully comprehensive set of invocation tests like these were attempting to be, and the addition of incremental tests as functionality changes or is added. We added default methods tests as a separate test suite. We also added private interface method tests as a distinct set of tests. With the nestmate work I am also adding specific invocation tests within the nestmate test hierarchy - because it is much easier and clearer to do so in that context than to try and fit in with existing tests.
05-04-2017
Given changes in 8 for private interface methods, static interface methods and default methods, I wonder if these tests are still applicable or whether they need a major rework, or whether we already covered things with the defmeth tests? This is also somewhat related to JDK 10 work on nestmates as we will be modifying invokespecial to support nestmates. Karen: what do you think? Is there still value in these tests or do we just close this?
08-02-2017
e.g Does this bug come from running these tests?
28-10-2015
Are there existing tests that cover the functionality tested by these? Do we have good coverage of invoke* operations with the defmeth tests? There have been bugs filed covering invoke* operation behavior. Would integrating the test cases cover what is tested with these tests?
28-10-2015
I know we don't have anyone to do this now but since we've been told to run these tests, it would be good to have them in some repository so that they are maintained. ie. continue to work over time.
28-10-2015