JDK-8161684 : [testconf] Add VerifyOops' testing into compiler tiers
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 9,11
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2014-01-14
  • Updated: 2024-11-18
  • Resolved: 2020-08-06
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 11 JDK 16
11.0.10Fixed 16 b11Fixed
Related Reports
Blocks :  
Blocks :  
Description
Morris Meyer: I see that we are using DeoptimizeALot as one of the nightly test run parameters - wondering if we should do a run with -Xcomp -XX:+VerifyOops
Morris Meyer: it would take longer - but it VerifyOops worked up a few crashers in the Lambda form code

Comments
Fix Request (11u) This workarounds AOT test failures with -XX:+VerifyOops, and thus makes the testing clean. It can be fixed properly with JDK-8209961 backport later (which would remove the added hunk). Patch applies cleanly to 11u, compiler/aot tests fail with -XX:+VerifyOops before this patch, and pass with it. compiler/aot tests still run without -XX:+VerifyOops. tier1 passes with/without -XX:+VerifyOops.
05-10-2020

URL: https://hg.openjdk.java.net/jdk/jdk/rev/4484115c646d User: lmesnik Date: 2020-08-06 20:42:49 +0000
06-08-2020

The AOT doesn't work with VerifyOops, otherwise we can add it to tier7/8 testing.
27-07-2020

[~lmesnik]?
07-07-2020

that part I knew, what I meant is given the known problems w/ VerifyOops are fixed we can re-do the experiment done in 2018-06, or in other(actually same) words: [~lmesnik], could you please run some tests/test-configuration w/ VerifyOops enabled to check if it makes sense to include in our regular testing?
16-01-2019

Tests are not executed with VerifyOops. It is not used in any of hotspot tiers.
16-01-2019

[~lmesnik], could you please run some tests/test-configuration w/ VerifyOops enabled to check if it makes sense to include in our regular testing?
12-06-2018

w/ tiered testing, I'd say we might want to have such configuration somewhere in ATR tiers.
12-05-2017

Is this in progress? Setting fixVersion to JDK 10.
26-01-2017