harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prashanth KS (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-6620) [jdktools] Unit tests to test the functionality of the javac/javaw binaries
Date Fri, 17 Sep 2010 14:15:35 GMT

    [ https://issues.apache.org/jira/browse/HARMONY-6620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12910601#action_12910601
] 

Prashanth KS commented on HARMONY-6620:
---------------------------------------

Missed adding this comment during the code freeze timeframe.

Other than the comment below, the rest of them have been addressed. I didn't do this because
I didn't want to nest method calls. I also added a provision to monitor exit status.

"Since all runExe callers call getProcessOutput why not have runExe
take a displayOutput boolean and then return:

 { proc, getProcessOutput(proc, displayOutput), errBuf.toString() } "

I see three different behaviors with DRLVM, IBM JDK and SUN JRE. The JavacBinTest.java test
hangs with DRLVM but works on the other two JDKs properly. JavawBinTest.java hangs on IBM
JDK, but works fine with the SUN JRE. I will examine this more deeply and get back with the
necessary reports.

I specifically created the tests in a windows dir because it is more visible to the developer,
rather than the exclude files. Hope this is ok. 



> [jdktools] Unit tests to test the functionality of the javac/javaw binaries
> ---------------------------------------------------------------------------
>
>                 Key: HARMONY-6620
>                 URL: https://issues.apache.org/jira/browse/HARMONY-6620
>             Project: Harmony
>          Issue Type: Test
>          Components: JDK
>         Environment: Windows and Linux
>            Reporter: Prashanth KS
>         Attachments: 001_HARMONY_6620.patch, 002_HARMONY_6620.patch, 003_HARMONY_6620.patch,
resources.zip
>
>
> The ANT unit tests written for the jdktools binaries such as javac aren't flexible enough.
i.e. if there is a test failure then the rest of the tests are skipped. Moreover, there aren't
a lot of test scenarios created for these binaries.
> Added Unit tests to test the javac.exe and javaw.exe tools. This helps in providing a
better analysis of these tools across different runtimes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message