1206880 - Log files for Flame device 18.2 in the QA Lab

Status: RESOLVED WONTFIX

(Mozilla QA :: General, defect)

Description

[Michael Bryant (uber)]

Attachment: 2015-09-21-16-57-39-logs.zip

Attached are the log files for device 18.2 in the QA lab

Comment 1

[Michael Bryant (uber)]

Adding Eli and Naoki as requested

Comment 2

[:Eli Perelman]

I took a look at the logs but I didn't see anything strange that would alert me of a problem, but preface that with the fact that I'm not really sure what I'm looking for.

Comment 3

[:Eli Perelman]

Attachment: Link to Github Gist: https://gist.github.com/eliperelman/1863e91b41f88c430c56

Prior to the device showing not found in Jenkins, the previous Raptor test had died. This is the output of the logcat during that test, as well as stdout from Raptor.

Comment 4

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Next time this happens, can we try reconnecting the device via adb and trying to do an adb shell df?

Comment 5

[Michael Bryant (uber)]

Attachment: 19.1 adb shell mesg.txt

Log file using "adb shell mesg" command on phone 19.1 found in powered off state October 6, 2015

Comment 6

[Michael Bryant (uber)]

Attachment: 19.1 adb df.txt

Log file using "adb shell df" command on phone 19.1 found in powered off state October 6, 2015

Comment 7

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Odd.  I'm not sure what's going on.  I don't think the df captured what happened prior to the shutdown.
System partition seems to have enough space...

Comment 8

[Robert Wood [:rwood]]

Hopefully this won't happen anymore after we move to Raptor 5.0 and the new fxos-device-service. Closing this, if it reappears then will file a new bug accordingly.

Comment 9

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Clearing my name based on that decision.