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

Added functionality for testScript.sh to run a test on a built JDK #943

Merged
merged 1 commit into from
Sep 30, 2019

Conversation

Willsparker
Copy link
Contributor

Ref: #939

Currently only implemented for the unix playbooks. If the option is specified, the script will run the MachineInfo test against a version of JDK8 that is built on the VM, having been setup by the playbook. It won't allow a test to be ran unless a JDK is built.

#!/bin/bash

mv /vagrant/pbTestScripts/workspace/build/src/build/linux-x86_64-normal-server-release/images/jdk8* ~
export TEST_JDK_HOME=$(find ~ -maxdepth 1 -type d -name "*jdk8u*"|grep -v ".*jre.*")
Copy link
Member

Choose a reason for hiding this comment

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

Any reason not to just set TEST_JDK_HOME to /vagrant/pbTestScripts/workspace/build/src/build/linux-x86_64-normal-server-release/images/jdk8*?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

There's 2 directories in there- the JDK to test, and the JRE, which has the same name but -jre at the end

@karianna karianna added this to the September 2019 milestone Sep 20, 2019
@karianna karianna requested a review from sxa September 20, 2019 23:39
@sxa sxa merged commit 4eb9902 into adoptium:master Sep 30, 2019
@Willsparker Willsparker deleted the 939 branch October 7, 2019 11:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants