Skip to content
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

WIP: Don't override OpenJ9 SHA with PR ref #7288

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

AdamBrousseau
Copy link
Contributor

  • When calling test pipelines, the OpenJ9 SHA should
    be used rather than the merge ref. Since the merge
    ref is a moving target, the SHA could change between
    the compile and the test. We need to ensure we are
    testing with the same level of OpenJ9 as we compile
    against.

Fixes #7287
[skip ci]

Signed-off-by: Adam Brousseau [email protected]

- When calling test pipelines, the OpenJ9 SHA should
  be used rather than the merge ref. Since the merge
  ref is a moving target, the SHA could change between
  the compile and the test. We need to ensure we are
  testing with the same level of OpenJ9 as we compile
  against.

Fixes eclipse-openj9#7287
[skip ci]

Signed-off-by: Adam Brousseau <[email protected]>
@AdamBrousseau
Copy link
Contributor Author

@keithc-ca

if (params.ghprbPullId && params.ghprbGhRepository == GHPRB_REPO_OPENJ9) {
SHAS['OPENJ9'] = "origin/pr/${params.ghprbPullId}/merge"
}
echo "Passing test OPenJ9 SHA:${SHAS['OPENJ9']}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: OPenJ9 -> OpenJ9

@AdamBrousseau AdamBrousseau changed the title Don't override OpenJ9 SHA with PR ref WIP: Don't override OpenJ9 SHA with PR ref Sep 30, 2019
@AdamBrousseau
Copy link
Contributor Author

Needs something more. When doing a depends build from the ext repo, the SHA passed to test is from the HEAD of the target branch rather than the merge commit. Marked as WIP for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

PR builds are inconsistent
2 participants