All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V4 00/11] runqemu: refactor it and remove machine knowledge
Date: Thu, 25 Aug 2016 22:52:35 +0100	[thread overview]
Message-ID: <1472161955.29583.1.camel@linuxfoundation.org> (raw)
In-Reply-To: <6ee635df-666d-90bb-b296-7aa76714cbcc@windriver.com>

Hi Robert,

On Thu, 2016-08-25 at 22:36 +0800, Robert Yang wrote:
> I've fixed the problem and will send a V5. I have tried to test it on
> my
> autobuilder, but it's running out of disk space last tonight. It is
> still in
> building today, and didn't see any problems by now, I will reply if I
> see.

We're getting closer, there was just one issue I noticed in the last
test run:

https://autobuilder.yoctoproject.org/main/builders/nightly-arm64/builds
/536/steps/Running%20Sanity%20Tests/logs/stdio

> > > and:
> > > 
> > > https://autobuilder.yoctoproject.org/main/builders/nightly-oe-sel
> > > ftest/builds/652/steps/Running%20oe-selftest/logs/stdio
> > > 
> > > 
> > > I'm also not sure what caused these, whether it was this patchset
> > > or
> > > not:
> > > 
> > > https://autobuilder.yoctoproject.org/main/builders/nightly-arm/bu
> > > ilds/927/steps/Running%20ESDK%20Sanity%20Tests/logs/stdio
> > > 
> > > https://autobuilder.yoctoproject.org/main/builders/nightly-mips/b
> > > uilds/901/steps/Running%20ESDK%20Sanity%20Tests/logs/stdio
> > > 
> > > https://autobuilder.yoctoproject.org/main/builders/nightly-ppc/bu
> > > ilds/914/steps/Running%20ESDK%20Sanity%20Tests/logs/stdio
> > > 
> > > https://autobuilder.yoctoproject.org/main/builders/nightly-x86/bu
> > > ilds/914/steps/Running%20ESDK%20Sanity%20Tests/logs/stdio
> > > 
> > > https://autobuilder.yoctoproject.org/main/builders/nightly-x86-64
> > > /builds/935
> > 
> > I'm not sure either, need more investigations.
> 
> I think that this isn't caused by runqemu patches since the error
> doesn't
> seem like relate to runqemu, and I can't reproduce it.

I think we can blame one of Ross' patches for this one!

Cheers,

Richard



  reply	other threads:[~2016-08-25 21:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-22  7:52 [PATCH V4 00/11] runqemu: refactor it and remove machine knowledge Robert Yang
2016-08-22  7:52 ` [PATCH V4 01/11] qemuboot.bbclass: add it for runqemu Robert Yang
2016-08-22  7:52 ` [PATCH V4 02/11] qemuarm.conf: set vars " Robert Yang
2016-08-22  7:52 ` [PATCH V4 03/11] qemuarm64.conf: " Robert Yang
2016-08-22  7:52 ` [PATCH V4 04/11] qemux86.conf/qemux86-64.conf: " Robert Yang
2016-08-22  7:52 ` [PATCH V4 05/11] qemumips/qemumips64.conf: " Robert Yang
2016-08-22  7:52 ` [PATCH V4 06/11] qemuppc.conf: " Robert Yang
2016-08-22  7:52 ` [PATCH V4 07/11] qemu.inc: inherit qemuboot.bbclass Robert Yang
2016-08-22  7:52 ` [PATCH V4 08/11] runqemu: refactor it and remove machine knowledge Robert Yang
2016-08-22  7:52 ` [PATCH V4 09/11] python-3.5-manifest.inc: the signal module RDEPENDS on enum Robert Yang
2016-08-22  7:52 ` [PATCH V4 10/11] nativesdk-qemu-helper: fix for new runqemu Robert Yang
2016-08-22  7:52 ` [PATCH V4 11/11] qemurunner.py/qemutinyrunner.py: remove runqemu-internal Robert Yang
2016-08-22 19:44 ` [PATCH V4 00/11] runqemu: refactor it and remove machine knowledge Aníbal Limón
2016-08-23  0:27   ` Robert Yang
2016-08-23  9:05 ` Richard Purdie
2016-08-23  9:21   ` Robert Yang
2016-08-25 14:36     ` Robert Yang
2016-08-25 21:52       ` Richard Purdie [this message]
2016-08-26  6:28         ` Robert Yang

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=1472161955.29583.1.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=liezhi.yang@windriver.com \
    --cc=openembedded-core@lists.openembedded.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.