-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8352896: LambdaExpr02.java runs wrong test class #24277
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 linzihao1999! A progress list of the required criteria for merging this PR into |
|
@linzihao1999 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 18 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. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@shipilev, @liach, @lahodaj) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
|
@linzihao1999 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
|
shipilev
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.
Ha! Looks good.
|
/integrate |
|
@linzihao1999 |
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.
Should we just drop main Xxx as this is automatically added by jtreg?
That make sense. Just drop the |
shipilev
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.
Sorry, but this is not what other tests in the same directory do. Leave it at
* @run main LambdaExpr02
5c7cc21 to
6dd3941
Compare
|
@linzihao1999 Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information. |
|
Guess we will fix this when jtreg introduces something like |
|
@lahodaj What do you think on this one? |
lahodaj
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.
I don't have a very strong preference between nothing, @run main <testname> and:
@compile <testname>.java
@run main <testname>
The latter is sometime good specifically for javac, as it forces compilation, and that is desirable while developing javac (because for @build/@run main, it may happen an updated javac is not used to compile the given test, as the test is already compiled).
But, that's not strong enough to alter long-existing test headers. So, keeping things more or less as they are, and consistent across the directory seems good.
|
/sponsor |
|
Going to push as commit c029220.
Your commit was automatically rebased without conflicts. |
|
@vicente-romero-oracle @linzihao1999 Pushed as commit c029220. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Fix LambdaExpr02.java runs wrong test class.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/24277/head:pull/24277$ git checkout pull/24277Update a local copy of the PR:
$ git checkout pull/24277$ git pull https://git.openjdk.org/jdk.git pull/24277/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 24277View PR using the GUI difftool:
$ git pr show -t 24277Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/24277.diff
Using Webrev
Link to Webrev Comment