I created OPENJPA-1071 for this and will take a look at updating trunk
and 1.3.x today.
-Donald
Michael Dick wrote:
I've been meaning to get back to this topic too. Conceptually Milosz's
latest proposal seems sound to me.
Donald's concern is valid, but it should only apply to a minority of our
test suite. I'd venture a guess that there are only a couple dozen classes
that worry about specific reasons for transaction rollbacks.
As a branch maintainer for 1.2.x and 1.0.x I wouldn't want to commit the
changes until I'd looked into those testcases. For trunk / 1.3.x I'd be more
willing to accept the risk.
Any other thoughts? If there are no further concerns I'm happy to commit the
changes in the open releases.
-mike
On Tue, Apr 28, 2009 at 3:25 PM, Rick Curtis <[email protected]> wrote:
What ever happened with this topic? Is more investigation needed?
I ran through the entire UT bucket today and it took me just about a hour
on
my laptop. I'd love to see the amount of time required to run the tests get
somewhere less than 30 min!
-Rick
--
View this message in context:
http://n2.nabble.com/Derby-test-suit-speed-up-tp2548968p2736634.html
Sent from the OpenJPA Developers mailing list archive at Nabble.com.
