Re: Dependent task hashes in depsig.*
On Wed, 2022-04-27 at 12:39 +0200, Jacob Kroon wrote:
On 4/27/22 12:12, Richard Purdie wrote:That definitely wasn't clear! I now understand better what you mean and yes,On Wed, 2022-04-27 at 11:06 +0200, Jacob Kroon wrote:I don't think I was being clear enough. With "scrambling a header in aHi Richard and Joshua,That is probably unfortunately inevitable. If the output has changed (i.e. the
we're supposed to be optimising that scenario.
No, they are hash equiv resolved hashes which would have a one to one mappingSo it is the outhashes that are listed above?This is because the depsig.do_populate_sysroot in "libgcc"The dependent resolved hashes are used, as resolved by hashequiv which is a key
with an outhash.
Then I don't understandTo be honest, I don't remember/understand offhand either. I'd need to go and
spend time trying to page in all the information.
We have too few people with the knowledge in these areas and I'm rapidly burning
out. I don't like this reply but I just don't have the time to dive into it and
debug it right now and I can't really give much more of a helpful comment/reply
without doing so.
I agree there is some issue here which does need investigation. At least do file
a bug so it doesn't get forgotten but we don't have many people taking on bugs
either. This one would get triaged to me or Joshua.
I'd also add that gcc is pretty horrific in that it bundles up a lot of it's
build tree into the sysroot. It is possible those bundled files are varying
somehow reproducibility wise causing some instability. I've worried about this
kind of issue for a while but I don't scale and there are a load of other issues
going on too :(.