All of lore.kernel.org
 help / color / mirror / Atom feed
From: "chris.laplante@agilent.com" <chris.laplante@agilent.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Cache unihash ... doesn't match BB_UNIHASH ...
Date: Fri, 7 Feb 2020 15:08:52 +0000	[thread overview]
Message-ID: <BN6PR1201MB2482E2CC1B03F12D77E33B538B1C0@BN6PR1201MB2482.namprd12.prod.outlook.com> (raw)
In-Reply-To: <6109c3315b8a215881c134441b74d0753820b5c8.camel@linuxfoundation.org>

> > Anecdotally, we are running Zeus for nightly builds with three
> > multiconfigs. I cherry-picked your "bitbake: fix2" and "bitbake:
> > fixup" patches and haven't seen any of the BB_UNIHASH errors since.
> > Granted it's only been a week. But before that, hash equiv +
> > multiconfig was unusable due to the BB_UNIHASH errors.
> 
> That is a really helpful data point, thanks. I should probably clean up
> those bitbake patches and get them merged then, I couldn't decide if
> they were right or not...

Sure thing! I should note, I did delete my hashserv.db (on the hash equiv server) out of caution after applying those patches. 

Chris 

  reply	other threads:[~2020-02-07 15:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-07  8:16 Cache unihash ... doesn't match BB_UNIHASH Alex Kiernan
2020-02-07  8:31 ` Richard Purdie
2020-02-07  9:12   ` Alex Kiernan
2020-02-07 14:43   ` chris.laplante
2020-02-07 15:05     ` Richard Purdie
2020-02-07 15:08       ` chris.laplante [this message]
2020-02-07 15:44       ` Alex Kiernan
2020-02-09  0:23         ` chris.laplante
2020-02-09  7:27           ` Alex Kiernan
2020-02-09 16:25             ` Alex Kiernan
2020-02-10 14:22               ` Alex Kiernan
2020-02-09 16:37           ` Joshua Watt
2020-02-12 16:51             ` chris.laplante

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=BN6PR1201MB2482E2CC1B03F12D77E33B538B1C0@BN6PR1201MB2482.namprd12.prod.outlook.com \
    --to=chris.laplante@agilent.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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.