Closed
Bug 732183
Opened 14 years ago
Closed 14 years ago
sut_tools/check.py incorrectly handles when checkSlaveActive fails
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bear, Assigned: bear)
Details
(Whiteboard: [android][sut_tools])
Attachments
(1 file)
|
2.08 KB,
patch
|
hwine
:
review+
|
Details | Diff | Splinter Review |
logTD = checkSlaveActive(tegraPath)
logTD turns out can return as None and the existing check on line 127 of check.py fails causing an exception.
| Assignee | ||
Comment 1•14 years ago
|
||
Assignee: nobody → bear
Attachment #602102 -
Flags: review?(hwine)
| Assignee | ||
Updated•14 years ago
|
Whiteboard: [android][sut_tools]
| Assignee | ||
Comment 2•14 years ago
|
||
i'm testing this on foopy17 since it was tegra-198 that caused me to discover the bug
Comment on attachment 602102 [details] [diff] [review]
change handling of return value from check*Active() to handle None properly
Original defect was improper grouping of clauses, allowing logTD to be introspected even when None. Instead of making the conditionals more complex with yet another layer of parenthesis, this restructures to show more clearly logTD==None means status is INACTIVE.
approved as long as tests pass.
Attachment #602102 -
Flags: review?(hwine) → review+
| Assignee | ||
Comment 4•14 years ago
|
||
committed changeset 2291:b0f38fe095c3
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•13 years ago
|
Product: mozilla.org → Release Engineering
Updated•8 years ago
|
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Updated•6 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•