Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (herse.apache.org: local policy)
Date: Fri, 29 Jun 2007 10:14:08 +0200
From: Knut Anders Hatlen <Knut.Hatlen@Sun.COM>
Subject: Re: 10.3 upgrade test on mac, anyone see failures?
In-reply-to: <c25576af0706281336q6f239846s322ee3220b3fab35@mail.gmail.com>
Sender: Knut.Hatlen@Sun.COM
To: derby-dev@db.apache.org
Message-id: <wjo864572n5b.fsf@sun.com>
Organization: Sun Microsystems
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
References: <c25576af0706281336q6f239846s322ee3220b3fab35@mail.gmail.com>
User-Agent: Gnus/5.110007 (No Gnus v0.7) Emacs/22.1 (usg-unix-v)

Myrna van Lunteren <m.v.lunteren@gmail.com> writes:

> Hi,
>
> I ran suites.All with 10.3.1.0 beta on a mac OS X, and I get 69
> failures and 17 errors.
> I tried specifying no oldReleasePath, an incorrect oldReleasePath, and
> a correct oldReleasePath, all giving me the same result.
> I'm currently out of ideas.
>
> Is there anyone else who has a mac that can confirm/counter this for me?

Hi Myrna,

This could be DERBY-1 which prevented DB creation on OS X and BSDs with
a buggy JVM. You can check whether you have a buggy JVM by booting a
database with 10.3 or trunk and see if derby.log contains this message
(added in DERBY-2020):

------------ BEGIN ERROR MESSAGE -------------

LogToFile.checkJvmSyncError: Your JVM seems to have a problem with
implicit syncing of log files. Will use explicit syncing instead.
------------ END ERROR MESSAGE -------------

So what happens, is not that the upgrade fails, but that 10.0 and some
of the 10.1 releases (don't remember which) can't create the database.

-- 
Knut Anders