db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-5069) Since Feb 7,2011 weme 6.2 Junit tests have failed to run completely with Failed to invoke suite():java.lang.reflect.InvocationTargetException
Date Fri, 25 Feb 2011 21:03:22 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999564#comment-12999564
] 

Kathey Marsden commented on DERBY-5069:
---------------------------------------

The trouble seems to be associated with the addition of this testing to DriverTest
        // test that the driver is one of the special 40 versions if we are running
        // on Java 6 or higher
        println( "Driver is a " + driver.getClass().getName() );
        assertEquals( JDBC.vmSupportsJDBC4(), driver.getClass().getName().endsWith( "40" )
);

But I am not sure why this particular part of the test is problematic as  there are lots of
other references to driver that seem to be avoided successfully with this code in the suite()
method.
  if (JDBC.vmSupportsJSR169())
        {
            return new TestSuite(
                "DriverTest tests java.sql.Driver, not supported with JSR169");
        }


> Since Feb 7,2011 weme 6.2 Junit tests have failed to run completely with Failed to invoke
suite():java.lang.reflect.InvocationTargetException
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5069
>                 URL: https://issues.apache.org/jira/browse/DERBY-5069
>             Project: Derby
>          Issue Type: Bug
>            Reporter: Kathey Marsden
>            Assignee: Kathey Marsden
>            Priority: Critical
>
> Since Feb 8, the weme 6.2 Junit tests have failed to run. The only output on the test
report is:
> Failed to invoke suite():java.lang.reflect.InvocationTargetException
> Below is the list of checkins on the day it started failing. derbyall looks ok. 
> SUBVERSION LOG FROM 1067846 TO 1068253:
> ------------------------------------------------------------------------
> r1068073 | rhillegas | 2011-02-07 11:34:02 -0800 (Mon, 07 Feb 2011) | 1 line
> DERBY-4869: Attempt to fix problem in tinderbox tests introduced by a previous commit
today.
> ------------------------------------------------------------------------
> r1067991 | rhillegas | 2011-02-07 08:04:25 -0800 (Mon, 07 Feb 2011) | 1 line
> DERBY-4869: Always raise SQLFeatureNotSupportedException when Connection.get/setNetworkTimeout()
is called.
> ------------------------------------------------------------------------
> r1067954 | rhillegas | 2011-02-07 06:54:31 -0800 (Mon, 07 Feb 2011) | 1 line
> DERBY-4869: Add JDBC 4.1 getParentLogger() method to Derby's implementations of Driver
and CommonDataSource.
> ------------------------------------------------------------------------
> This should be promoted to blocker if determined to be a product regression.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message