From: Joshua G Lock <joshua.g.lock@linux.intel.com>
To: Holger Freyther <holger@freyther.de>, poky@yoctoproject.org
Subject: Re: taskhash mismatch and what's next?
Date: Mon, 11 Apr 2016 09:30:20 +0100 [thread overview]
Message-ID: <1460363420.3398.4.camel@linux.intel.com> (raw)
In-Reply-To: <5D2DC2E7-EE57-4EC4-B9BD-72F0DB7F45C7@freyther.de>
On Mon, 2016-04-04 at 21:15 +0200, Holger Freyther wrote:
> Hi,
>
> todays internal built failed and I am greeted with:
>
> ERROR: meta-toolchain-osmo-1.0-r7 do_populate_sdk: Taskhash mismatch
> fb8cf0ab1d25eb3c1105f6d05e761f9d verses
> 51c3b8fae61b34daeacae493fe7458d8 for meta-telephony/recipes-
> osmocom/meta/meta-toolchain-osmo.bb.do_populate_sdk
> NOTE: recipe meta-toolchain-osmo-1.0-r7: task do_populate_sdk:
> Succeeded
> ERROR: Taskhash mismatch fb8cf0ab1d25eb3c1105f6d05e761f9d verses
> 51c3b8fae61b34daeacae493fe7458d8 for meta-telephony/recipes-
> osmocom/meta/meta-toolchain-osmo.bb.do_populate_sdk
I suspect this is the use of DATETIME in the recipe resulting in the
taskhash changing at the different times the checksum is created, i.e.
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=fab626cdf387c
5b4a4838074294cade1e6129a4f
Regards,
Joshua
>
> Now I understand that my meta-toolchain-osmo recipe[1] is to blame
> but what would be super nice is an extended error message. E.g. point
> to a piece of documentation that explains what is being hashed, which
> two hashes are being compared, when was the first computed, when the
> second one. Maybe even point to a recipe fix as an example?
>
>
> thanks a lot for your consideration
> holger
>
>
>
> [1] https://github.com/sysmocom/meta-telephony/blob/master/recipes-os
> mocom/meta/meta-toolchain-osmo.bb
prev parent reply other threads:[~2016-04-11 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 19:15 taskhash mismatch and what's next? Holger Freyther
2016-04-11 8:30 ` Joshua G Lock [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=1460363420.3398.4.camel@linux.intel.com \
--to=joshua.g.lock@linux.intel.com \
--cc=holger@freyther.de \
--cc=poky@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.