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

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

Hi,

Apologies if I've been unclear. The failure from the description is seen on the 
machine where tests are run nightly - this is a Windows XP desktop (I think 
it's an IBM ThinkCentre). This machine runs suites.All with ibm 1.5, 1.6 and 
weme 6.2 (which is IBM's implementation of the J2ME/CDC/Foundation profile). 
The test failure is because at the top of the .out file, there is an extra 
message 'ERROR XJ004: Database ' ' not found, which isn't in the master (and 
doesn't show up on the other jvms). I think it's possible that this message 
would go away if we specify the properties as in DERBY-5346...

But I tried to reproduce this failure with weme 6.2 on my laptop, which is a 
Thinkpad T60 with Windows XP - by running the test by itself, by running a 
modified tools suite, running the full tools suite, and finally running the 
full suites.All, and I did not see the failure. I used the same weme version on 
both machines.

So I'm still struggling to figure out when this happens on the nightly machine.

The getURL(String) not found message I got on my laptop, in all of the 
experiments indicated above. I'm confused about that too, because the failure 
on the nightly machine really indicates that the entire test was executed 
correctly, which seems impossible based on the behavior on my laptop.

It would be interesting to know if either of those problems shows with PhoneME, 
but I don't have access to that.


> converted ij5Test fails with weme6.2 (CDC/Foundation): 
> junit.framework.ComparisonFailure: Output at line 1 expected:<CONNECTION0* -  
>  jdbc:derby:wombat> but was:<ERROR XJ004: Database '' not found.>
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5374
>                 URL: https://issues.apache.org/jira/browse/DERBY-5374
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.9.0.0
>         Environment: windows XP, with weme6.2 (IBM's CDC/Foundation 
> implementation)
>            Reporter: Myrna van Lunteren
>
> The newly converted (to junit) test ij5Test fails with weme 6.2:
> ij5(org.apache.derbyTesting.functionTests.tests.tools.ij5Test)junit.framework.ComparisonFailure:
>  Output at line 1 expected:<CONNECTION0* -    jdbc:derby:wombat> but 
> was:<ERROR XJ004: Database '' not found.>
>       at 
> junit.framework.AssertionFailedError.<init>(AssertionFailedError.java:11)
>       at junit.framework.ComparisonFailure.<init>(ComparisonFailure.java:19)
>       at 
> org.apache.derbyTesting.functionTests.util.CanonTestCase.compareCanon(CanonTestCase.java:109)
>       at 
> org.apache.derbyTesting.functionTests.util.ScriptTestCase.runTest(ScriptTestCase.java:204)
>       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:23)
>       at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>       at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>       at junit.extensions.TestSetup.run(TestSetup.java:23)
>       at 
> org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> This is likely a similar problem as described in DERBY-5373 (re 
> importExportIJ). 
> see also (until cleaned up at some point in the future): 
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/weme6.2/1152992-suites.All_diff.txt

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

        

Reply via email to