-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8305846: Support compilation in Proc test utility #13425
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 weijun! A progress list of the required criteria for merging this PR into |
| return this; | ||
| } | ||
| // Compile as well | ||
| public Proc compile() throws IOException { |
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.
Why "throws IOException" ? I'm surprised javac doesn't say it can't be thrown.
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.
Oops, I'll remove it.
| String fullcp() { | ||
| if (cp == null) { | ||
| return System.getProperty("test.class.path") + File.pathSeparator + | ||
| System.getProperty("test.src.path"); |
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.
Pre-existing by why is the src path put in the classpath?
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.
I don't remember exactly. Maybe it allows you to read a resource.
| if (!comp) { | ||
| throw new IOException("Compilation error"); | ||
| } |
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.
Seems an odd use of IOException and not very helpful - will the actual compile command produce any diagnostics?
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.
According to the spec of CompilerUtils.compile, all warnings/errors emitted by the compiler are output to System.out/err.
For the IOException, it's because Proc::start throws IOException and I don't want to modify it.
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.
Why not just RuntimeException()?
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.
Yes, I can.
| } | ||
|
|
||
| if (compile) { | ||
| var comp = CompilerUtils.compile( |
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.
I don't find this use of var helpful - var is useful for saying "some type I don't really care about and can't be bothered to spell out". But here we just have a boolean so it is clearer to just say boolean compiled (or success or ok or some such name that reflects what the return value actually means). Thanks.
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.
Sure, I'll make it boolean.
|
/label remove hotspot-runtime core-libs |
|
@wangweij The |
mcpowers
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.
Only a minor nit, otherwise looks good.
| return this; | ||
| } | ||
| // Adds classpath to defaults. Can be called multiple times. | ||
| // once called, addcp is always true |
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.
Capitalize and end with period, otherwise it looks odd (to me).
|
@wangweij 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 372 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. ➡️ To integrate this PR with the above commit message to the |
|
/integrate |
|
Going to push as commit b5922c3.
Your commit was automatically rebased without conflicts. |
Enhance the
Procutility to support compilation.Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/13425/head:pull/13425$ git checkout pull/13425Update a local copy of the PR:
$ git checkout pull/13425$ git pull https://git.openjdk.org/jdk.git pull/13425/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 13425View PR using the GUI difftool:
$ git pr show -t 13425Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/13425.diff
Webrev
Link to Webrev Comment