676710 - Frequent Tegra exceptions from "Remote Device Error: Resolution change failed. Should be 1024/768 but is 0/0"

Status: RESOLVED INCOMPLETE

(Testing :: General, defect)

Description

[Phil Ringnalda (:philor)]

Either someone's lying or the screen is falling off the table while it reboots, but...

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1312494329.1312494856.31856.gz
Android Tegra 250 mozilla-central talos remote-tzoom on 2011/08/04 14:45:29
s: tegra-033

INFO: we have a current resolution of 1680, 1050
INFO: adjusting screen resolution to 1024, 768 and rebooting
calling reboot
Waiting for tegra to come back...
Try 1
devroot None
Try 2
devroot /mnt/sdcard/tests
results: {'screen': ['/mnt/sdcard/tests']}
/builds/tegra-033/talos-data/../error.flg
Remote Device Error: Resolution change failed.  Should be 1024/768 but is 0/0
program finished with exit code 1

...is a fair percentage of the purple runs where we then have to burn another run because I just blindly retrigger them whether we really needed them or not.

Comment 1

[Mike Taylor [:bear]]

SUTAgent is what is returning this value so I'm going to let the ateam have first crack at this bug

Comment 2

[Joel Maher ( :jmaher ) (UTC -8)]

a rare bug, I haven't been able to repro it, but I think we should leave this open to see if this crops up again.

Comment 3

[Phil Ringnalda (:philor)]

We RETRY on Remote Device Error, so since nobody ever looks at those we'll never know whether or not it happens.