From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] parse: get_file_depends(): return deterministic result
Date: Wed, 23 May 2012 11:27:59 +0100 [thread overview]
Message-ID: <1337768879.8248.57.camel@ted> (raw)
In-Reply-To: <1337527217-5550-1-git-send-email-enrico.scholz@sigma-chemnitz.de>
On Sun, 2012-05-20 at 17:20 +0200, Enrico Scholz wrote:
> The output of get_file_depends() concatenates elements of a set. Result
> of this operation is not deterministic because it is calculated by
> parallel running parsing threads.
>
> Because result of get_file_depends() is stored into BBINCLUDED which
> goes in into various hash calculations, this can cause unwanted rebuilds
> of cache or recipes.
>
> Signed-off-by: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
> ---
> lib/bb/parse/__init__.py | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/lib/bb/parse/__init__.py b/lib/bb/parse/__init__.py
> index 7b9c47e..1e69778 100644
> --- a/lib/bb/parse/__init__.py
> +++ b/lib/bb/parse/__init__.py
> @@ -138,6 +138,6 @@ def get_file_depends(d):
> depends = depends.union(d.getVar('__base_depends', True) or set())
> for (fn, _) in depends:
> dep_files.append(os.path.abspath(fn))
> - return " ".join(dep_files)
> + return " ".join(sorted(dep_files))
>
> from bb.parse.parse_py import __version__, ConfHandler, BBHandler
I've commented before on this list about the problems in this variable.
We need to fix this problem so the list is both correctly ordered and
that the order is maintained.
I'm therefore reluctant to take this patch and would like one that fixes
all the issues properly once and for all.
Cheers,
Richard
prev parent reply other threads:[~2012-05-23 10:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-20 15:20 [PATCH] parse: get_file_depends(): return deterministic result Enrico Scholz
2012-05-23 10: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=1337768879.8248.57.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=enrico.scholz@sigma-chemnitz.de \
/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.