-
Notifications
You must be signed in to change notification settings - Fork 77
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
Extension test change is not picked up by PR builds. #613
Comments
@JasonFengJ9 Issues should be created in the OpenJ9 repo for proper tracking. That is where the PR build code is as well. Looking at a grinder, the parameters for test are JDK_REPO and JDK_BRANCH. At the top level job (https://openj9-jenkins.osuosl.org/job/Pipeline_Build_Test_JDK11_aarch64_linux/1475/console) we see |
So the ask is that any PR build that changes code in extensions, should pass JDK_REPO & JDK_BRANCH to the test jobs. Correct? I'm not sure I was thinking of the same known issue originally. |
I think the original issue was |
Again, that's in the wrong repo. Pls open an issue at https://github.com/eclipse-openj9/openj9/issues |
It was tracked at infrastructure/issues/7363 unless an openj9 issue helps. |
Everything here is open source, the code that needs to be changed is open source in the OpenJ9 repo. |
ibmruntimes/openj9-openjdk-jdk11#670 (comment)
FYI @AdamBrousseau
The text was updated successfully, but these errors were encountered: