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

Myrna van Lunteren commented on DERBY-5072:
-------------------------------------------

Changes between the build where it showed up and the previous nightly build 
where it didn't were:
SUBVERSION LOG FROM 1068253 TO 1068745:
------------------------------------------------------------------------
http://svn.apache.org/viewvc?view=revision&revision=1068702 | dag | 2011-02-08 
16:23:56 -0800 (Tue, 08 Feb 2011) | 4 lines

DERBY-5011 Client driver lexer to determine statement type: fix bad attempt at 
incrementing a variable

Patch fix_bad_increment_dhw. Contributed by Dave Brosius,dbrosius at apache dot 
org

------------------------------------------------------------------------
http://svn.apache.org/viewvc?view=revision&revision=1068528 | rhillegas | 
2011-02-08 11:10:23 -0800 (Tue, 08 Feb 2011) | 1 line

DERBY-5009: Commit Dave Brosius' patch which fixes an error in normalizing the 
release notes for publication on the website.
------------------------------------------------------------------------
http://svn.apache.org/viewvc?view=revision&revision=1068524 | rhillegas | 
2011-02-08 10:58:02 -0800 (Tue, 08 Feb 2011) | 1 line

DERBY-4869: Make AutoloadTest aware of the new driver classes introduced by the 
getParentLogger() work.
------------------------------------------------------------------------
http://svn.apache.org/viewvc?view=revision&revision=1068489 | rhillegas | 
2011-02-08 09:35:58 -0800 (Tue, 08 Feb 2011) | 1 line

DERBY-4869: Uncomment the signature-matching tests on Java 7 now that all of 
the JDBC 4.1 methods have been added.
------------------------------------------------------------------------
http://svn.apache.org/viewvc?view=revision&revision=1068451 | rhillegas | 
2011-02-08 07:50:04 -0800 (Tue, 08 Feb 2011) | 1 line

DERBY-4869: Load the JDBC 4.0 exception factory when initializing the 4.0 
autoloaded driver.
------------------------------------------------------------------------
http://svn.apache.org/viewvc?view=revision&revision=1068305 | kahatlen | 
2011-02-08 01:43:45 -0800 (Tue, 08 Feb 2011) | 3 lines

DERBY-5013: remove dead allocation

Patch contributed by Dave Brosius <[email protected]>.
------------------------------------------------------------------------
http://svn.apache.org/viewvc?view=revision&revision=1068302 | kahatlen | 
2011-02-08 01:26:35 -0800 (Tue, 08 Feb 2011) | 4 lines

DERBY-5008: fix npe in error condition

Fix contributed by Dave Brosius <[email protected]>.

------------------------------------------------------------------------




> test failure in 
> org.apache.derbyTesting.functionTests.tests.jdbc4.Driver40UnbootedTest.test_notBooted
> -----------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5072
>                 URL: https://issues.apache.org/jira/browse/DERBY-5072
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.8.0.0
>         Environment: windows XP or Suse Linux, ibm 1.6 
>            Reporter: Myrna van Lunteren
>              Labels: derby_triage10_8
>
> Since Feb 8, build sync-ed up to revision 1068745, there has been one test 
> failure that remains unresolved:
> 1) 
> test_notBooted(org.apache.derbyTesting.functionTests.tests.jdbc4.Driver40UnbootedTest)junit.framework.AssertionFailedError:
>  expected:<0> but was:<1>
>       at 
> org.apache.derbyTesting.functionTests.tests.jdbc4.Driver40UnbootedTest.test_notBooted(Driver40UnbootedTest.java:159)
>       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>       at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
>       at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
>       at 
> org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:112)
>       at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>       at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>       at junit.extensions.TestSetup.run(TestSetup.java:16)
> The console spits out the following when this test runs:
> test_notBooted START-SPAWNED:UnbootedTest ERROR OUTPUT:
> Exception in thread "main" java.sql.SQLException: No suitable driver
>       at java.sql.DriverManager.getDriver(DriverManager.java:396)
>       at 
> org.apache.derbyTesting.functionTests.tests.jdbc4.Driver40UnbootedTest.main(Driver40UnbootedTest.java:105)
> END-SPAWNED  :UnbootedTest ERROR OUTPUT:
> This happens on both Suse Linux and Windows XP.
> See also: 
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/ibm16/1074780-suites.All_diff.txt
> (IBM 1.6 on Linux has the same problem, but you cannot tell which test fails 
> from the reports at that site because of a reporting issue).
> I tried to reproduce with just and just the jdbc4 suite on my system, and 
> couldn't, but perhaps in both cases the test was skipped because it ran in 0 
> ms? I'll continue investigating...
> Marking this as 'test issue' for now, and urgent because of imminent 10.8 
> release.

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

        

Reply via email to