From: Patrick Ohly <patrick.ohly@intel.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 03/11] bitbake-diffsigs: properly report which signature is missing
Date: Fri, 07 Apr 2017 18:25:44 +0200 [thread overview]
Message-ID: <1491582344.10884.79.camel@intel.com> (raw)
In-Reply-To: <01748f01da49c1a0d7ccdb114c6822b4969ff40d.1491514854.git.paul.eggleton@linux.intel.com>
On Fri, 2017-04-07 at 09:52 +1200, Paul Eggleton wrote:
> If just one of the two signatures we want to compare aren't available,
> report that one rather than misleadingly claiming both are missing.
I just noticed that bitbake-diffsigs -t ... do_build recursively dumps
differences in other tasks - cool, I don't know it could do that. It
worked fine for all-arch ca-certificates, but not for
$ bitbake-diffsigs -d -t gdb-cross-x86_64 do_build -s 68a82197720db0f0dbad8955635bc1c0 5631f484d848541bdbf6a4c1f8117f79
DEBUG: Signature file (previous): /fast/build/nodistro/x86/tmp-glibc/stamps/x86_64-linux/gdb-cross-x86_64/7.12.1-r0.do_build.sigdata.68a82197720db0f0dbad8955635bc1c0
DEBUG: Signature file (latest): /fast/build/nodistro/x86/tmp-glibc/stamps/x86_64-linux/gdb-cross-x86_64/7.12.1-r0.do_build.sigdata.5631f484d848541bdbf6a4c1f8117f79
Hash for dependent task gdb/gdb-cross_7.12.1.bb.do_populate_sysroot changed from 6247000d87570135b704fcfd3e4e7cd4 to 554c1ce69bf0538a91436e5f7c256488
Unable to find matching sigdata for /fast/work/openembedded-core/meta/recipes-devtools/gdb/gdb-cross_7.12.1.bb.do_populate_sysroot with hashes 6247000d87570135b704fcfd3e4e7cd4 or 554c1ce69bf0538a91436e5f7c256488
$ bitbake-diffsigs -d -t gdb-cross-x86_64 do_populate_sysroot -s 6247000d87570135b704fcfd3e4e7cd4 554c1ce69bf0538a91436e5f7c256488
DEBUG: Signature file (previous): /fast/build/nodistro/x86/tmp-glibc/stamps/x86_64-linux/gdb-cross-x86_64/7.12.1-r0.do_populate_sysroot.sigdata.6247000d87570135b704fcfd3e4e7cd4
DEBUG: Signature file (latest): /fast/build/nodistro/x86/tmp-glibc/stamps/x86_64-linux/gdb-cross-x86_64/7.12.1-r0.do_populate_sysroot.sigdata.554c1ce69bf0538a91436e5f7c256488
Hash for dependent task gdb/gdb-cross_7.12.1.bb.do_install changed from 0786db89020b877d443da848548b3d1d to 746c2815e180fa2a4ff28608c7c1b9d5
Unable to find matching sigdata for /fast/work/openembedded-core/meta/recipes-devtools/gdb/gdb-cross_7.12.1.bb.do_install with hashes 0786db89020b877d443da848548b3d1d or 746c2815e180fa2a4ff28608c7c1b9d5
In other words, automatic diff fails to find files, while manual diff finds them?!
This situation can be triggered with a local patch of mine (to be posted soon) and using
yocto-compat-layer.py -n --machines intel-corei7-64 intel-core2-32 qemux86 qemux86-64 -- /fast/work/meta-intel
The test uses MACHINE=... bitbake -S none world to generate the signatures for
different machines and then looks for tasks that are shared between
machines with different signatures.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2017-04-07 16:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 21:52 [PATCH 00/11] bitbake-diffsigs fixes/improvements Paul Eggleton
2017-04-06 21:52 ` [PATCH 01/11] bitbake-diffsigs: fix -t picking wrong files to compare Paul Eggleton
2017-04-06 21:52 ` [PATCH 02/11] lib/bb/siggen: add missing path separator to cleaned paths Paul Eggleton
2017-04-06 21:52 ` [PATCH 03/11] bitbake-diffsigs: properly report which signature is missing Paul Eggleton
2017-04-07 16:25 ` Patrick Ohly [this message]
2017-04-06 21:52 ` [PATCH 04/11] bitbake-diffsigs: drop naive logic for removing duplicate files Paul Eggleton
2017-04-06 21:52 ` [PATCH 05/11] lib/bb/siggen: show a diff when dumping changes to multi-line values Paul Eggleton
2017-04-06 21:52 ` [PATCH 06/11] lib/bb/siggen: don't show unchanged runtaskdeps list Paul Eggleton
2017-04-06 21:52 ` [PATCH 07/11] bitbake-diffsigs: change to use argparse Paul Eggleton
2017-04-06 21:52 ` [PATCH 08/11] bitbake-diffsigs: add an option to find and compare specific signatures Paul Eggleton
2017-04-06 21:52 ` [PATCH 09/11] lib/bb/siggen: add collapsed mode to compare_sigfiles() Paul Eggleton
2017-04-07 6:37 ` Patrick Ohly
2017-04-07 8:26 ` Paul Eggleton
2017-04-06 21:52 ` [PATCH 10/11] lib/bb/siggen: show word-diff for single-line values containing spaces Paul Eggleton
2017-04-06 21:52 ` [PATCH 11/11] bitbake-diffsigs: colourise output Paul Eggleton
2017-04-07 7:56 ` [PATCH 00/11] bitbake-diffsigs fixes/improvements Patrick Ohly
2017-04-07 8:29 ` Paul Eggleton
2017-04-07 8:32 ` Paul Eggleton
2017-04-07 8:54 ` Patrick Ohly
2017-04-07 9:48 ` Paul Eggleton
2017-04-07 12:20 ` Peter Kjellerstedt
2017-04-07 16:46 ` Richard Purdie
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=1491582344.10884.79.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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.