Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Date: Wed, 01 Jun 2005 11:10:06 +0200
From: Oystein.Grovlen@Sun.COM (=?iso-8859-1?q?=D8ystein_Gr=F8vlen?=)
Subject: Re: looking for opinions on reasonable hardware requirements for
 tests
 in standard derby suite
In-reply-to: <429CC746.5000309@sbcglobal.net>
To: Derby Development <derby-dev@db.apache.org>
Message-id: <x1ofoeaqxx1t.fsf@atum11.Norway.Sun.COM>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 8BIT
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.2
Lines: 23
References: <429CC746.5000309@sbcglobal.net>

>>>>> "MM" == Mike Matrigali <mikem_app@sbcglobal.net> writes:

    MM> Another category would be long running stress tests.  It would
    MM> be nice to have a set of tests that run longer than seconds
    MM> to minutes, but not reasonable to expect everyone to include
    MM> 10 hour stress test runs in their nightly checkins.

    MM> I would still like almost all tests to be included in derbyall,
    MM> but it would seem reasonable for there to be a small suite
    MM> which hopefully could be set up to be automatically run on
    MM> some interval - worst case at least before a release.

I agree with you.  We need a testsuite for long-running tests and
large data volumes.  I have a feeling that due to the way we do
testing, the robustness of Derby for large data volumes are not the
best.  I know David had some recovery problems when doing a large data
volume test.

Hopefully, we can get someone to host the running of such a suite at
least every week.

-- 
�ystein