JDK-8202467 : jdk/jshell/ToolBasicTest.java fails at testClasspathDirectory()
  • Type: Bug
  • Component: tools
  • Sub-Component: jshell
  • Affected Version: 11
  • Priority: P3
  • Status: Open
  • Resolution: Unresolved
  • OS: windows
  • Submitted: 2018-05-01
  • Updated: 2018-09-03
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-8202520 - JShell tests: move intermittently failing tests to tier2
Relates :  
JDK-8172295 - JShell: ToolBasicTest fails with "package pkg does not exist"
Description
[TestNG] Running:
  jdk/jshell/ToolBasicTest.java

config ReplToolTesting.setUp(): success
test ToolBasicTest.elideStartUpFromList(): success
config ReplToolTesting.setUp(): success
test ToolBasicTest.elideStartUpFromSave(): success
config ReplToolTesting.setUp(): success
test ToolBasicTest.test8142447(): success
config ReplToolTesting.setUp(): success
test ToolBasicTest.testAddExports(): success
config ReplToolTesting.setUp(): success
test ToolBasicTest.testBadClasspath(): success
config ReplToolTesting.setUp(): success
test ToolBasicTest.testBadModulePath(): success
config ReplToolTesting.setUp(): success
test ToolBasicTest.testBadSourceJarClasspath(): success
config ReplToolTesting.setUp(): success
test ToolBasicTest.testClasspathDirectory(): failure
java.lang.AssertionError: Output: '|  Error:
|  package pkg does not exist
|  new pkg.A();
|      ^---^
' does not fit pattern: '(\\$\\d+) ==> A' expected [true] but found [false]
	at org.testng.Assert.fail(Assert.java:94)
	at org.testng.Assert.failNotEquals(Assert.java:496)
	at org.testng.Assert.assertTrue(Assert.java:42)
	at ReplToolTesting.lambda$evaluateExpression$11(ReplToolTesting.java:331)
	at ReplToolTesting.assertCommandCheckOutput(ReplToolTesting.java:483)
	at ReplToolTesting.evaluateExpression(ReplToolTesting.java:329)
	at ToolBasicTest.lambda$testClasspathDirectory$52(ToolBasicTest.java:268)
	at ReplToolTesting$PromptedCommandOutputStream.write(ReplToolTesting.java:795)
	at ReplToolTesting$PromptedCommandOutputStream.write(ReplToolTesting.java:811)
	at java.base/java.io.PrintStream.write(PrintStream.java:559)
	at java.base/sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:233)
	at java.base/sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:312)
	at java.base/sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:316)
	at java.base/sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:153)
	at java.base/java.io.OutputStreamWriter.flush(OutputStreamWriter.java:254)
	at jdk.internal.le/jdk.internal.jline.console.ConsoleReader.readLine(ConsoleReader.java:2339)
	at jdk.internal.le/jdk.internal.jline.console.ConsoleReader.readLine(ConsoleReader.java:2280)
	at jdk.jshell/jdk.internal.jshell.tool.ConsoleIOContext.readLine(ConsoleIOContext.java:142)
	at jdk.jshell/jdk.internal.jshell.tool.JShellTool.getInput(JShellTool.java:1257)
	at jdk.jshell/jdk.internal.jshell.tool.JShellTool.run(JShellTool.java:1170)
	at jdk.jshell/jdk.internal.jshell.tool.JShellTool.start(JShellTool.java:971)
	at jdk.jshell/jdk.internal.jshell.tool.JShellToolBuilder.run(JShellToolBuilder.java:240)
	at ReplToolTesting.testRawRun(ReplToolTesting.java:302)
	at ReplToolTesting.testRaw(ReplToolTesting.java:285)
	at ReplToolTesting.test(ReplToolTesting.java:240)
	at ReplToolTesting.test(ReplToolTesting.java:224)
	at ReplToolTesting.test(ReplToolTesting.java:220)
	at ToolBasicTest.testClasspathDirectory(ToolBasicTest.java:270)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:569)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:85)
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:639)
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:821)
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1131)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:124)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108)
	at org.testng.TestRunner.privateRun(TestRunner.java:773)
	at org.testng.TestRunner.run(TestRunner.java:623)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:357)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:352)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:310)
	at org.testng.SuiteRunner.run(SuiteRunner.java:259)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1185)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1110)
	at org.testng.TestNG.run(TestNG.java:1018)
	at com.sun.javatest.regtest.agent.TestNGRunner.main(TestNGRunner.java:94)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:569)
	at com.sun.javatest.regtest.agent.MainActionHelper$SameVMRunnable.run(MainActionHelper.java:229)
	at java.base/java.lang.Thread.run(Thread.java:832)
config ReplToolTesting.setUp(): success
...
Comments
David, Correct. I don't think this particular failure has anything to do with network connectivity. My statement was: > Here's the problem, not specifically the problem with that test. All JShell tests fail at least rarely > attempting to create network connections -- they create lots. It is very likely, however, related to high-concurrency testing. Really hard to tell when I can't reproduce.
05-05-2018
From 82802467: > All JShell tests fail at least rarely attempting to create network connections I have a hard time seeing how the above failure mode might relate to a problem creating network connections. Is there some verbose mode for running the tests so that these connection issues can be made visible in the logs?
03-05-2018