diff options
| author | Paul Eggleton <paul.eggleton@linux.intel.com> | 2016-12-13 11:05:06 +1300 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-12-14 09:56:32 +0000 |
| commit | fb37304d27857df3c53c0867e81fbc8899b48089 (patch) | |
| tree | 20674d3dfbd97eb48a421e11c0c37400d5b2b7b9 /scripts/lib/devtool/package.py | |
| parent | 541c56d755ba0354297673e857628026ad9e4df2 (diff) | |
| download | openembedded-core-fb37304d27857df3c53c0867e81fbc8899b48089.tar.gz openembedded-core-fb37304d27857df3c53c0867e81fbc8899b48089.tar.bz2 openembedded-core-fb37304d27857df3c53c0867e81fbc8899b48089.zip | |
classes/image: suppress log_check mechanism for warnings/errors logged through BitBake
If you printed a warning through bb.warn() / bbwarn or an error through
bb.error() / bberror, this was also being picked up by our log_check
mechanism that was designed to pick up warnings and errors printed by
other programs used during do_rootfs. This meant you saw not only the
warning or error itself, you saw it a second time through log_check,
which is a bit ugly. Use the just-added BB_TASK_LOGGER to access the
logger and add a handler that we can use to find out if any warning or
error we find in the logs is one we should ignore as it has already been
printed.
Fixes [YOCTO #8223].
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'scripts/lib/devtool/package.py')
0 files changed, 0 insertions, 0 deletions