Closed
Bug 746338
Opened 14 years ago
Closed 14 years ago
Clientproxy should not exit due to unknown returns from verify.py
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Callek, Assigned: Callek)
Details
Attachments
(1 file, 1 obsolete file)
|
1.32 KB,
patch
|
bear
:
review+
|
Details | Diff | Splinter Review |
When verify.py exits with an error code but does not create an error flag we currently sys.exit(1) making clientproxy hang/have problems.
This should stop.
[Built on top of Bug 746283 without which there will be conflicts]
Attachment #615882 -
Flags: review?(bear)
|
Assignee | |
Updated•14 years ago
|
Attachment #615882 -
Attachment is patch: true
|
|
Assignee | |
Updated•14 years ago
|
Attachment #615882 -
Attachment is obsolete: true
Attachment #615882 -
Flags: review?(bear)
|
||
Updated•14 years ago
|
Attachment #615885 -
Flags: review?(bear) → review+
|
|
Assignee | |
Comment 2•14 years ago
|
||
|
|
Assignee | |
Comment 3•14 years ago
|
||
This was already deployed
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
|
||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
|
|
||
Updated•8 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•