Test java/awt/FontClass/CreateFont/bigfont fails JDK 8 b67 Linux x86.
Log: http://aurora-ds.ru.oracle.com:9500/runs/139836.ute.st2-2/results/workDir/java/awt/FontClass/CreateFont/bigfont.jtr
----------messages:(3/115)----------
command: applet bigfont.html
reason: User specified action: run applet bigfont.html
elapsed time (seconds): 1.567
----------System.out:(3/188)----------
Applet 1 com.sun.javatest.regtest.AppletWrapper$AppletThreadGroup[name=AppletThreadGroup,maxpri=10]
64000000
java.awt.FontFormatException: Unsupported sfnt /tmp/+~JF982265630742164997.tmp
----------System.err:(5/323)----------
java.lang.RuntimeException: Allowed file to be too large.
at BigFont.init(BigFont.java:74)
at com.sun.javatest.regtest.AppletWrapper$AppletRunnable.run(AppletWrapper.java:155)
at java.lang.Thread.run(Thread.java:722)
STATUS:Failed.Applet thread threw exception: java.lang.RuntimeException: Allowed file to be too large.
result: Failed. Execution failed: Applet thread threw exception: java.lang.RuntimeException: Allowed file to be too large.
test result: Failed. Execution failed: Applet thread threw exception: java.lang.RuntimeException: Allowed file to be too large.
|
|
|
SUGGESTED FIX
The proposed fix works for 1.7.0/1.8.0
http://sqe-rb.us.oracle.com/r/8234/diff/#index_header
|
|
|
SUGGESTED FIX
http://spbweb.russia.sun.com/~ad153231/jdk7/webrev-fonts2/index.html
|
|
|
EVALUATION
Same as in 6802962:
-make BigFont a "main" test
-wrap FontFile into shell starter
|
|
|
EVALUATION
The jtreg harness itself seem tries to get [0] of the empty string so it constantly falls into the if-statement in the String.charAt().
But by some reason it neither can throw the exception out nor somehow report.
"DefaultTestRunner:Worker-0:0" prio=10 tid=0xa17c4400 nid=0x1fd0 runnable [0x005b2000]
java.lang.Thread.State: RUNNABLE
JavaThread state: _thread_blocked
Thread: 0xa17c4400 [0x1fd0] State: _call_back _has_called_back 1 _at_poll_safepoint 0
JavaThread state: _thread_blocked
at java.lang.Throwable.fillInStackTrace(Native Method)
- locked <0xa1d56580> (a java.lang.StringIndexOutOfBoundsException)
at java.lang.Throwable.<init>(Throwable.java:247)
at java.lang.Exception.<init>(Exception.java:66)
at java.lang.RuntimeException.<init>(RuntimeException.java:62)
at java.lang.IndexOutOfBoundsException.<init>(IndexOutOfBoundsException.java:56)
at java.lang.StringIndexOutOfBoundsException.<init>(StringIndexOutOfBoundsException.java:69)
at java.lang.String.charAt(String.java:695)
at com.sun.javatest.regtest.AppletAction$HTMLFileContents.getAttPositions(AppletAction.java:501)
at com.sun.javatest.regtest.AppletAction$HTMLFileContents.attsToDictionary(AppletAction.java:596)
at com.sun.javatest.regtest.AppletAction$HTMLFileContents.<init>(AppletAction.java:455)
at com.sun.javatest.regtest.AppletAction.run(AppletAction.java:149)
at com.sun.javatest.regtest.RegressionScript.run(RegressionScript.java:101)
at com.sun.javatest.Script.run(Script.java:228)
at com.sun.javatest.DefaultTestRunner.runTest(DefaultTestRunner.java:167)
at com.sun.javatest.DefaultTestRunner.access$100(DefaultTestRunner.java:43)
at com.sun.javatest.DefaultTestRunner$1.run(DefaultTestRunner.java:66)
We seem don't have any tests which rely on the <param> tag and jtreg can't recognize it in any way.
It's easy to fix the test just to make it up and running (honestly it will fail by some other reason, it must be because of being old) but javatest team may want to fix this in the harness.
|
|
|
SUGGESTED FIX
There is a fix for these tests in jdk6 ws. We could fwd-port it into the jdk7.
|
|
|
EVALUATION
The newer link is: http://jre.sfbay/java/re/jdk/6u22/promoted/ea/b30/j4b/ws/j2se/test/java/awt/FontClass/
|
|
|