-
Bug
-
Resolution: Fixed
-
P4
-
15
-
b22
-
generic
-
generic
The new test java/awt/font/Rotate/RotatedSyntheticBoldTest.java introduced by JDK-8233006 is accidentally executed with additional parameters causing it not to test the real issue.
The test contains the following description:
/*
+ * @test RotatedSyntheticBoldTest
+ * @bug 8233006
+ * @summary This test verifies that rotated synthetically bolded fonts
+ * do not have a wandering baseline
+ * @run main RotatedSyntheticBoldTest
+ *
+ * Note this is designed to be run headless. The creation of the UI
+ * is meant to be run outside the harness as an visualisaton aid to
+ * debugging any failure.
+ */
The comment is not marked with @comment - and is therefore counted as additional param to the @run.
You can see it in the jtr file after executing the test. It contains the lines:
#section:main
----------messages:(5/516)----------
command: main RotatedSyntheticBoldTest Note this is designed to be run headless. The creation of the UI is meant to be run outside the harness as an visualisaton aid to debugging any failure.
reason: User specified action: run main RotatedSyntheticBoldTest Note this is designed to be run headless. The creation of the UI is meant to be run outside the harness as an visualisaton aid to debugging any failure.
Mode: othervm
The test will start a gui and not the real test when executed with more than one arg. Therefore the test does not execute the expected test. And in case of a headless VM and a bad timing the GUI will even throw a HeadlessException. but only when the shutdown of the VM after executing is slower than the startup of the Swing Framework.
An easy fix would be to add @comment before the additional text.
The test contains the following description:
/*
+ * @test RotatedSyntheticBoldTest
+ * @bug 8233006
+ * @summary This test verifies that rotated synthetically bolded fonts
+ * do not have a wandering baseline
+ * @run main RotatedSyntheticBoldTest
+ *
+ * Note this is designed to be run headless. The creation of the UI
+ * is meant to be run outside the harness as an visualisaton aid to
+ * debugging any failure.
+ */
The comment is not marked with @comment - and is therefore counted as additional param to the @run.
You can see it in the jtr file after executing the test. It contains the lines:
#section:main
----------messages:(5/516)----------
command: main RotatedSyntheticBoldTest Note this is designed to be run headless. The creation of the UI is meant to be run outside the harness as an visualisaton aid to debugging any failure.
reason: User specified action: run main RotatedSyntheticBoldTest Note this is designed to be run headless. The creation of the UI is meant to be run outside the harness as an visualisaton aid to debugging any failure.
Mode: othervm
The test will start a gui and not the real test when executed with more than one arg. Therefore the test does not execute the expected test. And in case of a headless VM and a bad timing the GUI will even throw a HeadlessException. but only when the shutdown of the VM after executing is slower than the startup of the Swing Framework.
An easy fix would be to add @comment before the additional text.