From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: Christopher Larson <kergoth@gmail.com>
Cc: yocto <yocto@yoctoproject.org>
Subject: Re: [[RFC][PATCH]] yocto-compat-layer.py: Add script to YP Compatible Layer validation
Date: Mon, 13 Feb 2017 10:27:00 -0600 [thread overview]
Message-ID: <58A1DE54.9000609@linux.intel.com> (raw)
In-Reply-To: <CABcZANkJC0FVsrRh+Kdd8_h9yRWR=3gpWWO4O0t-gbKbEMOukw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2352 bytes --]
On 02/11/2017 08:04 PM, Christopher Larson wrote:
> On Sat, Feb 11, 2017 at 10:55 AM, Aníbal Limón <anibal.limon@linux.intel.com
>> wrote:
>
>> During the development of this script based on OEQA framework i found a
>> bug causing don't display stack traces, i sent a fix to the ML [1] also
>> is on my branch at [2].
>>
>> I attached and example of how a log file looks, the example log results
>> are based on meta-yocto-bsp.
>>
>> Cheers,
>> alimon
>>
>> [1]
>> http://lists.openembedded.org/pipermail/openembedded-core/
>> 2017-February/132494.html
>> [2]
>> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/
>> log/?h=alimon/yp_compatible
>>
>
> This seems like a good start, but this isn’t useful:
>
> AssertionError: True is not false : Layer meta-yocto-bsp changed
> signatures.
>
> Presumably this is telling the user it’s modifying things without using the
> appropriate overrides for machine or distro, but it doesn’t actually tell
> them that, and displaying the changed checksums isn’t of a great deal of
> use on its own either, I’d suggest at least capturing the changed variables
> via bitbake-diffsigs or bitbake -S printdiff.
Ok i can add another tests using bitbake -S printdiff.
I have a question, did you see the changed signatures like the attached
results log ones?
Example,
AssertionError: True is not false : Layer meta-yocto-bsp changed signatures.
packagegroup-core-lsb:do_build changed 3a1b91e693c766befca17e00ca69cfe9
-> 1153f4c44d409486e10a19449981aef7
packagegroup-core-lsb:do_package_write_rpm changed
7fafda279503fb441f957fe88981cbc9 -> 45845055584bad62e1b6d67b12e668bd
packagegroup-core-lsb:do_package changed
c312cfe0956cecd9af010de2de09dc89 -> 3d00ea36ae703c99c2e8be57ad309a04
meta-world-pkgdata:do_build changed d62a25aedc0adc4ed0832ea20141c4b7 ->
e8ee6e0e34122c095bc62a26e90be51f
packagegroup-core-lsb:do_packagedata changed
9a63506a1764a11a5177c206839ce8ba -> 919b5c641cc779e59bd8df94b50a3d07
packagegroup-core-lsb:do_package_qa changed
53a4bafbdea1fc41098ae48aef584b12 -> babec54733e94d0df008e237927552e7
If not please apply this patch [1]
Best regards,
alimon
[1]
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=alimon/yp_compatible&id=f35f9b2bc068ee4e50acdc163464da4aaadda956
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2017-02-13 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-11 17:51 [[RFC][PATCH]] yocto-compat-layer.py: Add script to YP Compatible Layer validation Aníbal Limón
2017-02-11 17:55 ` Aníbal Limón
2017-02-12 2:04 ` Christopher Larson
2017-02-13 16:27 ` Aníbal Limón [this message]
2017-02-17 21:27 ` Aníbal Limón
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=58A1DE54.9000609@linux.intel.com \
--to=anibal.limon@linux.intel.com \
--cc=kergoth@gmail.com \
--cc=yocto@yoctoproject.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.