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
JDK-8255612: Explicitly disable dtrace for Oracle OpenJDK Linux builds #946
Conversation
|
@erikj79 This change now passes all automated pre-integration checks. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 16 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.
|
/integrate |
@erikj79 Since your change was applied there have been 16 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 3fd8216. |
The OpenJDK build on Linux will determine if the JVM feature "dtrace" should be enabled based on the availability of dtrace on the build host. For Oracle produced OpenJDK builds, we implicitly had this disabled because our build environment didn't have it installed. Rather than having to trust the build host to not have dtrace installed, we would like to make this setting explicit. We don't want to change the default behavior of OpenJDK, so we are adding this configure flag to the jib-profiles.js configuration where appropriate, so it only affects Oracle produced builds.
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/946/head:pull/946
$ git checkout pull/946