Bug ID: JDK-6201464 Regression: CTE_REGTEST/Generic/4493901/EncodingTest.java times out

Versions (Unresolved/Resolved/Fixed)

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	Other
5.0Resolved	5.0u2 b05Fixed

JDK        : 1.5.0_02 b03
Platform[s]         : Fails On:  Solaris 10 Sparc b70
Failing Test [s]    : CTE_REGTEST/Generic/4493901/EncodingTest.java


    Test source location:
    =====================
/net/jdk/export/jpse04/Regression/1.5.0/test/CTE_REGTEST/Generic/4493901/EncodingTest.java

    jtr file location:
    ==================
file:///net/cady/export/dtf/unified/results/tiger_u2/b03/cte-reg/cte-sol10/workDir/CTE_REGTEST/Generic/4493901/EncodingTest.jtr

    How to reproduce:
    ====================
    - Set JAVA_HOME to /net/koori.sfbay/p/jdk05/jdk/1.5.0_02/ea/b03/binaries/solaris-sparc
    - cd /net/jdk/export/jpse04/Regression/1.5.0/test/CTE_REGTEST/Generic/4493901
    - /net/koori.sfbay/onestop/jct-tools/2.1.6/archive/fcs/binaries/solaris/bin/jtreg -r:/tmp -w:/tmp .


    Test output:
    =============
----------System.err:(0/0)----------
result: Failed. Execution failed: Program `/net/koori.sfbay/p/jdk05/jdk/1.5.0_02/ea/b03/binaries/solaris-sparc/bin/java' interrupted! (timed out?)


test result: Failed. Execution failed: Program `/net/koori.sfbay/p/jdk05/jdk/1.5.0_02/ea/b03/binaries/solaris-sparc/bin/java' interrupted! (timed out?)

    Specific Machine Info:
    =====================
SunOS koi 5.10 s10_70 sun4u sparc SUNW,Ultra-80

EVALUATION This test takes a particularly brute force approach to checking for alias names. It takes 49 seconds on my reasonably fast solaris-sparc machine, so it's not particularly surprising that on a slower machine, the default timeout of 2 minutes is being exceeded. This is probably a test case error. I recommend rewriting the test case to remove the brute force search and do something cleverer, like iterate over all encoding names. SQE should check whether a longer timeout, or expansion factor would cause this test to pass. ###@###.### 2005-1-11 03:13:41 GMT As evaluated above, test case should either use a longer timeout setup instead of the default 120 seconds or change the testing approach. Transfer to SQE for necessary test case update. ###@###.### 2005-1-12 07:00:33 GMT ###@###.### 2005-1-12 07:10:15 GMT

11-01-2005