Clarification regarding the GitHub Actions pre-submit testing

Alan Bateman Alan.Bateman at
Thu Mar 18 11:32:01 UTC 2021

On 18/03/2021 08:29, Aleksey Shipilev wrote:
> :
> It is fine to have some platforms build-broken when projects are 
> developed outside the mainline. But when the contribution to the 
> mainline happens, I think it is fair to ask to meet this -- quite low! 
> -- standard of being buildable everywhere. Unless, of course, there is 
> a sound reason why it is complicated to do. In that case, I would hope 
> that porters get notified about these issues before the integration 
> happens, so they can implement missing parts sooner
"build everywhere" is a high bar in the context of JEPs from big 
projects such as Project Valhalla or Loom that may have a lot of 
architecture specific code. You've listed building of hotspot on 
linux-ppc64le, linux-s390x, and a few others as being enabled for the 
Github Actions now but I wouldn't expect JEPs from these projects to 
have to wait for these ports. If the ports are done before integration 
then great, if they happen a few weeks or months after integration then 
that might be okay too. Inviting maintainers of ports to get involved at 
an appropriate time is reasonable but if the port is not complete then I 
don't think it should be a blocker for integration.


More information about the jdk-dev mailing list