*ConfiguableTest.java and just exclude those.
Alan
-Original Message-
From: David Blevins [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 03, 2004 10:26 AM
To: [EMAIL PROTECTED]
Subject: Re: Unit/Stress Tests
On Tue, Aug 03, 2004 at 08:41:44AM -0400, Alan D. Cabrera wrote:
IMHO
On Wed, Aug 04, 2004 at 05:01:57PM -0500, Dain Sundstrom wrote:
On Aug 3, 2004, at 2:09 PM, Dain Sundstrom wrote:
That's basically a 20 minute difference with only 4.5 minutes
reportedly spend on our tests. What is taking up the other 15
minutes? Is setUp/tearDown not counted in the test
Before we jump off the cliff here, just how long do the stress tests
currently take? I don't think it is a significant fraction of the
build time. I recall trying this idea of isolating stress tests in
jboss builds and it turned into a real mess. Noone likes maintaining
the test system,
On Tue, Aug 03, 2004 at 09:19:54AM -0700, David Jencks wrote:
Before we jump off the cliff here, just how long do the stress tests
currently take?
Ok, never mind, I retract the idea. I just ran some comparisons and
came out with some interesting numbers.
On my 3Ghz WinXP/Cygwin box, these
I think the reason our stress tests don't take very long, is we are
limiting them because we don't want the build to take a long time. I
think once we remove this limitation the test time will grow and we
will get actual stress testing.
-dain
On Aug 3, 2004, at 11:19 AM, David Jencks wrote:
