Closed
Bug 692662
Opened 13 years ago
Closed 13 years ago
Intermittent Tegra "Cleanup Device exception" from "Remote Device Error: devRoot from devicemanager [/data/data/com.mozilla.SUTAgentAndroid/files/tests] is not correct"
Categories
(Release Engineering :: General, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mbrubeck, Unassigned)
References
Details
(Keywords: intermittent-failure, Whiteboard: [android_tier_1][android][tegra][purple])
+++ This bug was initially created as a clone of Bug #681855 +++
https://tbpl.mozilla.org/php/getParsedLog.php?id=6713074&tree=Mozilla-Aurora
Android Tegra 250 mozilla-aurora opt test reftest-2 on 2011-10-06 16:25:04 PDT for push 557b00e625d2
builder: mozilla-aurora_tegra_android_test-reftest-2
slave: tegra-116
starttime: 1317943504.34
results: exception (4)
buildid: 20111006150449
builduid: 1542f1c856234f1d922ad92399a82af3
revision: 557b00e625d266c507864cf6a4acf524a5fe6f50
========= Started Cleanup Device exception (results: 4, elapsed: 30 secs) ==========
python /builds/sut_tools/cleanup.py 10.250.50.26
in dir /builds/tegra-116/test/. (timeout 1200 secs)
watching logfiles {}
argv: ['python', '/builds/sut_tools/cleanup.py', '10.250.50.26']
environment:
PATH=/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
PWD=/builds/tegra-116/test
SUT_IP=10.250.50.26
SUT_NAME=tegra-116
__CF_USER_TEXT_ENCODING=0x1F5:0:0
closing stdin
using PTY: False
Connecting to: 10.250.50.26
reconnecting socket
send cmd: testroot
recv'ing...
response: /data/data/com.mozilla.SUTAgentAndroid/files
$>send cmd: cd /data/data/com.mozilla.SUTAgentAndroid/files/tests
recv'ing...
response: $>send cmd: cwd
recv'ing...
response: /data/data/com.mozilla.SUTAgentAndroid/files/tests
$>devroot /data/data/com.mozilla.SUTAgentAndroid/files/tests
/builds/tegra-116/test/../error.flg
Remote Device Error: devRoot from devicemanager [/data/data/com.mozilla.SUTAgentAndroid/files/tests] is not correct
program finished with exit code 1
elapsedTime=30.285996
======== Finished Cleanup Device exception (results: 4, elapsed: 30 secs) ========
Comment 1•13 years ago
|
||
https://tbpl.mozilla.org/php/getParsedLog.php?id=6724344&tree=Mozilla-Inbound
https://tbpl.mozilla.org/php/getParsedLog.php?id=6725473&tree=Mozilla-Inbound
https://tbpl.mozilla.org/php/getParsedLog.php?id=6723267&tree=Mozilla-Inbound
https://tbpl.mozilla.org/php/getParsedLog.php?id=6722634&tree=Mozilla-Inbound
https://tbpl.mozilla.org/php/getParsedLog.php?id=6720016&tree=Mozilla-Inbound
Comment 2•13 years ago
|
||
Comment 3•13 years ago
|
||
Reporter | ||
Comment 4•13 years ago
|
||
Comment 5•13 years ago
|
||
Comment 6•13 years ago
|
||
Comment 7•13 years ago
|
||
Comment 8•13 years ago
|
||
These generally mean that the sdcard has gone bad, and we should replace it.
Comment 9•13 years ago
|
||
Filed bug 693013 for tegra-116, so we can leave this open to catch the next one that goes bad the same way (bugs being where I keep most of my memory).
Comment 10•13 years ago
|
||
fixed according to aki, reopen if we see this again
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•12 years ago
|
Keywords: intermittent-failure
Assignee | ||
Updated•12 years ago
|
Whiteboard: [android_tier_1][android][tegra][purple][orange] → [android_tier_1][android][tegra][purple]
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•