-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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-8254920: Application launched with jpackage produced .exe crashes JVM #940
Conversation
👋 Welcome back herrick! A progress list of the required criteria for merging this PR into |
@andyherrick The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
@@ -273,7 +273,8 @@ public static void executeLauncherAndVerifyOutput(JPackageCommand cmd, | |||
String... args) { | |||
AppOutputVerifier av = getVerifier(cmd, args); | |||
if (av != null) { | |||
av.executeAndVerifyOutput(args); | |||
// when running app launchers, clear users environment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about executeLauncher() method? It will not clear the environment.
I'd adjust getVerifier() method instead and store flag to clear launcher environment in JPackageCommand instanceinstead.
Something like this:
public JPackageCommand JPackageCommand.setClearLauncherEnv(boolean value) {
clearLauncherEnv = value;
return this;
}
boolean JPackageCommand.getClearLauncherEnv() {
return clearLauncherEnv;
}
AppOuputVerifier.setClearLauncherEnv(boolean value) {
clearLauncherEnv = value;
}
AppOuputVerifier HelloApp.getVerifier(JPackageCommand cmd, String... args) {
AppOuputVerifier reply = ...;
reply.setClearLauncherEnv(cmd.getClearLauncherEnv());
return reply;
}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
@andyherrick This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. 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 4 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
/integrate |
@andyherrick Since your change was applied there have been 8 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 952abea. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Reviewed-by: asemenyuk, almatvee, kizune
JVM
Progress
Testing
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/940/head:pull/940
$ git checkout pull/940