jdk8-b122: HotSpot (II)
Alejandro E Murillo
alejandro.murillo at oracle.com
Tue Dec 31 15:38:08 PST 2013
hs25-b65 has been integrated into jdk8-b122.
http://hg.openjdk.java.net/jdk8/jdk8/rev/347009c58816
http://hg.openjdk.java.net/jdk8/jdk8/corba/rev/0cd687347540
http://hg.openjdk.java.net/jdk8/jdk8/hotspot/rev/d3521d8e562a
http://hg.openjdk.java.net/jdk8/jdk8/jaxp/rev/93bf25903af0
http://hg.openjdk.java.net/jdk8/jdk8/jaxws/rev/bc622ba563f9
http://hg.openjdk.java.net/jdk8/jdk8/jdk/rev/e1499442453b
http://hg.openjdk.java.net/jdk8/jdk8/langtools/rev/232b9cf6303a
http://hg.openjdk.java.net/jdk8/jdk8/nashorn/rev/9d112a0e7df7
Component : VM
Status : 0 major failures, 0 minor failures
Date : 12/24/2013 at 17:00 MSK
Tested By : VM SQE &dmitry.fazunenko at oracle.com
Cost(total man-days): 1
Workspace : 2013-12-27-154212.amurillo.hs25-b65-snapshot
Bundles : 2013-12-27-154212.amurillo.hs25-b65-snapshot
Platforms :
Others
Tests :/net/sqenfs-1.sfbay/export1/comp/vm/testbase/
Log :http://surl.us.oracle.com/pit_jdk8_b122_2
Browsers : NA
Patches : NA
Number of Tests Executed : 202485 passed tests, 2242 failed tests (37 new failures)
Bug verification status:
======================================
Tested, Pass:
Tested, Pass (partial fixes):
Tested, Fail:
Untested bug fixes:
Setup is not available:
8027804: JCK resolveMethod test fails expecting AbstractMethodError
8029233: Update copyright year to match last edit in jdk8 hotspot repository for 2013
8030633: nsk/jvmti/RedefineClasses/StressRedefine failed invalid method ordering length on Solaris
8030752: new hotspot build - hs25-b65
New bugs filed: JDK-8031089
Bugs in PIT build:
Bugs in earlier promoted build:
Number of PIT requested: 1
Integration target J2SE build number: JDK8 b122
Issues and Notes:
This is PIT for HS25 b65 for JDK8 b122. Only 2/3 of jobs have been completed.
Taking into account that the number of fixed bug is small, it's ok.
The majority of SQE engineers are on the New Year Break right now, so we cannot provide comprehensive analysis of the failures.
I haven't seen any critical issue among the results, so I say Go.
--
Alejandro
More information about the jdk8-dev
mailing list