RFR: 8076488: AARCH64: jdk9 fails to build from source
vladimir.kozlov at oracle.com
Wed Apr 22 22:48:02 UTC 2015
Best case scenario:
1. Changes pushed into a Hotspot groups repos (jdk9/hs-comp) using JPRT
and we do Nightly testing on them.
2. Each week on Thursday all changes which passed at least one Nightly
testing are pushed from all groups repos into main repo (jdk9/hs) using
3. Hotspot gatekeeper creates bundles for all platforms from main repo
(jdk9/hs) and start PIT testing which is going whole weekend.
4. Monday-Tuesday SQE analyze PIT results and give yes (or no) on merge
to jdk9/dev. If 'yes' Hotspot gatekeeper pushes changes to jdk9/dev.
So usually it takes one/one-and-half weeks for changes propagate from
jdk9/hs-comp to jdk9/dev.
What happened in last weeks. As you may notice no Hotspot changes were
pushed into jdk9/dev since April 6:
We had severe failures on Windows systems and SQE gave 'no' on merge to
And jdk9/hs-comp was not merged to jdk9/hs between March 31 and April 6
because we had regression in Nightly testing.
Note, this and next week there will be no merge to jdk9/dev due to
technical issues (we will not be able to run PIT testing).
Most likely you will see "Intrinsify ByteBuffer.put" changes in jdk9/dev
only in May.
My suggestion would be to use one of Hotspot group's repo as base for
your work if it includes Hotspot changes.
On 4/22/15 2:15 AM, Andrew Haley wrote:
> On 04/17/2015 06:08 PM, Andrew Haley wrote:
>> On 04/17/2015 05:50 PM, Vladimir Kozlov wrote:
>>> > Ah, no I won't. My patch already fixed this, and (IMO) in a much better
>>> > way. This patch is already in jprt, and will emerge soon, I hope.
>>> Andrew, do you mean the change pushed few days ago as part of 8077615 changes?:
> How does this work? Is it that changes are pushed to hs-comp (by
> JPRT?) tested, and then manually merged at some point in the future?
> I'm thinking about the workflow. It's now Apr 22, and the patch
> "Intrinsify ByteBuffer.put" went into hs-comp on Mar 31. This seems
> like a very long time to wait while developing. It's particularly
> awkward if we have a bug which breaks the build.
> I'm not asking for anything to be changed, just trying to understand
> how I (and other external contributors) should best interact with the
> HotSpot workflow.
More information about the hotspot-dev