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
8270184: [TESTBUG] Add coverage for jvmci ResolvedJavaType.toJavaName() for lambdas #4746
Conversation
|
@jerboaa 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 44 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.
|
Thanks for the review! |
/integrate |
Going to push as commit 6a9bc10.
Your commit was automatically rebased without conflicts. |
Please review this simple test addition. It adds more coverage
toJavaName()
for generated classes for lambdas.Testing: jtreg:test/hotspot/jtreg/compiler/jvmci
Thoughts?
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/4746/head:pull/4746
$ git checkout pull/4746
Update a local copy of the PR:
$ git checkout pull/4746
$ git pull https://git.openjdk.java.net/jdk pull/4746/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 4746
View PR using the GUI difftool:
$ git pr show -t 4746
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/4746.diff