From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/6] Add optional task signatures to buildhistory
Date: Fri, 7 Apr 2017 16:57:17 +1200 [thread overview]
Message-ID: <cover.1491540566.git.paul.eggleton@linux.intel.com> (raw)
If you're looking to compare task signatures between builds, that can
actually be a bit difficult to do if you don't have anything printed
out (e.g. from an error) with some signatures to look for. buildhistory
already makes a commit (or several commits) for each build, so we can
actually write the signatures into buildhistory so that we can compare
them later. If available (via the tasks actually having run, or by
explicitly creating them), we can even use the siginfo/sigdata files
to dig down and find out exactly what caused the signature changes.
Finally, add sha256sums for each file staged by every shared state task
so that we can see when a task re-executes if the file contents has
changed.
(All of this functionality defaults to off, you need to add "task" to
BUILDHISTORY_FEATURES in order to enable it).
There's also a small fix making it a bit easier to run the
buildhistory-diff script from the buildhistory repository.
NOTE: this patch series requires some of the patches in the set recently
sent to the bitbake-devel list.
The following changes since commit 901659a51cd53625a93f57a9c5865e90a07ec09d:
oeqa/runtime/utils/targetbuildproject: use parent classes defaults tmpdir (2017-04-06 10:13:34 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/buildhistory-sigs
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=paule/buildhistory-sigs
Paul Eggleton (6):
buildhistory-diff: operate from buildhistory directory
classes/buildhistory: write out task signatures on every build
buildhistory-diff: add option to compare task signature list
buildhistory-diff: add option to compare actual signature differences
classes/uninative: set SSTATEPOSTUNPACKFUNCS[vardepvalueexclude] properly
classes/buildhistory: save output file signatures for sstate tasks
meta/classes/buildhistory.bbclass | 40 +++++++++++++
meta/classes/uninative.bbclass | 2 +-
meta/lib/oe/buildhistory_analysis.py | 109 ++++++++++++++++++++++++++++++++++-
meta/lib/oe/sstatesig.py | 10 ++++
scripts/buildhistory-diff | 13 ++++-
5 files changed, 170 insertions(+), 4 deletions(-)
--
2.9.3
next reply other threads:[~2017-04-07 4:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 4:57 Paul Eggleton [this message]
2017-04-07 4:57 ` [PATCH 1/6] buildhistory-diff: operate from buildhistory directory Paul Eggleton
2017-04-07 4:57 ` [PATCH 2/6] classes/buildhistory: write out task signatures on every build Paul Eggleton
2017-04-07 4:57 ` [PATCH 3/6] buildhistory-diff: add option to compare task signature list Paul Eggleton
2017-04-07 4:57 ` [PATCH 4/6] buildhistory-diff: add option to compare actual signature differences Paul Eggleton
2017-04-07 4:57 ` [PATCH 5/6] classes/uninative: set SSTATEPOSTUNPACKFUNCS[vardepvalueexclude] properly Paul Eggleton
2017-04-07 4:57 ` [PATCH 6/6] classes/buildhistory: save output file signatures for sstate tasks Paul Eggleton
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=cover.1491540566.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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