Out of curiosity - is there anything helpful in derby.log?
I ran derbyall with J2ME/CDC/FP with the new snapshot. 3 tests failed.
I have attached the diff for failures.
* derbyall/derbyall.fail:jdbcapi/metadataJdbc20.java (needs master file update)
The stack trace for IllegalStateException from .tmp files:
at java.util.zip.ZipFile.getEntryImpl(Native Method)
Has anyone seen this before?
I tried to run the failed online compress tests individually but
looking at the tests, I think they have to be run in sequence. So I
ran just storeall suite and the tests oc_rec1.java and oc_rec3.java
passed. I am not sure if these failures are intermittent. If anyone
who has more knowledge of these tests can look into this and tell if
this could be a problem in test/code, it would be great.
On 10/5/05, Kathey Marsden <email@example.com> wrote:
> Knut Anders Hatlen wrote:
> >Kathey Marsden <
> >>Running derbyall with the 10.1 jars made with a sane build (svn
> >>292855), I am seeing a difference in plan for lang/wisconsin.sql in
> >>embedded. If I run the test independently it passes.
> >I tried to run the test independently with your snapshot, and it
> Thanks Knut for looking at this. I finally gave up on that snapshot
> and made a new proposed snapshot based on SVN 292855.
> I still have no idea what the problem was with wisconsin but derbyall on
> Windows runs cleanly with the new one.
> Also the same build has expected results on Ole's page.
> I will go ahead and bump the version. The only issue with the version
> is that there was a test change checked in yesterday (DERBY-459)
> which is not in the snapshot but got put in before the version bump.
> Deepa could you try this with J2ME? If anyone else can give the
> snapshot a try before we post it that would be great.