Unable to run cros tryjob hwtest for guado_moblab |
||
Issue descriptionI tried on two separate machines to exclude the hardware being the issue but the tryjob does not seem to be able to provision the moblab Command was cros tryjob --remote -g 1100297 guado_moblab-paladin-tryjob --hwtest Build bucket: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8943703074664376944 From the logs http://cros-full-0013.mtv.corp.google.com/results/208571908-chromeos-test/chromeos2-row1-rack8-host5/debug/autoserv.DEBUG DevServerException: CrOS auto-update failed for host chromeos2-row1-rack8-host5: 0) RootfsUpdateError: Failed to perform rootfs update: DevServerStartupError('Timeout (30) waiting for remote devserver port_file',), 1) RootfsUpdateError: Failed to perform rootfs update: DevServerStartupError('Timeout (30) waiting for remote devserver port_file',) Previous attempt was https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?id=2665188 Similar dev server errors in http://cros-full-0013.mtv.corp.google.com/results/208527590-chromeos-test/chromeos2-row2-rack8-host11/provision_AutoUpdate/debug/
,
Jun 20 2018
I see this successful tryjob - thanks for the fix. https://ci.chromium.org/p/chromeos/builders/luci.chromeos.general/Try/b8943249388377048672 |
||
►
Sign in to add a comment |
||
Comment 1 by jrbarnette@chromium.org
, Jun 20 2018> [ ... ] update: DevServerStartupError('Timeout (30) waiting for remote devserver port_file',) [ ... ] This message means that the devserver based AU wasn't able to install and start a devserver on the moblab instance. That's attempted because quick-provision is disabled for tryjobs. There's a new provisioning flow that's driven from Autotest instead of the devserver. That flow won't try and start a devserver on the moblab. I can't guarantee that the new flow will work any better for tryjobs, but we're committed to support that flow in future, whereas the devserver-based flow is committed to go to the chopping block. As of 17:40 or so today, the new flow is enabled for moblab, so we should find out how the new flow behaves before we decide our next steps.