Closed
Bug 1190883
Opened 9 years ago
Closed 6 years ago
Bitbar: Failed to contact device, due to time out.
Categories
(Firefox OS Graveyard :: Gaia::UI Tests, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: jlorenzo, Unassigned)
Details
05:06:38 [EnvInject] - Variables injected successfully. 05:06:38 [Testdroid] - Connecting to https://fxos.testdroid.com/testdroid-cloud as admin@localhost.com using proxy http://proxy.dmz.scl3.mozilla.com:3128 05:07:39 [Testdroid] - [ERROR] - Failed to retrieve device by build id Failed to execute API call: /runs. Reason: Read timed out 05:07:39 FATAL: com.testdroid.api.APIException: Failed to execute API call: /runs. Reason: Read timed out 05:07:39 java.io.IOException: com.testdroid.api.APIException: Failed to execute API call: /runs. Reason: Read timed out 05:07:39 at jenkins.plugins.testdroid.DeviceSessionWrapper.setUp(DeviceSessionWrapper.java:149) 05:07:39 at hudson.model.Build$BuildExecution.doRun(Build.java:154) 05:07:39 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) 05:07:39 at hudson.model.Run.execute(Run.java:1759) 05:07:39 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 05:07:39 at hudson.model.ResourceController.execute(ResourceController.java:89) 05:07:39 at hudson.model.Executor.run(Executor.java:240) 05:07:39 Caused by: com.testdroid.api.APIException: Failed to execute API call: /runs. Reason: Read timed out 05:07:39 at com.testdroid.api.DefaultAPIClient.postOnce(DefaultAPIClient.java:514) 05:07:39 at com.testdroid.api.DefaultAPIClient.post(DefaultAPIClient.java:418) 05:07:39 at jenkins.plugins.testdroid.DeviceSessionWrapper.flashDevice(DeviceSessionWrapper.java:460) 05:07:39 at jenkins.plugins.testdroid.DeviceSessionWrapper.getDevice(DeviceSessionWrapper.java:406) 05:07:39 at jenkins.plugins.testdroid.DeviceSessionWrapper.setUp(DeviceSessionWrapper.java:146) 05:07:39 ... 6 more
Comment 1•6 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•