Closed
Bug 1130339
Opened 11 years ago
Closed 11 years ago
Investigate issues with b2g-23.1 and b2g-24.2
Categories
(Firefox OS Graveyard :: Infrastructure, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: viorela, Unassigned)
Details
It looks like b2g-23.1 crashed while non-smoktests have run on it: http://jenkins1.qa.scl3.mozilla.com/job/flame-kk-319.mozilla-central.nightly.ui.functional.non-smoke.1/8/console
The device fails to restart, as seen from the stacktrace.
Please take a look to see what is wrong with that device.
I will put it offline meanwhile: http://jenkins1.qa.scl3.mozilla.com/computer/b2g-23.1/
| Reporter | ||
Updated•11 years ago
|
Flags: needinfo?(gmealer)
| Reporter | ||
Comment 1•11 years ago
|
||
Same thing happened with b2g-24.2: http://jenkins1.qa.scl3.mozilla.com/job/flame-kk-319.mozilla-central.nightly.ui.functional.non-smoke.2/8/console.
Please investigate that node too.
| Reporter | ||
Updated•11 years ago
|
Summary: Investigate issues with b2g-23.1 → Investigate issues with b2g-23.1 and b2g-24.2
I don't currently see issues with them, so bringing them back online. Keeping the needinfo to remind myself to check back.
Both machines seem to be executing tests OK now.
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(gmealer)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•