Closed
Bug 916415
Opened 11 years ago
Closed 11 years ago
When a device is busy, mozpool log is uninformative
Categories
(Testing Graveyard :: Mozpool, defect)
Testing Graveyard
Mozpool
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Callek, Assigned: dustin)
Details
Attachments
(1 file)
1.43 KB,
patch
|
Callek
:
review+
|
Details | Diff | Splinter Review |
2013-09-10T05:40:45 statemachine Requested device None is busy. (e.g. from http://mobile-imaging-001.p1.releng.scl1.mozilla.com/ui/log.html?request=392595) This is an issue because we never set |device_name| except in the success case of http://mxr.mozilla.org/build/source/mozpool/mozpool/mozpool/requestmachine.py#126 * set at L128 * Get list of avail devices: L134 * If avil devices \-Set device_name to one of those devices L148 * else (no avail devices) \-Report this line with uninitialized var L163
Assignee | ||
Updated•11 years ago
|
Assignee: relops → dustin
Component: RelOps → Mozpool
Product: Infrastructure & Operations → Testing
QA Contact: arich
Version: other → unspecified
Assignee | ||
Updated•11 years ago
|
Summary: [mozpool] When a device is busy, mozpool log is uninformative → When a device is busy, mozpool log is uninformative
Assignee | ||
Comment 1•11 years ago
|
||
Attachment #807339 -
Flags: review?(bugspam.Callek)
Reporter | ||
Updated•11 years ago
|
Attachment #807339 -
Flags: review?(bugspam.Callek) → review+
Assignee | ||
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•