On 06/01/14 16:18, Dimitar Mavrodiev wrote:
Yes, I've disabled IPv6 and it came out as successful in the report. Is
it possible that jtreg behaves differently across different OSes? I am
using it on Linux and OSX, the bug report mentions Windows.

It is possible, but I don't see any special handling for SkipException in the jtreg source. I also cannot find any use of it in the any of the OpenJDK JDK 9 repositories. Maybe just to be safe you could print a warning message and simply return?

-Chris.



On Mon, Jan 6, 2014 at 6:16 PM, Chris Hegarty <chris.hega...@oracle.com
<mailto:chris.hega...@oracle.com>> wrote:

    On 06/01/14 16:05, Dimitar Mavrodiev wrote:

        The jtreg version I am using(4.1 fcs b05) seems to be correctly
        handling
        it. What jtreg version should I be using?


    See https://bugs.openjdk.java.net/__browse/JDK-8026362
    <https://bugs.openjdk.java.net/browse/JDK-8026362> for a an example
    of this.

    Did you try to run your test without ::1 enabled?

    -Chris.



        On Mon, Jan 6, 2014 at 5:52 PM, Alan Bateman
        <alan.bate...@oracle.com <mailto:alan.bate...@oracle.com>
        <mailto:Alan.Bateman@oracle.__com
        <mailto:alan.bate...@oracle.com>>> wrote:

             On 06/01/2014 15:21, Dimitar Mavrodiev wrote:

                 Thanks, Chris.

                 I've removed the dependency on the internal HttpServer.
        Here's
                 another webrev
        
https://googledrive.com/host/____0B2CI6Ih--1t5bVVwbVlBRmpVMDg/____2/index.html
        
<https://googledrive.com/host/__0B2CI6Ih--1t5bVVwbVlBRmpVMDg/__2/index.html>

        
<https://googledrive.com/host/__0B2CI6Ih--1t5bVVwbVlBRmpVMDg/__2/index.html
        
<https://googledrive.com/host/0B2CI6Ih--1t5bVVwbVlBRmpVMDg/2/index.html>>.


             I'm not 100% sure how jtreg handles TestNG tests throwing
             SkipException. If it doesn't then it probably means adding
        a flag so
             that the test passes silently when IPv6 is not enabled.

             -Alan



Reply via email to