jdk10/hs integration status

[David Holmes]

Hi Jesper,

On 2/09/2017 8:15 PM, jesper.wilhelmsson at oracle.com wrote:
> Hi,
> 
> After going through the results of our nightlies it seems we are in fairly good shape for integration. There was one issue with a typo in a recent fix that caused some failures, this issue was resolved yesterday just after the nightly snapshot was taken.

The JPRT job that was used for the nightly testing was not valid. The 
repos were out of sync due to a re-run with an intervening integration 
job. The MaxRAMFraction failures in the tools tests below were caused by 
that.

David
-----

> 
> There is currently one issue that I didn't recognise and at the moment it is marked as an integration blocker:
> 
> JDK-8187124 <https://bugs.openjdk.java.net/browse/JDK-8187124>	
> TestInterpreterMethodEntries.java: Unable to create shared archive file <https://bugs.openjdk.java.net/browse/JDK-8187124>
> 
> This could as well be a problem with the test execution in which case it is not a blocker, but someone needs to look into the details here.
> 
> 
> There are four test failures that looks slightly different:
> tools/jar/modularJar/Basic.java
> tools/jar/multiRelease/ApiValidatorTest.java
> tools/jar/multiRelease/Basic.java
> tools/launcher/InfoStreams.java
> 
> These four tests fails because they get a warning on stderr:
> Option MaxRAMFraction was deprecated in version 10.0 and will likely be removed in a future release.
> I do not consider this a blocker for integration, bug filed: JDK-8187125 <https://bugs.openjdk.java.net/browse/JDK-8187125>
> 
> 
> JDK10/hs now has restricted write access. Basically it is locked but in order to fix any urgent issues that might pop up over the next couple of days these people have write access: Vladimir Kozlov, Dan Daugherty, Stefan Karlsson, and myself.
> 
> /Jesper
>