From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: McClintock Matthew-B29882 <B29882@freescale.com>,
Patches,
discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Recipes with disabled parallel make
Date: Wed, 10 Oct 2012 11:06:30 +0100 [thread overview]
Message-ID: <1349863590.15658.198.camel@ted> (raw)
In-Reply-To: <CAJTo0LZ2hwkk58_jQQx9a5mjEFSjyexuk0trRL5_8z_FGyZiRg@mail.gmail.com>
On Wed, 2012-10-10 at 10:16 +0100, Burton, Ross wrote:
> Hi Matthew,
>
> On 10 October 2012 02:45, McClintock Matthew-B29882
> <B29882@freescale.com> wrote:
> >>> 1. Recipes (files) confirmed to fail with P_M enabled (need to have
> >>> P_M disabled as it is now):
> >>> meta/recipes-connectivity/bind/bind_9.8.1.bb
> >>> meta/recipes-extended/slang/slang_2.2.4.bb
> >>> meta/recipes-extended/tcp-wrappers/tcp-wrappers_7.6.bb
> >>> meta/recipes-support/js/js_1.7.0+1.8.0rc1.bb
> >>> meta/recipes-support/pth/pth_2.0.7.bb
>
> Lack of parallelism is one of those things that really bugs me...
>
> Do you still have the failure logs to hand? I'd love to see a patch
> which put the failure alongside the PARALLEL_MAKE=0. It's also
> probably worth removing the PARALLEL_MAKE for the other targets once
> master opens for development and seeing if they break on the
> autobuilders (as some parallel races are rare to hit).
We've done this in the archives, the PARALLEL_MAKE entries we have are
pretty much all needed, sadly. I'm not breaking master on the
autobuilder by removing them "just for fun".
Cheers,
Richard
next prev parent reply other threads:[~2012-10-10 10:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 0:35 Recipes with disabled parallel make Khem Raj
2012-02-10 14:45 ` Tom Rini
2012-02-12 21:56 ` Yury Bushmelev
2012-02-13 6:10 ` Khem Raj
2012-03-02 22:29 ` Yury Bushmelev
2012-03-02 22:37 ` Khem Raj
2012-03-02 22:56 ` Yury Bushmelev
2012-03-02 22:39 ` Richard Purdie
2012-03-02 23:30 ` Khem Raj
2012-03-03 7:48 ` Yury Bushmelev
2012-03-03 19:55 ` Khem Raj
2012-03-03 22:15 ` Yury Bushmelev
2012-03-08 13:34 ` Andreas Oberritter
2012-10-10 1:45 ` McClintock Matthew-B29882
2012-10-10 9:16 ` Burton, Ross
2012-10-10 10:06 ` Richard Purdie [this message]
2012-10-10 14:04 ` McClintock Matthew-B29882
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=1349863590.15658.198.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=B29882@freescale.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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