Closed
Bug 663363
Opened 13 years ago
Closed 13 years ago
addRetryEvaluateCommand shouldn't ignore timeout parameter
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rail, Assigned: bhearsum)
Details
Attachments
(1 obsolete file)
addRetryEvaluateCommand wraps shell commands and run them using retry.py. ATM, addRetryEvaluateCommand doesn't pass timeout parameter to retry.py, so it always uses its own default 300s.
Attachment #538489 -
Flags: review?(bhearsum)
|
Reporter | |
Comment 1•13 years ago
|
||
Worked fine in staging.
|
Assignee | |
Updated•13 years ago
|
Attachment #538489 -
Flags: review?(bhearsum) → review+
|
|
Assignee | |
Comment 2•13 years ago
|
||
Comment on attachment 538489 [details] [diff] [review] addRetryEvaluateCommand timeout Landed this on default. I don't see any instances of this failing in production, so no need to rush through a reconfig for it.
Attachment #538489 -
Flags: checked-in+
|
||
Comment 3•13 years ago
|
||
Comment on attachment 538489 [details] [diff] [review] addRetryEvaluateCommand timeout Backed out due to backing out bug 613953.
Attachment #538489 -
Flags: checked-in+ → checked-in-
|
|
Assignee | |
Updated•13 years ago
|
Attachment #538489 -
Attachment is obsolete: true
|
|
Assignee | |
Comment 4•13 years ago
|
||
fixed by the latest patch in bug 613953.
Status: NEW → RESOLVED
Closed: 13 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
•