- 
    Bug 
- 
    Resolution: Fixed
- 
     P4 P4
- 
    11, 12
- 
        b20
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build | 
|---|---|---|---|---|---|---|
| JDK-8272887 | 11.0.14-oracle | Vaibhav Choudhary | P4 | Resolved | Fixed | b01 | 
| JDK-8272913 | 11.0.13 | Zhengyu Gu | P4 | Resolved | Fixed | b04 | 
                    During code review of JDK-8213707, JC Beyler pointed out except002 and except003 also have wrong class names.
http://mail.openjdk.java.net/pipermail/hotspot-dev/2018-November/035156.html
http://mail.openjdk.java.net/pipermail/hotspot-dev/2018-November/035156.html
- backported by
- 
                    JDK-8272887 [TEST] Wrong classname in vmTestbase/nsk/stress/except/except002 and except003 -           
- Resolved
 
-         
- 
                    JDK-8272913 [TEST] Wrong classname in vmTestbase/nsk/stress/except/except002 and except003 -           
- Resolved
 
-         
- relates to
- 
                    JDK-8213721 [Graal] Tests vmTestbase/nsk/stress/except/except* may be encountering SEGV during out-of-memory conditions -           
- Resolved
 
-         
 
        