From: Martin Jansa <martin.jansa@gmail.com>
To: Chen Qi <Qi.Chen@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/5] rootfs.py: two changes regarding log checking
Date: Wed, 18 Mar 2015 13:03:18 +0100 [thread overview]
Message-ID: <20150318120318.GC4738@jama> (raw)
In-Reply-To: <003afa4a3acb0670e6e3b9d3e12e9b276f03876c.1426670089.git.Qi.Chen@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 2129 bytes --]
On Wed, Mar 18, 2015 at 05:16:10PM +0800, Chen Qi wrote:
> This patch involves two changes.
>
> 1. Extend the regular expression to also catch '^WRARNING:' in _log_check_warn.
typo WRARNING
> Warnings from bb.note or bbnote begin with 'WARNING:'. So if we decide to
> catch warnings at rootfs time, we should not ignore those produced by
> the build system itself.
>
> 2. Delay _log_check in rootfs process so that more warnings are likely to be
> catched. Note that we should at least delay the _log_check after the
> execution of ROOTFS_POSTPROCESS_COMMANDS, because we want to catch warnings
> there.
>
> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> ---
> meta/lib/oe/rootfs.py | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/meta/lib/oe/rootfs.py b/meta/lib/oe/rootfs.py
> index 7e8d5d1..3a77e86 100644
> --- a/meta/lib/oe/rootfs.py
> +++ b/meta/lib/oe/rootfs.py
> @@ -128,6 +128,7 @@ class Rootfs(object):
> self._generate_kernel_module_deps()
>
> self._cleanup()
> + self._log_check()
>
> def _uninstall_unneeded(self):
> # Remove unneeded init script symlinks
> @@ -327,8 +328,6 @@ class RpmRootfs(Rootfs):
>
> self.pm.install_complementary()
>
> - self._log_check()
> -
> if self.inc_rpm_image_gen == "1":
> self.pm.backup_packaging_data()
>
> @@ -355,7 +354,7 @@ class RpmRootfs(Rootfs):
> pass
>
> def _log_check_warn(self):
> - r = re.compile('^(warn|Warn|NOTE: warn|NOTE: Warn)')
> + r = re.compile('^(warn|Warn|NOTE: warn|NOTE: Warn|WARNING:)')
> log_path = self.d.expand("${T}/log.do_rootfs")
> with open(log_path, 'r') as log:
> for line in log.read().split('\n'):
> --
> 1.9.1
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2015-03-18 12:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 9:16 [PATCH 0/5] Changes regarding log checking and license checksums Chen Qi
2015-03-18 9:16 ` [PATCH 1/5] rootfs.py: two changes regarding log checking Chen Qi
2015-03-18 9:48 ` Paul Eggleton
2015-03-18 15:46 ` Aníbal Limón
2015-03-19 2:16 ` ChenQi
2015-03-18 12:03 ` Martin Jansa [this message]
2015-03-18 9:16 ` [PATCH 2/5] rootfs.py: add log checking ability for deb and ipk Chen Qi
2015-03-18 9:16 ` [PATCH 3/5] packagegroup: add LIC_FILES_CHKSUM Chen Qi
2015-03-18 9:37 ` Paul Eggleton
2015-03-18 9:16 ` [PATCH 4/5] os-release: " Chen Qi
2015-03-18 9:16 ` [PATCH 5/5] glibc-collateral.inc: " Chen Qi
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=20150318120318.GC4738@jama \
--to=martin.jansa@gmail.com \
--cc=Qi.Chen@windriver.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.