From: Tom Zanussi <tom.zanussi@intel.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Current Build Failures for d82f205cfa790b40e132e11b7937050bc3b97ff3
Date: Thu, 13 Jan 2011 10:47:23 -0600 [thread overview]
Message-ID: <1294937243.9232.2.camel@elmorro> (raw)
In-Reply-To: <4D2F2A4A.8030305@windriver.com>
On Thu, 2011-01-13 at 08:37 -0800, Bruce Ashfield wrote:
> On 11-01-13 11:33 AM, Elizabeth Flanagan wrote:
> > All,
> >
> > The current nightly based on d82f205cfa790b40e132e11b7937050bc3b97ff3 is
> > showing 3 build failures so far.
> >
> > Machine: qemux86
> > Failure: intermittent tasks_0.18 failure at do_compile
> > Description: Tasks_0.18 has failed during one buildset, however it's not
> > failing on the other.
> >
> >
> > Machine: arm
> > Failure: sanity tests time out and cause cascading failures.
> > Description: I'm patching the autobuilder today so that sanity tests
> > timing out shouldn't cause a cascading failure, however the arm sanity
> > tests are still timing out.
> >
> > Machine: qemux86-64
> > Failure: linux-yocto_git failing at do_compile_perf
> > Description:
> > | CC util/scripting-engines/trace-event-perl.o
> > | cc1: warnings being treated as errors
> > | cc1: error: include location "/usr/local/include" is unsafe for
> > cross-compilation
>
> I saw this one as well, but hadn't gone back to look at
> it yet. Did something change underneath us?
>
> I haven't updated any parts of the recipes or kernel that
> would have triggered the new failure. Or at least nothing
> that has ever showed up in my testing.
>
Yeah, it's strange that this starts happening seemingly out of the blue
- nothing wrt this has changed recently AFAICS.
> Darren/Tom: you guys have been into perf/trace recently,
> any ideas (or time) for a quick fix ? I'm going to be
> pegged for the day trying to sort out some other items.
>
Coincidentally, I was going to look at perf scripting next week - guess
I'll start this week instead. Don't have a quick fix off the top of my
head - will start looking into it later today/tonight...
Tom
> Cheers,
>
> Bruce
>
> > | make: *** [util/scripting-engines/trace-event-perl.o] Error 1
> >
> > _______________________________________________
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
>
next prev parent reply other threads:[~2011-01-13 16:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 16:33 Current Build Failures for d82f205cfa790b40e132e11b7937050bc3b97ff3 Elizabeth Flanagan
2011-01-13 16:37 ` Bruce Ashfield
2011-01-13 16:47 ` Tom Zanussi [this message]
2011-01-14 1:37 ` João Henrique Freitas
2011-01-14 1:41 ` Bruce Ashfield
2011-01-14 6:34 ` Tom Zanussi
2011-01-14 15:48 ` Bruce Ashfield
2011-01-14 1:59 ` Xu, Jiajun
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=1294937243.9232.2.camel@elmorro \
--to=tom.zanussi@intel.com \
--cc=bruce.ashfield@windriver.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.