From: Ian Arkver <ian.arkver.dev@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Need arm64/qemu help
Date: Mon, 5 Mar 2018 22:10:17 +0000 [thread overview]
Message-ID: <82357905-d251-7d83-dd8b-5787e65d8a0a@gmail.com> (raw)
In-Reply-To: <1520101306.3436.60.camel@linuxfoundation.org>
On 03/03/18 18:21, Richard Purdie wrote:
> On Sat, 2018-03-03 at 09:00 +0000, Richard Purdie wrote:
>> Hi,
>>
>> I need some help with a problem we keep seeing:
>>
>> https://autobuilder.yocto.io/builders/nightly-arm64/builds/798
>>
>> Basically, now and again, for reasons we don't understand, all the
>> sanity tests fail for qemuarm64.
>
> Another failure:
>
> https://autobuilder.yocto.io/builders/nightly-arm64/builds/801/steps/Running%20Sanity%20Tests/logs/stdio
>
> In this case one testimage failed, the others passed...
Interesting, re your comments on host load affecting all runs.
I was going to ask about repeatability over qemu/kernel builds, but here
we have 3 instances of the same qemu and kernel binaries only one of
which fails.
I've done some limited testing, but haven't been able to reproduce this
on my single build machine. Every aarch64 boot works ok for me, and the
ping test completes. I only tried core-image-minimal. I tried
cleansstate'ing the kernel and/or qemu-native and remaking, but no
change. Poky commit I tried was
master:bd5424f5b05a0a65471a77632efe7b9907370217
Regards,
Ian
>
> Cheers,
>
> Richard
>
prev parent reply other threads:[~2018-03-05 22:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-03 9:00 Need arm64/qemu help Richard Purdie
2018-03-03 10:51 ` Ian Arkver
2018-03-03 11:06 ` Richard Purdie
2018-03-03 11:13 ` Ian Arkver
2018-03-11 0:11 ` Victor Kamensky
2018-03-11 14:05 ` Richard Purdie
[not found] ` <CAFEAcA-d6-_tVRWKbZpVsQtece4fjuUqF+o+-m-AG4jPUHPY4g@mail.gmail.com>
2018-03-12 2:25 ` Victor Kamensky
2018-03-17 22:51 ` Victor Kamensky
[not found] ` <87a7v4kj5g.fsf@linaro.org>
2018-03-19 6:26 ` Victor Kamensky
[not found] ` <87605sjvk4.fsf@linaro.org>
2018-03-19 17:46 ` Victor Kamensky
[not found] ` <CAFEAcA8p9uO_7MXzkqyAnc-gifTHhmUgyRyE8X7hZnW=sbgQOg@mail.gmail.com>
2018-03-19 23:24 ` Victor Kamensky
[not found] ` <e15e3ca1-ee9e-1efa-2247-2789aac05091@linaro.org>
2018-03-20 2:22 ` Victor Kamensky
[not found] ` <874llbk1xc.fsf@linaro.org>
2018-03-20 2:14 ` Victor Kamensky
2018-03-03 18:21 ` Richard Purdie
2018-03-05 22:10 ` Ian Arkver [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=82357905-d251-7d83-dd8b-5787e65d8a0a@gmail.com \
--to=ian.arkver.dev@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.