From: Tom Rini <trini@konsulko.com>
To: Joshua Watt <JPEWhacker@gmail.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: sstate hash equivalence breaks rm_work
Date: Sun, 3 Mar 2019 15:47:31 -0500 [thread overview]
Message-ID: <20190303204731.GK5026@bill-the-cat> (raw)
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
Hey all,
As part of the packagegroup-core-base-utils series I noticed that
with rm_work enabled like I usually have, every build was starting over
with rebuilding linux-libc-headers and going down from there. I
finished bisecting this now and it comes down to:
commit d889acb4f8f06f09cece80fa12661725e6e5f037
Author: Joshua Watt <jpewhacker@gmail.com>
Date: Fri Jan 4 10:20:15 2019 -0600
sstate: Implement hash equivalence sstate
This can be reproduced easily with qemux86, core-image-minimal, oe-core
and this in site.conf:
# Save more space
INHERIT += "rm_work"
# But keep this around for debugging
RM_WORK_EXCLUDE += ""
INHERIT += "buildstats"
INHERIT += "buildstats-summary"
(I doubt the last two matter, but I only noticed that was in my bisect
just now).
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2019-03-03 20:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-03 20:47 Tom Rini [this message]
2019-03-03 21:21 ` sstate hash equivalence breaks rm_work Joshua Watt
2019-03-03 21:25 ` Tom Rini
2019-03-03 22:11 ` Joshua Watt
2019-03-03 22:20 ` Joshua Watt
2019-03-03 22:51 ` Tom Rini
2019-03-04 10:17 ` Burton, Ross
2019-03-04 10:26 ` Martin Jansa
2019-03-04 10:45 ` Burton, Ross
2019-03-04 10:56 ` Martin Jansa
2019-03-04 12:21 ` Tom Rini
2019-03-04 15:58 ` Tom Rini
2019-03-04 16:06 ` Richard Purdie
2019-03-04 16:14 ` Tom Rini
2019-03-04 16:21 ` Richard Purdie
2019-03-04 16:38 ` Tom Rini
2019-03-04 16:17 ` Joshua Watt
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=20190303204731.GK5026@bill-the-cat \
--to=trini@konsulko.com \
--cc=JPEWhacker@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox