Confirmed users
1,989
edits
ReleaseEngineering/Archive/Android Tegras: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/Archive/Android Tegras (view source)
Revision as of 13:37, 2 July 2013
, 2 July 2013→How to deal with failing pandas in mozpool
| Line 373: | Line 373: | ||
Failing states in mozpool: | Failing states in mozpool: | ||
* These mesages in the log means that the panda requested by buildbot was not made available in the ready state in within the timeout parameters specified by mozpool. Sometimes this seems to be an intermittent error. If not, the panda should be disabled from production runs. | * These mesages in the log means that the panda requested by buildbot was not made available in the ready state in within the timeout parameters specified by mozpool. Sometimes this seems to be an intermittent error. If not, the panda should be disabled from production runs and a bug opened with DC Ops to investigate this device. | ||
<pre> | <pre> | ||
| Line 391: | Line 391: | ||
</pre> | </pre> | ||
* Devices in the "failed_pxe_booting" state in mozpool. Not sure what to do in this state since requests to reboot or reimage are refused because the device isn't available on the network. | * Devices in the "failed_pxe_booting" state in mozpool. Not sure what to do in this state since requests to reboot or reimage are refused because the device isn't available on the network. Opening a bug with DC Ops to investigate this device is a good first step. | ||
= References = | = References = | ||