|
If you were logged in you would be able to see more operations.
|
|
|
|
Time Tracking:
|
|
Original Estimate:
|
3h
|
|
|
Remaining Estimate:
|
0h
|
|
|
Time Spent:
|
5h
|
|
|
|
| Severity: |
Usability
|
| Resolution Date: |
29/May/08 11:37 PM
|
|
The newly added thread safety tests (and possibly some of the existing ones) tend to run for a long time, consuming a lot of CPU cycles, and sometimes even failing due to a timeout (currently 300 seconds in nightly builds). It would be useful to provide a mechanism such as a command line option whereby the tests' runtime could be limited without necessarily causing them to fail when the amount of time is exceeded. One way to do it would be for each test to set an alarm in response to this command line option and in handler for the alarm set a flag that each thread would check at each iteration of its loop to see if it should break.
|
|
Description
|
The newly added thread safety tests (and possibly some of the existing ones) tend to run for a long time, consuming a lot of CPU cycles, and sometimes even failing due to a timeout (currently 300 seconds in nightly builds). It would be useful to provide a mechanism such as a command line option whereby the tests' runtime could be limited without necessarily causing them to fail when the amount of time is exceeded. One way to do it would be for each test to set an alarm in response to this command line option and in handler for the alarm set a flag that each thread would check at each iteration of its loop to see if it should break. |
Show » |
logged work - 07/May/08 08:48 PM
| Time Worked: |
4h |
|
<No comment>
|
logged work - 22/May/08 03:33 PM
|
Improvement
Resolved
Major
allow thread safety tests to time out without failing
