-
Notifications
You must be signed in to change notification settings - Fork 712
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
Use --with-openssl=fetched on Windows #14343
Conversation
jenkins compile win,win32 jdk8 depends ibmruntimes/openj9-openjdk-jdk8#543 |
jenkins compile win32 jdk8 depends ibmruntimes/openj9-openjdk-jdk8#543 |
* variables-functions.groovy: look for '--with-openssl' option in EXTRA_CONFIGURE_OPTIONS; don't download if absent, 'fetched' or 'system' * defaults.yml: update configure options Signed-off-by: Keith W. Campbell <keithc@ca.ibm.com>
Signed-off-by: Keith W. Campbell <keithc@ca.ibm.com>
jenkins compile win,win32 jdk8 depends ibmruntimes/openj9-openjdk-jdk8#543 |
jenkins compile win jdk11 depends ibmruntimes/openj9-openjdk-jdk11#471 |
jenkins compile win jdk17 depends ibmruntimes/openj9-openjdk-jdk17#61 |
jenkins compile win jdk18 depends ibmruntimes/openj9-openjdk-jdk18#9 |
jenkins compile win jdknext depends ibmruntimes/openj9-openjdk-jdk#395 |
jenkins compile all jdk8 depends ibmruntimes/openj9-openjdk-jdk8#543 |
jenkins compile all jdk11 depends ibmruntimes/openj9-openjdk-jdk11#471 |
jenkins compile all jdk17 depends ibmruntimes/openj9-openjdk-jdk17#61 |
There are problems on other platforms. |
jenkins compile all jdk8 depends ibmruntimes/openj9-openjdk-jdk8#543 |
jenkins compile all jdk11 depends ibmruntimes/openj9-openjdk-jdk11#471 |
jenkins compile all jdk17 depends ibmruntimes/openj9-openjdk-jdk17#61 |
AIX seems to have some strange (unrelated?) problems:
Both openssl and openj9 appear to have compiled successfully. |
jenkins compile aix jdk11 depends ibmruntimes/openj9-openjdk-jdk11#471 |
@jdekonin the AIX build that failed happened on p8-java1-ibm03. Maybe these machines aren't as ready to go as we hoped. Or maybe they are just faster and expose a timing hole. The failure isn't new, we see it occasionally, but not very often. |
The new build is running on the same machine, we'll see if it works. Either way, it's not an issue with this PR. |
Issue: #14302: