Closed Bug 774639 Opened 13 years ago Closed 13 years ago

Native Android talos remote-ts perma-failing on mozilla-beta after 2012-07-16 uplift

Categories

(Testing :: Talos, defect)

Product:
Testing
Component:
Talos
Version:
15 Branch
Platform:
ARM
Android
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(firefox15-)

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox15 - ---

People

(Reporter: emorley, Assigned: jmaher)

Details

appears to be that we are losing connection to the tegra. ts is running and producing numbers, but it loses connection somewhere in the middle and then further steps that access the tegra (like verify.py) fail to connect as well.
(In reply to Joel Maher (:jmaher) from comment #1) > appears to be that we are losing connection to the tegra. ts is running and > producing numbers, but it loses connection somewhere in the middle and then > further steps that access the tegra (like verify.py) fail to connect as well. Joel - are you in the best position to investigate this further? We won't want to ship a release of 15 until we know there aren't any regressions hiding behind this test. Thanks!
Assignee: nobody → jmaher
tracking-firefox15: ? → +
We've had some greens since, so I think it's just the usual craptastic Android reliability turned up a couple of notches, rather than perma-fail. (Albeit still like 80%). Latest failure: https://tbpl.mozilla.org/php/getParsedLog.php?id=13670301&tree=Mozilla-Beta
Our current theory is that the spurious mid-test reboots are coming from the automation code on the buildbot tools side of things. We can run the tests locally many times without any failures. We are continuing to debug...
there are plenty of green ts tests on mozilla-beta, it seems that ts fails as much as everything else.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
Resolution: INVALID → WORKSFORME
untracking for 15 given the resolution.
tracking-firefox15: + → -
You need to log in before you can comment on or make changes to this bug.