-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JDK16 extension changes to enable OJDK MHs #29
Conversation
We don't need the PR, builds can depend on the branch directly. |
Ok, looks like I was wrong. I guess we can't use a branch from a fork. |
8d4accf
to
2b6a8bd
Compare
2b6a8bd
to
add04fe
Compare
add04fe
to
537c4cd
Compare
537c4cd
to
dad598a
Compare
dad598a
to
ac5e7fd
Compare
1ae3d7f
to
5dc2e6f
Compare
478e4d1
to
f6dfff1
Compare
This reverts commit 5d554a1.
…outside the arity range Reviewed-by: mchung
f6dfff1
to
f6e2b25
Compare
I suspect that all the bindCaller failures in sanity.openjdk will be fixed by eclipse-openj9/openj9#12716, will test with this PR to verify |
Tested locally that all sanity.openjdk test failures due to bindCaller is fixed by eclipse-openj9/openj9#12716 |
extended.functional update:
|
update: latest build of OJDK MH for Java 17 extended.system |
@pshipton can we merge this? The jdk16 excludes were merged |
See the failures in https://openj9-jenkins.osuosl.org/job/Pipeline-Build-Test-JDK16/44/ |
The extended.functional testvmcheck failures occur on Java 11 as well, so not related to OJDK MH. |
@fengxue-IS Is |
no, the JIT failure has been excluded, |
New one The following re-occurred. This adds overhead to daily triage, and the failures are archiving artifacts which may cause a space issue. |
New one Re-occurred, same as previous comment. |
This PR is created to launch OpenJ9 PR build jobs with OJDK MHs enabled in OpenJ9.
It should not be merged.