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

Enable macos test build #77

Closed
smlambert opened this issue Jul 7, 2017 · 7 comments
Closed

Enable macos test build #77

smlambert opened this issue Jul 7, 2017 · 7 comments
Assignees

Comments

@smlambert
Copy link
Contributor

Now that we have some macs for testing, we can enable a test build (https://ci.adoptopenjdk.net/view/OpenJDK%20tests/job/openjdk_test_x86-64_macos/) that will be triggered to run all the tests upon successful completion of the image build (https://ci.adoptopenjdk.net/job/openjdk_build_x86-64_macos/).

@smlambert smlambert self-assigned this Jul 7, 2017
@sophia-guo
Copy link
Contributor

Jenkins build got "wget: command not found"
Login in as Jenkins wget works fine. "Which wget" will get this wget is a softlink. Using absolute path of wget in jenkins build will also work.

@bblondin we need to update "Configure System" and add environment variables to update PATH environment to include path /usr/local/Cellar/wget/1.19.1_1/bin/, probably do the same thing for all slave machines.

@gdams
Copy link
Member

gdams commented Jul 18, 2017

okay so for some reason jenkins doesn't seem to have /usr/local/bin/ in the path. That's why wget is not getting detected

@bblondin
Copy link
Contributor

wget is on the path for Jenkins:

sh-3.2# su - jenkins
DXU773:~ jenkins$ which wget
/usr/local/bin/wget

Error: /Users/jenkins/workspace/openjdk_test_x86-64_macos/openjdk-test/get.sh: line 33: wget: command not found

inside get.sh you should have code that sets the path: ie.

if [[ "$(uname)" = Darwin ]] ; then
        export PATH=$PATH:/usr/local/bin/
fi

I see that you have attempted to call wget directly from its real path in get.sh (/usr/local/Cellar/wget/1.19.1_1/bin/wget http://download.forge.ow2.org/asm/asm-5.0.1.jar) for one of the wget calls. if you are going to do this it should be a call to /usr/local/bin/ as the version of wget (and other tools) will change in the future.

@bblondin bblondin self-assigned this Jul 18, 2017
@sophia-guo
Copy link
Contributor

sophia-guo commented Jul 18, 2017

I would prefer to set this PATH by environment variable instead of setting it in the script file. The reason is this is a jenkins environment setting, which should not be handled by shell script. The advantage is in this way it will not be needed to be exported for each test build.

Login in as jenkins wget is on the path for Jenkins. However if you put "which wget" in script shell and trigger the build by jenkins interface you will see "no wget command". I believe login in as jenkins the environment variables is different from the jenkins system properties from Manage Jenkins from UI? Could you check the System properties using Manage Jenkins?

Calling wget directly from its real path in get.sh (/usr/local/Cellar/wget/1.19.1_1/bin/wget http://download.forge.ow2.org/asm/asm-5.0.1.jar) is only to help to figure out what the issue is.

@bblondin
Copy link
Contributor

ok added to the two test macs

@gdams
Copy link
Member

gdams commented Aug 2, 2017

@smlambert can this be closed now?

@smlambert
Copy link
Contributor Author

Yes, closed. Mac test builds are running to completion: https://ci.adoptopenjdk.net/view/OpenJDK%20tests/job/openjdk_test_x86-64_macos/

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

No branches or pull requests

4 participants