You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Michael Dick (JIRA)" <ji...@apache.org> on 2009/07/23 16:53:15 UTC
[jira] Created: (OPENJPA-1194) LockManager tests call
platformSpeedTest() for every test method
LockManager tests call platformSpeedTest() for every test method
----------------------------------------------------------------
Key: OPENJPA-1194
URL: https://issues.apache.org/jira/browse/OPENJPA-1194
Project: OpenJPA
Issue Type: Sub-task
Affects Versions: 2.0.0
Reporter: Michael Dick
Priority: Minor
The platformSpeedTest method is used to get a rough estimate of how fast the system is and from that determine how long we need to wait when running lock manager tests. It seems unlikely that this will change dramatically between test methods within a single class so it'd be better to find a way to cache the value without re-running the test.
The test appears to be quick, but it's still largely wasted cycles.
Unfortunately this is one of the areas where junit3 is limited - it's very tricky to initialize once per class (junit4 and testNG appear to be better at this), but we should be able to execute it only once per class.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (OPENJPA-1194) LockManager tests call
platformSpeedTest() for every test method
Posted by "Michael Dick (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Dick closed OPENJPA-1194.
---------------------------------
Resolution: Fixed
> LockManager tests call platformSpeedTest() for every test method
> ----------------------------------------------------------------
>
> Key: OPENJPA-1194
> URL: https://issues.apache.org/jira/browse/OPENJPA-1194
> Project: OpenJPA
> Issue Type: Sub-task
> Reporter: Michael Dick
> Assignee: Michael Dick
> Priority: Minor
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> The platformSpeedTest method is used to get a rough estimate of how fast the system is and from that determine how long we need to wait when running lock manager tests. It seems unlikely that this will change dramatically between test methods within a single class so it'd be better to find a way to cache the value without re-running the test.
> The test appears to be quick, but it's still largely wasted cycles.
> Unfortunately this is one of the areas where junit3 is limited - it's very tricky to initialize once per class (junit4 and testNG appear to be better at this), but we should be able to execute it only once per class.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OPENJPA-1194) LockManager tests call
platformSpeedTest() for every test method
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods updated OPENJPA-1194:
----------------------------------
Affects Version/s: 2.0.0-M2
Fix Version/s: 2.0.0-M3
> LockManager tests call platformSpeedTest() for every test method
> ----------------------------------------------------------------
>
> Key: OPENJPA-1194
> URL: https://issues.apache.org/jira/browse/OPENJPA-1194
> Project: OpenJPA
> Issue Type: Sub-task
> Affects Versions: 2.0.0-M2
> Reporter: Michael Dick
> Assignee: Michael Dick
> Priority: Minor
> Fix For: 2.0.0-M3
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> The platformSpeedTest method is used to get a rough estimate of how fast the system is and from that determine how long we need to wait when running lock manager tests. It seems unlikely that this will change dramatically between test methods within a single class so it'd be better to find a way to cache the value without re-running the test.
> The test appears to be quick, but it's still largely wasted cycles.
> Unfortunately this is one of the areas where junit3 is limited - it's very tricky to initialize once per class (junit4 and testNG appear to be better at this), but we should be able to execute it only once per class.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OPENJPA-1194) LockManager tests call
platformSpeedTest() for every test method
Posted by "Michael Dick (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Dick updated OPENJPA-1194:
----------------------------------
Affects Version/s: (was: 2.0.0)
Assignee: Michael Dick
Remaining Estimate: 0h
Original Estimate: 0h
> LockManager tests call platformSpeedTest() for every test method
> ----------------------------------------------------------------
>
> Key: OPENJPA-1194
> URL: https://issues.apache.org/jira/browse/OPENJPA-1194
> Project: OpenJPA
> Issue Type: Sub-task
> Reporter: Michael Dick
> Assignee: Michael Dick
> Priority: Minor
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> The platformSpeedTest method is used to get a rough estimate of how fast the system is and from that determine how long we need to wait when running lock manager tests. It seems unlikely that this will change dramatically between test methods within a single class so it'd be better to find a way to cache the value without re-running the test.
> The test appears to be quick, but it's still largely wasted cycles.
> Unfortunately this is one of the areas where junit3 is limited - it's very tricky to initialize once per class (junit4 and testNG appear to be better at this), but we should be able to execute it only once per class.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.