Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (nike.apache.org: domain of rick.hillegas@oracle.com
 designates 156.151.31.81 as permitted sender)
Message-ID: <53F4E589.9010802@oracle.com>
Date: Wed, 20 Aug 2014 11:14:33 -0700
From: Rick Hillegas <rick.hillegas@oracle.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US;
 rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: "derby-dev@db.apache.org" <derby-dev@db.apache.org>
Subject: testing crash recovery
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I would like to understand what additional testing of the release 
candidate should be performed in order to satisfy the checklist item 
called "Recovery after crashing engine". Various recovery tests are run 
as part of our platform release tests, but it I don't see any tests for 
crash recovery.

We do have a crash recovery test for encrypted databases 
(CryptoCrashRecovery), but that only runs on debug jars. So it has only 
been exercised by nightly/continuousIntegration tests on the 10.11 
branch, not on the release candidate itself.

I have some questions for the Store experts:

1) Does "Recovery after crashing engine" mean running 
CryptoCrashRecovery on the debug distribution of 10.11.1.1?

2) Does it entail some other, formal tests?

3) Or is it meant to cover some other ad-hoc tests which are run by hand 
and are not checked in under subversion?

Thanks,
-Rick