Closed Bug 919920 Opened 11 years ago Closed 9 years ago

Intermittent TEST-UNEXPECTED-FAIL | remotereftests.py | Timed out while waiting for server startup.

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Platform:
ARM
Android
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: cbook, Unassigned)

References

(Depends on 1 open bug,
URL
)

Details

(Keywords: intermittent-failure) 

Android 2.2 Armv6 Tegra mozilla-aurora opt test plain-reftest-2 on 2013-09-24 00:52:31 PDT for push 12802f082fff

slave: tegra-057

https://tbpl.mozilla.org/php/getParsedLog.php?id=28273216&tree=Mozilla-Aurora

TEST-UNEXPECTED-FAIL | remotereftests.py | Timed out while waiting for server startup.

i guess have something to do with reaching the server
Jeff, this seems like maybe a mozharness issue? Could you please take a look? This is one of our top oranges across all branches.
Flags: needinfo?(jhammel)
Actually, looks like Ted already did some analysis over in bug 915212. Chris, can you please look into this?
Depends on: 915212
Flags: needinfo?(jhammel) → needinfo?(catlee)
For tegra tests we most certainly do not reboot the foopies between test runs. Is that where the test server runs?
Flags: needinfo?(catlee)
(In reply to Chris AtLee [:catlee] from comment #52)
> For tegra tests we most certainly do not reboot the foopies between test
> runs. Is that where the test server runs?

I responded to that question in bug 915212, since that bug seems to have more analysis of the problem. But, yes, that is where the http server for mochitest is running (on the foopy).
Bug 1011207 likely explains the recent Android 2.3 failures.
Assignee: nobody → gbrown
Assignee: gbrown → nobody
Inactive; closing (see bug 1180138).
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.