ReleaseEngineering/Archive/Android Tegras: Difference between revisions

Jump to navigation Jump to search
m
Line 373: Line 373:
Failing states in mozpool:
Failing states in mozpool:


Seeing this 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 and
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.


<pre>
<pre>
Line 390: Line 390:
13:29:42    INFO - Waiting for request 'ready' stage.  Current state:  
13:29:42    INFO - Waiting for request 'ready' stage.  Current state:  
</pre>
</pre>
Sometimes this seems to be an intermittent error.  Buildbot assigns a slave for the build and when mozpool verifies it it doesn't get into a ready state within the timeouts specified in mozpool.  If this panda continues in this state, you should disable the slave from production runs and investigate.


Devices in the "failed_pxe_booting" state.  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.  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.
Confirmed users
1,989

edits

Navigation menu