[
https://issues.apache.org/jira/browse/OPENJPA-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick updated OPENJPA-1071:
--
Fix Version/s: 1.2.2
1.0.4
> Derby test suit speed
1.3.0
> Derby test suit speed-up
>
>
> Key: OPENJPA-1071
> URL: https://issues.apache.org/jira/browse/OPENJPA-1071
> Project: OpenJPA
> Issue Type: Test
> Components
[
https://issues.apache.org/jira/browse/OPENJPA-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods resolved OPENJPA-1071.
---
Resolution: Fixed
Trunk updated with OPENJPA-1210
> Derby test suit speed
[
https://issues.apache.org/jira/browse/OPENJPA-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on OPENJPA-1071 started by Donald Woods.
> Derby test suit speed-up
>
>
> Key: OPENJPA-1071
>
ects Versions: 1.0.3, 1.2.1
>Reporter: Donald Woods
>Assignee: Donald Woods
>Priority: Minor
> Fix For: 1.0.4, 1.2.2, 1.3.0, 2.0.0
>
>
> See dev discussion thread -
> http://n2.nabble.com/Derby-test-suit-speed-up-td2548968.html
2685 reduced the build + test time for
openjpa-persistence-jdbc on my Mac from 16:41 down to 9:41 minutes with Sun
1.5.0_16.
Still working through the changes to trunk, as the new persistence.lockmgr
tests rely upon lock timeouts.
> Derby test suit s
Derby test suit speed-up
Key: OPENJPA-1071
URL: https://issues.apache.org/jira/browse/OPENJPA-1071
Project: OpenJPA
Issue Type: Test
Components: build / infrastructure
Affects Versions: 1.2.1, 1.0.3
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
;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.
>
>
http://n2.nabble.com/Derby-test-suit-speed-up-tp2548968p2736634.html
Sent from the OpenJPA Developers mailing list archive at Nabble.com.
Valid point, Donald.
I had another look at Derby manual [1] and I think we are quite safe if we also
specify derby.locks.deadlockTimeout [2] and make it less than
derby.locks.waitTimeout. This should assure we get deadlocks and timeouts as
before but faster.
Regards,
Milosz
[1]
http://db.apa
The tests may not break, but the results could be completely different
and passing for the wrong reason.
Seems that we should also set derby.locks.deadlockTrace
http://db.apache.org/derby/docs/10.0/manuals/tuning/perf79.html
and review the trace results, since a lot of the tests just catch an
Hello!
Good to know it also works outside my laptop!
It could be beneficial to find out which test cases benefit from specifying
Derby timeout. I suspect we have a few. One is TestException but this is
intentional. There might be others which deadlock and we do not want this. The
way to find t
+1. Tested on 1.0.x and it dropped the time for mvn clean test from nearly
10 minutes to just over 2.
I'll give it a try on other branches when I get a chance, but this looks
great to me. Thanks for finding it Milosz!
-mike
2009/3/28 Albert Lee
> +1, as you said, if not affecting any tests.
>
+1, as you said, if not affecting any tests.
On Sat, Mar 28, 2009 at 8:15 AM, Miłosz Tylenda wrote:
> Hi All!
>
> Have anybody experimented with setting default Derby timeout in our test
> suite? I have set the timeout to 5 seconds and the test suite execution time
> felt down from 34 to 19 minu
Hi All!
Have anybody experimented with setting default Derby timeout in our test suite?
I have set the timeout to 5 seconds and the test suite execution time felt down
from 34 to 19 minutes on my system. Part of my openjpa-persistence-jdbc pom.xml
looks like this:
16 matches
Mail list logo
