From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: Buildhistory in action
Date: Thu, 19 Jan 2012 15:04:34 +0000 [thread overview]
Message-ID: <3069877.zIVnnZc8iy@helios> (raw)
In-Reply-To: <1326978483.2511.68.camel@ted>
On Thursday 19 January 2012 13:08:03 Richard Purdie wrote:
> If I change into tmp/buildhistory and show the last commit the result is
> included below. Since the version changed, the diff isn't as readable as
> would be ideal, however reading through it clearly shows the .a files
> moving to the staticdev packages with no unintended changes as far as I
> could tell.
>
> One of my big worries with the staticdev changes is any unintended
> packaging changes. This lets me view the changes more precisely which
> can only lead to higher quality regression spotting for the project. I'd
> like to suggest more people start enabling this and using it to check
> the changes they're making.
>
> I know Paul is working on tools to better display these changes too and
> those will help make these diffs easier to read.
There's the command line buildhistory-diff tool (in scripts/) already, and this
will query the git repository and report just the changes that might represent
regressions, in a form that's a bit easier to read than git diff. For example
(simulated):
paul@helios:~/poky/poky/build/tmp/buildhistory$ ~/poky/poky/scripts/buildhistory-diff . HEAD^^
Changes to images/qemux86_64/eglibc/core-image-minimal (files-in-image.txt):
/etc/anotherpkg.conf was added
/sbin/anotherpkg was added
* (installed-package-names.txt):
* anotherpkg was added
Changes to images/qemux86_64/eglibc/core-image-minimal (installed-package-names.txt):
anotherpkg was added
packages/qemux86_64-poky-linux/v86d: PACKAGES: added "v86d-extras"
* PR changed from "r0" to "r1"
* PV changed from "0.1.10" to "0.1.12"
packages/qemux86_64-poky-linux/v86d/v86d: PKGSIZE changed from 110579 to 144381 (+30%)
* PR changed from "r0" to "r1"
* PV changed from "0.1.10" to "0.1.12"
For those that may not be aware I'm also working on a web frontend to
view/manage these changes more effectively (utilising the same backend code),
however it still needs quite a bit of work.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-01-19 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 13:08 Buildhistory in action Richard Purdie
2012-01-19 14:37 ` Koen Kooi
2012-01-19 14:45 ` Paul Eggleton
2012-01-19 14:59 ` Koen Kooi
2012-01-19 15:04 ` Paul Eggleton [this message]
2012-01-19 16:06 ` Mark Hatle
2012-01-19 16:22 ` 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=3069877.zIVnnZc8iy@helios \
--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 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.