JDK-8194968 : problem list actions for tools/javac/jvm/VerboseOutTest
  • Type: Bug
  • Component: tools
  • Sub-Component: javac
  • Affected Version: 11
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2018-01-12
  • Updated: 2018-05-12
  • Resolved: 2018-05-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.
JDK 11
11 b13Fixed
Related Reports
Relates :  
JDK-8194893 - javac -verbose prints wrong paths for output files
Sub Tasks
JDK-8195067 :  
problem list tools/javac/jvm/VerboseOutTest.java - Resolved
JDK-8202584 :  
de-problem list tools/javac/jvm/VerboseOutTest - Resolved
Description
Observed a failure on Windows Server 2012 R2.

Parts of the test log:
[loading /modules/java.base/java/lang/invoke/CallSite.class]
[wrote .\\VerboseOutTest.class]
[total 78ms]

----------System.err:(13/792)----------
java.lang.Exception: expected output not found: [wrote ./VerboseOutTest.class]
	at VerboseOutTest.run(VerboseOutTest.java:61)
	at VerboseOutTest.main(VerboseOutTest.java:40)
	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:564)
	at com.sun.javatest.regtest.agent.MainActionHelper$SameVMRunnable.run(MainActionHelper.java:229)
	at java.base/java.lang.Thread.run(Thread.java:844)
Comments
Fix understood
03-05-2018
Problem listing the test doesn't solve the issue that a tier1 test failure was filed as a P4 bug. If a failure in this test is actually a P4, then this test should not be in tier1. Changing from P4 -> P2.
16-01-2018
the test has been problem listed by JDK-8195067 / http://hg.openjdk.java.net/jdk/jdk/rev/fb56735cb46a
12-01-2018
Why is a tier 1 failure a P4? I'd prefer if we take CI failures seriously.
12-01-2018
From JDK-8194893 http://hg.openjdk.java.net/jdk/jdk/rev/7a700fd0ad509c9d9013a142c4d73e12805d77cf
12-01-2018