On 4 October 2013 15:30, Antonio Terceiro <antonio.terce...@linaro.org> wrote:
> On Thu, Oct 03, 2013 at 01:23:14PM +0300, Fathi Boudra wrote:
>> Our aarch64 support doesn't use QEMU. We use OE and extract archives
>> of cross-built binaries.
>>
>> According to previous comments, the problem is that we try to run
>> Ubuntu specific commands.
>> Most likely because LAVA code path detects the rootfs and seems to
>> think it's Ubuntu.
>>
>> In BE case, LAVA behavior should be similar to aarch64:
>> - LAVA detects OE
>> - we don't run native OS commands but only extract archives (QEMU
>> isn't involved, or flash-kernel...)
>
> Actually those commands are run regardless of which OS is in the image, but on
> little endian images it is harmless. The fix for this is to make the second
> commmand (the one that failed aborting the job) condition on the first one,
> which is allowed to fail:
>
> https://git.linaro.org/gitweb?p=lava/lava-dispatcher.git;a=commitdiff;h=3cb7985bab6593e14c30f3312f6dbe83c6e4488d

ah I thought it wasn't run at all with aarch64. In any case, it should
behave like aarch64 :)

> With this change in, I was able to reproduce that job up to the point of
> booting the big endian kernel - but the kernel does not boot:
>
> https://staging.validation.linaro.org/scheduler/job/3369/log_file

LNG kernel issue. The fix in LAVA will do the trick.

> (note that is the staging LAVA server, I will be looking into deploying this
> change to the production server later today)

Thanks.

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

Reply via email to