From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: bitbake-devel@lists.openembedded.org,
Paul Barker <pbarker@toganlabs.com>
Subject: Re: [PATCH] runqueue: Ensure only recursive task dependencies are pruned
Date: Wed, 28 Feb 2018 11:27:19 +0000 [thread overview]
Message-ID: <1519817239.3436.3.camel@linuxfoundation.org> (raw)
In-Reply-To: <1519814643.24236.418.camel@linuxfoundation.org>
On Wed, 2018-02-28 at 10:44 +0000, Richard Purdie wrote:
> We have a problem with this patch since it causes:
>
> $ oe-selftest -r
> sstatetests.SStateTests.test_sstate_sametune_samesigs
[...]
> =====================================================================
> =
> 2018-02-28 10:36:13,406 - oe-selftest - INFO - FAIL:
> test_sstate_sametune_samesigs (sstatetests.SStateTests)
> 2018-02-28 10:36:13,406 - oe-selftest - INFO - ----------------------
Further investigation suggests this is a metadata bug and bitbake is
right here. Working on a fix for the metadata.
Cheers,
Richard
prev parent reply other threads:[~2018-02-28 11:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 21:48 [PATCH] runqueue: Ensure only recursive task dependencies are pruned Richard Purdie
2018-02-28 10:44 ` Richard Purdie
2018-02-28 11:27 ` Richard Purdie [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=1519817239.3436.3.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=pbarker@toganlabs.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