-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8348888: tier1 closed build failure on Windows after JDK-8348348 #23340
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
Conversation
|
👋 Welcome back jiangli! A progress list of the required criteria for merging this PR into |
|
@jianglizhou 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 3 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 |
|
@jianglizhou 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. |
|
@alexeysemenyukoracle please review |
kevinrushforth
left a comment
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.
Since the only failures we've seen are on Windows, this fix should work. Alexey will be able to confirm this.
|
Will wait for @alexeysemenyukoracle's confirmation for testing. Thanks! |
It doesn't look like it complains about undefined DEF_STATIC_JNI_OnLoad |
The compilation error I saw did. A Mach5 job I submitted passed in one case where it was failing, so I think the fix is good. @alexeysemenyukoracle Please confirm, though. |
liach
left a comment
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.
Closed windows uninstaller build affected by the original issue now builds successfully. This patch should be fine.
|
/reviewers 2 reviewer |
|
I believe it complained about the way DEF_STATIC_JNI_OnLoad is defined. That is why disabling the usage of DEF_STATIC_JNI_OnLoad fixes the problem. |
That probably describes the issue more clear. Thumbs up. |
@kevinrushforth Thanks! |
|
Thanks all, for reviews and testing! I created JDK-8348892 to follow up on the issue. |
|
/integrate |
|
Going to push as commit 1efae9a.
Your commit was automatically rebased without conflicts. |
|
@jianglizhou Pushed as commit 1efae9a. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Please review this workaround for the compiler error on Windows. This error occurs in closed build with custom make logic that uses zip_util.c. The error indicates
DEF_STATIC_JNI_OnLoadis not defined, thus disable the macro on Windows for now until the cause is fully understood.Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/23340/head:pull/23340$ git checkout pull/23340Update a local copy of the PR:
$ git checkout pull/23340$ git pull https://git.openjdk.org/jdk.git pull/23340/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 23340View PR using the GUI difftool:
$ git pr show -t 23340Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/23340.diff
Using Webrev
Link to Webrev Comment