Bump fuzzing timeout to 1500 seconds

RESOLVED FIXED

Status

P3
normal
RESOLVED FIXED
8 years ago
5 years ago

People

(Reporter: catlee, Assigned: catlee)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

8 years ago
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

8 years ago
Summary: Bump fuzzing timeout to 1200 seconds → Bump fuzzing timeout to 1500 seconds
(Assignee)

Comment 1

8 years ago
Created attachment 476162 [details] [diff] [review]
Allow ScriptFactory to take timeout parameters
Attachment #476162 - Flags: review?(lsblakk)
Attachment #476162 - Flags: review?(lsblakk) → review+
(Assignee)

Updated

8 years ago
Blocks: 593081
(Assignee)

Updated

8 years ago
No longer blocks: 593081
Depends on: 600224
Blocks: 600224
No longer depends on: 600224
Flags: needs-reconfig+
(Assignee)

Comment 2

8 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

8 years ago
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.