-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8360131: Remove use of soon-to-be-removed APIs by CTW framework #25916
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
👋 Welcome back david-beaumont! A progress list of the required criteria for merging this PR into |
@david-beaumont 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 235 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 (@liach, @TobiHartmann) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
@david-beaumont 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
|
LGTM |
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 think ctw is in hs-tier2 tests. You may run them on the CI for sanity checking.
@@ -69,30 +79,40 @@ public void close() { | |||
} | |||
} | |||
|
|||
private final ImageReader reader; | |||
//private final ImageReader reader; |
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.
//private final ImageReader reader; |
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.
doh - thanks.
} | ||
} catch (IOException e) { | ||
throw new RuntimeException(e); |
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.
Maybe throw an error for consistency with other methods in this class?
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.
Personally I don't like Error
as a response to runtime issues like this, but consistency is probably good, so done.
* @throws AssertionError if filename isn't valid filename for class file - | ||
* {@link #isClassFile(String)} |
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.
* @throws AssertionError if filename isn't valid filename for class file - | |
* {@link #isClassFile(String)} |
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.
What's the suggestion here? I see no change.
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.
doh you meant just to delete it. Done.
The test group |
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.
The Java code looks good. Let's wait for hotspot reviewers. I think the tests you've run are sufficient.
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 to me but since variants of CTW are executed in tier3 as well, I would recommend running tier1-3 before integrating this.
/integrate |
@david-beaumont |
/sponsor |
Going to push as commit fdfc557.
Your commit was automatically rebased without conflicts. |
@TobiHartmann @david-beaumont Pushed as commit fdfc557. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Migrate the CWT framework to use only supported JRT file system access for fetching class bytes.
This avoids accessing APIs in ImageReader which are scheduled to be removed as part of preview mode class support in Valhalla (essentially these APIs are "too low level" and expose semantics that are incompatible with supporting preview classes in Valhalla).
This will be a further change to this code when the preview mode work goes in, but this will be limited to how the file system is opened (with or without preview mode).
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/25916/head:pull/25916
$ git checkout pull/25916
Update a local copy of the PR:
$ git checkout pull/25916
$ git pull https://git.openjdk.org/jdk.git pull/25916/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 25916
View PR using the GUI difftool:
$ git pr show -t 25916
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/25916.diff
Using Webrev
Link to Webrev Comment