Closed
Bug 757062
Opened 13 years ago
Closed 13 years ago
Bughunter - handle oom and oof file errors better.
Categories
(Testing Graveyard :: Sisyphus, defect)
Testing Graveyard
Sisyphus
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bc, Assigned: bc)
Details
Attachments
(1 file)
|
6.57 KB,
patch
|
Details | Diff | Splinter Review |
Bughunter's crashworkers currently can get into a bad state if the worker runs out of memory.
This can occur due to a test url which consumes all or most of the memory on the machine which then results in cascading failures in Bughunter's scripts which fail due to out of memory conditions. These cascading failures can also cause Bughunter to leave open file handles which accumulate until there are no more handles available.
To fix this, catch out of memory errors as early as possible during the Popen call to test the url as well as to encapulate the entire call to runTest to catch any cascading failures before they affect the entire worker. Attempt to recover by reloading the program and if not possible to recover, then exit.
Another area where out of memory errors can affect the worker is the during the processing of ASSERTION stacks via fix_stack_using_bpsyms.py. Encapsulate the calls to fixSimples in a similar fashion and in the event of an out of memory condition simply copy the raw input to output rather than failing.
| Assignee | ||
Comment 1•13 years ago
|
||
| Assignee | ||
Comment 2•13 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•