All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Trevor Woerner <twoerner@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: 1.4_M6.rc1 started
Date: Wed, 10 Apr 2013 22:41:43 -0400	[thread overview]
Message-ID: <516622E7.90509@windriver.com> (raw)
In-Reply-To: <CAHUNapTQhQNb+DRf7Z6HvtcQmQ+Jo2jtJiqKt8u6frUEvM-UaQ@mail.gmail.com>

On 13-04-10 10:34 PM, Trevor Woerner wrote:
> On Wed, Apr 10, 2013 at 6:48 PM, Flanagan, Elizabeth
> <elizabeth.flanagan@intel.com>  wrote:
>> Our first release candidate for dylan has been started.
>>
>> Repo               Branch      Hash
>> poky                dylan         adb63ca02348af72a30cef2f20de2234b74a7200
>
> I did a little bit of my own ad-hoc testing and wanted to share my
> results. Maybe others could give it a try and see if they come up with
> the same?
>
> Checking out the dylan branch of poky I just wanted to perform a
> simple "bitbake console-image-minimal" for each of the supported qemu
> targets, run the resulting image under qemu, log in as root, and run
> "uname -a".
>
> Here are my results:
>
> qemux86
>          bitbake core-image-minimal
>                  - okay
>          runqemu qemux86
>                  - okay
>
> qemuarm
>          bitbake core-image-minimal
>                  - okay
>          runqemu qemuarm
>                  - segfault
>
> qemumips
>          bitbake core-image-minimal
>                  - okay
>          runqemu qemumips
>                  - couldn't log in on main terminal
>                  - but could log in using Ctrl+Alt+3 terminal

Fixed. A few hours ago.

>
> qemuppc
>          bitbake core-image-minimal
>                  - okay
>          runqemu qemuppc
>                  - okay
>
> qemux86-64
>          bitbake core-image-minimal
>                  - okay
>          runqemu qemux86-64
>                  - okay
>
> I have attached a png of my qemuarm output. Right now I'm deleting its
> tmp directory and trying again.

Known problem. And I've got a fix already tested and on it's way to
Richard.

Cheers,

Bruce

>
> Next I want to try a "bitbake world" of all the targets to see whether
> they can all succeed (they did a couple commits ago).
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



  reply	other threads:[~2013-04-11  2:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10 22:48 1.4_M6.rc1 started Flanagan, Elizabeth
2013-04-11  2:34 ` Trevor Woerner
2013-04-11  2:41   ` Bruce Ashfield [this message]
2013-04-11  3:21     ` Trevor Woerner
2013-04-11  3:23       ` Bruce Ashfield
2013-04-11  8:38 ` Richard Purdie
2013-04-11 13:35   ` Georgescu, Alexandru C

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=516622E7.90509@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=twoerner@gmail.com \
    --cc=yocto@yoctoproject.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.