JDK-8172676 : JShell: addToClasspath fails intermittently
  • Type: Bug
  • Component: tools
  • Sub-Component: jshell
  • Affected Version: 9
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2017-01-12
  • Updated: 2017-01-12
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbd_minorUnresolved
Related Reports
Relates :  
JDK-8172295 - JShell: ToolBasicTest fails with "package pkg does not exist"
Relates :  
JDK-8171829 - JShell test: jdk/jshell/CompletionSuggestionTest.java failed with AssertionError
Description
Disparate tests show failures because classes/packages created by the "Compiler" test harness and added to the classpath by the JShell.addToClasspath() mechanism are not seen on the classpath on subsequent accesses.

Since it can't be reproduced, it is unclear if this is an issue with addToClasspath or a filesystem or "Compiler" timing issue.

With JDK-8165405, JShell.addToClasspath is no longer used by the tool and the test infrastructure that used it now uses a completely different mechanism.   However, it is still in the API and API tests have been seen to fail.