Thanks everyone for the help,
It was actually due to the changing the Arthur's test definition to download the recent fastboot from dl.google.com, but not installing wget (and gzip) packages which are needed for that. I've restarted the jenkins job which submits the test - let's see where it fails this time :)
Thanks, Andrey
On 20.10.2017 09:19, Neil Williams wrote:
On 20 October 2017 at 07:05, Arthur She <arthur.she@linaro.org mailto:arthur.she@linaro.org> wrote:
Hi, I got a problem in LAVA v2.You've actually got a problem with the image transfer stage: https://staging.validation.linaro.org/scheduler/job/188583#L356 and https://staging.validation.linaro.org/scheduler/job/185376#L351
This could have led to a broken image being used.
You've misread the LAVA test log - this is not the uefi menu timing out, this is that the supplied kernel didn't boot - probably because the transfer failed in fastboot. This in turn could well be an intermittent hardware fault - these are dev boards after all.
My test jobs failed due to uefi-menu-selector timeout occasionally. Like this one <https://staging.validation.linaro.org/scheduler/job/188583> and this one <https://staging.validation.linaro.org/scheduler/job/185376>. When it happened, I usually re-submit the test job and, sometimes, it got recovery and had the test job run successfully, like this <https://staging.validation.linaro.org/scheduler/job/185377>. However, we're working on our own CI loop now, the test job <https://staging.validation.linaro.org/scheduler/job/194340> is submitted automatically. It doesn't make sense to re-submit the test job. Any ideas? Thanks, Arthur _______________________________________________ Lava-users mailing list Lava-users@lists.linaro.org <mailto:Lava-users@lists.linaro.org> https://lists.linaro.org/mailman/listinfo/lava-users <https://lists.linaro.org/mailman/listinfo/lava-users>--
Neil Williams
neil.williams@linaro.org mailto:neil.williams@linaro.org http://www.linux.codehelp.co.uk/