Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: testing branch 2011-02-03
Date: Sat, 05 Feb 2011 08:28:49 -0700	[thread overview]
Message-ID: <4D4D6CB1.9050008@mentor.com> (raw)
In-Reply-To: <AANLkTi=QkexH5odXt9-6a9SFe=hhyv=tsiBXOhHt-u9p@mail.gmail.com>

On 02/04/2011 06:08 AM, Cliff Brake wrote:
> master has been merged to testing-next and is ready for clean builds.
>
> I realize I've been tardy in getting the testing-next going, so I'm
> going to create a cron job now that does that weekly.
>
> Last week's testing results:
>
> http://cgit.openembedded.org/cgit.cgi/openembedded/tag/?id=tested_2011-01-28
>
> For more information on OE testing, see:
>
> http://www.openembedded.org/index.php/Testing

Without be21179c5321bd0afb9221f020ac12ad75c86a3b all of mine (would 
have) failed so I wont be reporting results on the table this week but I 
am kicking things off on current top of tree.  I expect:
- angstrom-2008.1 + qt4* to fail (reported earlier this week)
- qt4* + arm + minimal-uclibc to fail (one of those __cxa_atexit things, 
will report better)
- qt4* + mips64 + minimal-uclibc to fail (don't have the log handy, will 
report).

-- 
Tom Rini
Mentor Graphics Corporation



      parent reply	other threads:[~2011-02-05 15:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-04 13:08 testing branch 2011-02-03 Cliff Brake
2011-02-04 13:37 ` Anders Törnqvist
2011-02-04 13:50   ` Frans Meulenbroeks
2011-02-04 14:11     ` Anders Törnqvist
2011-02-04 14:19       ` Cliff Brake
2011-02-04 15:01 ` Cliff Brake
2011-02-04 15:21 ` Steffen Sledz
2011-02-04 15:30   ` Anders Törnqvist
2011-02-04 18:07   ` Khem Raj
2011-02-07  8:13     ` Steffen Sledz
2011-02-09  7:50   ` Steffen Sledz
2011-02-09 15:02     ` Tom Rini
2011-02-10  7:41       ` Steffen Sledz
2011-02-04 15:30 ` Jonathan Cameron
2011-02-05 15:28 ` Tom Rini [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=4D4D6CB1.9050008@mentor.com \
    --to=tom_rini@mentor.com \
    --cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox