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

Clone reference repository is looking for $HOME #1790

Closed
AdamBrousseau opened this issue May 15, 2020 · 1 comment
Closed

Clone reference repository is looking for $HOME #1790

AdamBrousseau opened this issue May 15, 2020 · 1 comment
Labels
Milestone

Comments

@AdamBrousseau
Copy link
Contributor

Describe the bug
https://github.com/AdoptOpenJDK/openjdk-tests/blame/fb7463af44f406b233def68085a7bfc5f4bb7e83/buildenv/jenkins/testJobTemplate#L204
#1484
I believe when this executes the job actually looks for $HOME/openjdk_cache instead of, for example /home/jenkins/openjdk_cache
I see this error on a machine which has the cache setup

Cloning the remote Git repository
Cloning repository https://github.com/AdoptOpenJDK/openjdk-tests.git
 > git init /home/jenkins/workspace/Test_openjdk8_j9_sanity.functional_ppc64le_linux_Nightly/openjdk-tests # timeout=10
ERROR: Reference path does not exist: $HOME/openjdk_cache

At OpenJ9 we pull this value based on what plaform we are running on as it changes from linux to osx to windows. Hardcoding it to /home/jenkins/openjdk_cache would be a slight improvement but it wouldn't help osx for example.

To Reproduce
Steps to reproduce the behavior (or Grinder rerun link):
Run a test job on a machine which has ~/openjdk_cache vs a machine which does not.

Expected behavior
Should find the cache.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

@AdamBrousseau
Copy link
Contributor Author

My browser decided to double save this.
Dup #1789

@karianna karianna added this to the May 2020 milestone May 15, 2020
@karianna karianna added the bug label May 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants