On 17 October 2012 17:47, Dave Pigott dave.pigott@linaro.org wrote:

That is very weird:

http://staging.validation.linaro.org/scheduler/job/34124/log_file#entry16

<LAVA_DISPATCHER>2012-10-17 09:17:03 AM INFO: [ACTION-E] deploy_linaro_image is finished successfully. <LAVA_DISPATCHER>2012-10-17 09:17:03 AM INFO: [ACTION-B] boot_linaro_image is started with {} <LAVA_DISPATCHER>2012-10-17 09:17:03 AM INFO: Boot the test image <LAVA_DISPATCHER>2012-10-17 09:17:03 AM ERROR: boot_linaro_image failed

All the time stamps are within a second, and it doesn't appear it tried to do anything else.

This can be understood, they are the steps before and after I think.

Thanks, Yongqin Liu

Dave

On 17 Oct 2012, at 10:42, YongQin Liu yongqin.liu@linaro.org wrote:

Hi, All

In my afternoon, the jobs on staging failed to run due to the following error: http://staging.validation.linaro.org/scheduler/job/34124/log_file

Traceback (most recent call last): File "/srv/lava/branches/lava-dispatcher/lava_dispatcher/actions/boot_control.py", line 63, in run client.boot_linaro_image() File "/srv/lava/branches/lava-dispatcher/lava_dispatcher/client/base.py", line 365, in boot_linaro_image self._boot_linaro_image() File "/srv/lava/branches/lava-dispatcher/lava_dispatcher/client/targetdevice.py", line 68, in _boot_linaro_image self.proc = self.target_device.power_on() File "/srv/lava/branches/lava-dispatcher/lava_dispatcher/device/master.py", line 77, in power_on self._boot_linaro_image() File "/srv/lava/branches/lava-dispatcher/lava_dispatcher/device/master.py", line 403, in _boot_linaro_image boot_cmds = self.deployment_data['boot_cmds'] KeyError: 'boot_cmds'

I can run the jobs in my morning.

-- Thanks, Yongqin Liu

---

#mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android linaro-validation@lists.linaro.org http://lists.linaro.org/pipermail/linaro-validation

---

linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation

On 17 October 2012 22:36, Andy Doan andy.doan@linaro.org wrote:

On 10/17/2012 04:42 AM, YongQin Liu wrote:

...

Hi, All

In my afternoon, the jobs on staging failed to run due to the following error: http://staging.validation.linaro.org/scheduler/job/34124/log_file

Traceback (most recent call last): File "/srv/lava/branches/lava-dispatcher/lava_dispatcher/actions/boot_control.py", line 63, in run client.boot_linaro_image() File "/srv/lava/branches/lava-dispatcher/lava_dispatcher/client/base.py", line 365, in boot_linaro_image self._boot_linaro_image() File "/srv/lava/branches/lava-dispatcher/lava_dispatcher/client/targetdevice.py", line 68, in _boot_linaro_image self.proc = self.target_device.power_on() File "/srv/lava/branches/lava-dispatcher/lava_dispatcher/device/master.py", line 77, in power_on self._boot_linaro_image() File "/srv/lava/branches/lava-dispatcher/lava_dispatcher/device/master.py", line 403, in _boot_linaro_image boot_cmds = self.deployment_data['boot_cmds'] KeyError: 'boot_cmds'

I can run the jobs in my morning.

I see the bug, I think. I believe its a problem in our health check logic on this new branch. Will be fixed today.

If it's the problem of the health job, then do we also need to update the post-build-lava.py in android-build for generating the right android job file?

On 17 October 2012 22:53, Andy Doan andy.doan@linaro.org wrote:

On 10/17/2012 09:49 AM, YongQin Liu wrote:

...

If it's the problem of the health job, then do we also need to update the post-build-lava.py in android-build for generating the right android job file?

post-build-lava.py shouldn't have anything related to health jobs in it. This is a regression bug, so nothing should change except in my poorly written code :)

OK, I see, thanks for the answer. I have this question just because I can see the difference between the health job logic and normal android job logic.