Closed
Bug 1144207
Opened 9 years ago
Closed 9 years ago
Device b2g-07.1 encountering timeout exceptions in telephony cases
Categories
(Firefox OS Graveyard :: Infrastructure, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: onelson, Unassigned)
References
Details
Device b2g-07.1 encountered many problems with telephony cases in today's smoke run. On re-running these cases individually, the phone encountered the same problems: all time out exceptions. These tests were run adhoc on a separate device where none of the timeout exceptions were encountered. Advising investigation into the device in question. Failing mozilla-central-nightly.smoke run for 3/17 (device b2g-07.1): * http://jenkins1.qa.scl3.mozilla.com/job/flame-kk-319.mozilla-central.nightly.ui.functional.smoke/95/testReport/junit/ Failures reproed on device b2g-07.1: * http://jenkins1.qa.scl3.mozilla.com/job/flame-kk.ui.adhoc/727/ Failures not observed on different device (b2g-24.1): * http://jenkins1.qa.scl3.mozilla.com/job/flame-kk.ui.adhoc/728/ Test Failures were: [Not Reproduced manually] test_cost_control_data_alert_mobile_py [Not Reproduced manually] test_dialer_receive_call_with_locked_screen_py [Not Reproduced manually] test_browser_cell_data_py [Not Reproduced manually] test_dialer_receive_call_py [Not Reproduced manually] test_settings_cell_data_py [Not Reproduced manually] test_sms_contact_py [Not Reproduced manually] test_sms_py [Not Reproduced manually] test_sms_with_attachments_py [Not Reproduced manually] test_sms_with_picture_attached_py
Reporter | ||
Updated•9 years ago
|
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Flags: needinfo?(gmealer)
Looks like the crash in bug 1144224 takes down the cellular stack with it. I reset a bunch of phones that didn't show a cell signal, including b2g-07.1
Status: NEW → RESOLVED
Closed: 9 years ago
Depends on: 1144224
Flags: needinfo?(gmealer)
Resolution: --- → FIXED
Updated•9 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
You need to log in
before you can comment on or make changes to this bug.
Description
•