[DERBY-5072] test failure in org.apache.derbyTesting.functionTests.tests.jdbc4.Driver40UnbootedTest.test_notBooted

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 10.8.1.2
• Component/s: Test
• Labels: derby_triage10_8
• Environment: windows XP or Suse Linux, ibm 1.6
• Urgency: Urgent
• Bug behavior facts: Regression Test Failure
• Assignee: Unassigned
• Reporter: Myrna van Lunteren
• Created: 27/Feb/11 05:46
• Updated: 19/Apr/11 12:38
• Resolved: 28/Feb/11 19:33

Description

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.

Issue Links

• duplicates: DERBY-4872 'No suitable Driver' - Drivers don't get auto-loaded when only derbyrun.jar is in the classpath with ibm 1.6 jvm.