Closed
Bug 597084
Opened 14 years ago
Closed 14 years ago
Bump fuzzing timeout to 1500 seconds
Categories
(Release Engineering :: General, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: catlee, Assigned: catlee)
References
Details
Attachments
(1 file)
|
2.59 KB,
patch
|
lsblakk
:
review+
catlee
:
checked-in+
|
Details | Diff | Splinter Review |
There are some cases where fuzzing jobs are getting killed because they're taking longer than 1200 seconds with no output. This is mostly because stdout is being redirected to a local file. Jesse says that bumping this to 1500 seconds should be adequate to let the fuzzing timeout + browser hang timeout elapse.
|
Assignee | |
Updated•14 years ago
|
Summary: Bump fuzzing timeout to 1200 seconds → Bump fuzzing timeout to 1500 seconds
|
|
Assignee | |
Comment 1•14 years ago
|
||
Attachment #476162 -
Flags: review?(lsblakk)
|
||
Updated•14 years ago
|
Attachment #476162 -
Flags: review?(lsblakk) → review+
|
|
Assignee | |
Updated•14 years ago
|
Blocks: releng-downtime
|
|
Assignee | |
Updated•14 years ago
|
No longer blocks: releng-downtime
Depends on: 600224
|
||
Updated•14 years ago
|
|
|
||
Updated•14 years ago
|
Flags: needs-reconfig+
|
|
Assignee | |
Comment 2•14 years ago
|
||
Comment on attachment 476162 [details] [diff] [review]
Allow ScriptFactory to take timeout parameters
changeset: 964:1840dbe060e3
Attachment #476162 -
Flags: checked-in+
|
|
Assignee | |
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
|
||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•