Closed
Bug 691916
Opened 13 years ago
Closed 12 years ago
Android Tegra purple: Configure Device exception with Remote Device Error: current resolution X:1366 Y:768 does not match what was set X:1680 Y:1050
Categories
(Release Engineering :: General, defect, P3)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: mbrubeck, Unassigned)
References
Details
(Keywords: intermittent-failure, Whiteboard: [android][tegra][purple])
https://tbpl.mozilla.org/php/getParsedLog.php?id=6675142&tree=Mozilla-Beta Android Tegra 250 mozilla-beta opt test mochitest-2 on 2011-10-04 12:28:03 PDT for push 0e269b0cf409 builder: mozilla-beta_tegra_android_test-crashtest slave: tegra-019 starttime: 1317756360.94 results: exception (4) buildid: 20111004103832 builduid: 3e417fe4f68243b2affd0dc898160dcf revision: 0e269b0cf409b3e4c30d035305b2a8cfee65d900 ========= Started Configure Device exception (results: 4, elapsed: 3 mins, 43 secs) ========== python /builds/sut_tools/config.py 10.250.49.6 crashtest in dir /builds/tegra-019/test/. (timeout 1200 secs) watching logfiles {} argv: ['python', '/builds/sut_tools/config.py', '10.250.49.6', 'crashtest'] environment: PATH=/opt/local/bin:/opt/local/sbin:/opt/local/Library/Frameworks/Python.framework/Versions/2.6/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin PWD=/builds/tegra-019/test SUT_IP=10.250.49.6 SUT_NAME=tegra-019 __CF_USER_TEXT_ENCODING=0x1F6:0:0 closing stdin using PTY: False connecting to: 10.250.49.6 reconnecting socket devroot /mnt/sdcard/tests results: {'screen': ['X:1024 Y:768']} current resolution X:1024 Y:768 /builds/tegra-019/test/../proxy.flg results: {'os': ['harmony-eng 2.2 FRF91 20101105.183900 test-keys']} results: {'screen': ['X:1024 Y:768']} INFO: we have a current resolution of 1024, 768 INFO: adjusting screen resolution to 1680, 1050 and rebooting DEBUG: gCallbackData is: on port: 50019 Creating server with 10.250.48.200:50019 Calling disconnect on callback server . Got data back from agent: System rebooted Shutting down server now System rebooted Waiting for tegra to come back... Try 1 reconnecting socket devroot /mnt/sdcard/tests results: {'screen': ['X:1366 Y:768']} current resolution X:1366 Y:768 /builds/tegra-019/test/../error.flg Remote Device Error: current resolution X:1366 Y:768 does not match what was set X:1680 Y:1050 process killed by signal 15 program finished with exit code -1 elapsedTime=223.043520 ======== Finished Configure Device exception (results: 4, elapsed: 3 mins, 43 secs) ========
Reporter | ||
Updated•13 years ago
|
Whiteboard: [android_tier_1][android][tegra][purple] → [android_tier_1][android][tegra][purple][orange]
Comment 1•13 years ago
|
||
Wrong log link? That one looks like a bug 689839, and doesn't seem to have a "remote device error" anywhere in it. FWIW, I talk about a similiar log (to the paste, not the link) with bear the other day, and his take on it was that the resolution, which it will reboot and try to reset multiple times, wasn't the problem, the problem was that just another "Tegra went away, here, have a 'process killed by signal 15' with a pancake on its head instead" happened to occur right after that resolution thing, which looks like a problem and looks related even if it's not.
Comment 2•13 years ago
|
||
Or more accurately, it's just the normal noises in here unless it's a Tegra over 94 (so it might be a new one that's broken) or the same Tegra doing it over and over (so it might be an old one that's broken).
Reporter | ||
Comment 3•13 years ago
|
||
(In reply to Phil Ringnalda (:philor) from comment #1) > Wrong log link? That one looks like a bug 689839, and doesn't seem to have a > "remote device error" anywhere in it. Good catch. The correct link is https://tbpl.mozilla.org/php/getParsedLog.php?id=6674299&tree=Mozilla-Beta
Comment 4•13 years ago
|
||
https://tbpl.mozilla.org/php/getParsedLog.php?id=6741885&tree=Mozilla-Aurora Android Tegra 250 mozilla-aurora opt test jsreftest-2 on 2011-10-08 01:09:51 PDT for push a929601e7a9e builder: mozilla-aurora_tegra_android_test-jsreftest-2 slave: tegra-110 starttime: 1318061391.33 results: exception (4) buildid: 20111008000158 builduid: 6a49f8d857a64f199efa601de6761f85 revision: a929601e7a9e873d5afe95090c1688cf323e9cbf connecting to: 10.250.49.98 reconnecting socket devroot /mnt/sdcard/tests results: {'screen': ['X:1024 Y:768']} current resolution X:1024 Y:768 /builds/tegra-110/test/../proxy.flg results: {'os': ['harmony-eng 2.2 FRF91 20101105.183900 test-keys']} results: {'screen': ['X:1024 Y:768']} INFO: we have a current resolution of 1024, 768 INFO: adjusting screen resolution to 1680, 1050 and rebooting DEBUG: gCallbackData is: on port: 50110 Creating server with 10.250.48.213:50110 Calling disconnect on callback server . Got data back from agent: System rebooted Shutting down server now System rebooted Waiting for tegra to come back... Try 1 reconnecting socket devroot /mnt/sdcard/tests results: {'screen': ['X:1366 Y:768']} current resolution X:1366 Y:768 /builds/tegra-110/test/../error.flg Remote Device Error: current resolution X:1366 Y:768 does not match what was set X:1680 Y:1050 program finished with exit code 1 elapsedTime=240.954953 Rather suspiciously lacks any sort of indication of the Tegra going away.
Updated•13 years ago
|
Whiteboard: [android_tier_1][android][tegra][purple][orange] → [android][tegra][purple][orange]
Updated•13 years ago
|
Whiteboard: [android][tegra][purple][orange] → [android][tegra][purple]
Updated•13 years ago
|
Whiteboard: [android][tegra][purple] → [android][tegra][purple][orange]
Updated•13 years ago
|
Priority: -- → P3
Comment 5•12 years ago
|
||
We're verifying the resolution now before we do the work, so this is no longer happening in production
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•12 years ago
|
Keywords: intermittent-failure
Assignee | ||
Updated•12 years ago
|
Whiteboard: [android][tegra][purple][orange] → [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
•