RFR(L): 8066153: JEP-JDK-8046155: Test task: cover existing
pavel.punegov at oracle.com
Wed Oct 7 18:49:04 UTC 2015
Thank you, Vladimir.
LogCompilation output processing will signal failure only if we found
that the method was printed when it should not be.
It won't fail if there are no methods that should be printed at all, or
there is a broken output that just wouldn't match regexps.
On 07.10.2015 05:50, Vladimir Kozlov wrote:
> We have test problems with parsing output of LogCompilation and other
> outputs because it could be cut off. I would prefer adding new WB
> events API to record interesting events.
> Otherwise seems fine. Nils should look on this to make sure all
> paths/flags are tested.
> On 9/28/15 8:32 PM, Pavel Punegov wrote:
>> please review the following tests fro JEP 165 Compiler Control.
>> These tests cover both CompileCommand and new directives (through
>> The main idea of tests is to create a one or multiple commands or
>> directives for methods in the pool and execute a test VM with a set of
>> method states (should method be compiled, inlined, printed, etc.). On
>> the end test checks that only correct methods are logged with
>> LogCompilation, or printed via PrintAssembly.
>> webrev: http://cr.openjdk.java.net/~ppunegov/8066153/webrev.00/
More information about the hotspot-compiler-dev