Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Stefan Schmidt <stefan@datenfreihafen.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: testing 2010-10-04
Date: Tue, 5 Oct 2010 15:57:32 +0200	[thread overview]
Message-ID: <20101005135732.GE3517@excalibur.local> (raw)
In-Reply-To: <i8f965$scu$1@dough.gmane.org>

Hello.

On Tue, 2010-10-05 at 15:28, Koen Kooi wrote:
> On 05-10-10 14:32, Stefan Schmidt wrote:
> > Hello.
> > 
> > On Mon, 2010-10-04 at 14:05, Cliff Brake wrote:
> >> Testing run from last week:
> >> http://cgit.openembedded.org/cgit.cgi/openembedded/tag/?id=testing_2010-09-27
> >>
> >> testing-next is updated and ready for clean builds:
> >> http://wiki.openembedded.net/index.php/Testing
> > 
> > Openjdk-6 build fails on cacao:
> > http://tinderbox.openembedded.net/public/logs/task/8408323.txt
> 
> Openjdk fails in a lot of ways. Building it is a lottery. When changing
> nothing (host system and OE) I can do 2 builds from scratch and have one
> building openjdk and the other will fail. Or hang in icedtea compilation
> taking 0% cpu.

It was the first fail for all testing-next builds that have been done until now.

I agree that building it is not as stable as I would like it, but it is also not
as bad as described. The only problem i have been run into for a long time is a
segfault of the host javavm when bringing up other packages. Restarting the
build always gaves me a working image.

> So openjdk is not a good measure of passing judgement over a branch.

It failed in 1 out of 7 testing cycles for now. Not that bad imho. Surely it
gives no idea of the overall usability of a certain branch, but thats why we
have more images and distros to cover up more areas.

regards
Stefan Schmidt



  reply	other threads:[~2010-10-05 13:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-04 18:05 testing 2010-10-04 Cliff Brake
2010-10-05 10:27 ` Frans Meulenbroeks
2010-10-05 11:39   ` Frans Meulenbroeks
2010-10-05 14:21     ` Cliff Brake
2010-10-05 12:32 ` Stefan Schmidt
2010-10-05 13:23   ` Frans Meulenbroeks
2010-10-05 14:00     ` Stefan Schmidt
2010-10-05 14:24     ` Cliff Brake
2010-10-05 13:28   ` Koen Kooi
2010-10-05 13:57     ` Stefan Schmidt [this message]
2010-10-05 14:50   ` dfoley
2010-10-06 10:37     ` Stefan Schmidt
2010-10-07 15:34       ` dfoley
2010-10-07 18:26         ` Khem Raj
2010-10-07 19:04           ` Dallas Foley
2010-10-08  5:44             ` Stefan Schmidt

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=20101005135732.GE3517@excalibur.local \
    --to=stefan@datenfreihafen.org \
    --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