-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
8353332: Test jdk/jshell/ToolProviderTest.java failed in relation to enable-preview #24492
Conversation
👋 Welcome back jlahoda! A progress list of the required criteria for merging this PR into |
@lahodaj 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 21 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 |
I don't have knowledge of this area, but given what seems to be happening in this test and the code that I looked through briefly, this proposed change to provide a way for augmenting the building of the I'll update the JBS issue once the CI runs that I've triggered (without this change) come back. That should tell us if local stored preferences is (the only thing) that's playing a role in these failures. |
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.
This looks OK to me. I think it would be good to have someone more familiar with this area review this too.
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.
/integrate |
Going to push as commit 9088afc4f16b6265e640bf176d8ca8e3ac6ca45c.
Your commit was automatically rebased without conflicts. |
JShell keeps persisted preferences in
java.util.prefs.Preferences
. But, during tests, an empty persistence is typically used, to avoid values persisted on the test machine to affect the test.But, in case of
jdk/jshell/ToolProviderTest.java
, this is not done, as JShell is started using theTool
interface.This patch strives to fix that, by adding indirection in building JShell in
JShellToolProvider
, and using that in the test to inject empty persistence.Thanks to @jaikiran for figuring out the probable cause.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/24492/head:pull/24492
$ git checkout pull/24492
Update a local copy of the PR:
$ git checkout pull/24492
$ git pull https://git.openjdk.org/jdk.git pull/24492/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 24492
View PR using the GUI difftool:
$ git pr show -t 24492
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/24492.diff
Using Webrev
Link to Webrev Comment