diff options
| author | Olof Johansson <olof.johansson@axis.com> | 2018-06-25 13:34:46 +0200 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2018-06-28 09:22:30 +0100 |
| commit | 21d015f6c9927598d64c48c925638619b25cf232 (patch) | |
| tree | b75700084f7596867324733b9168fcae9ceb9af6 /meta/COPYING.MIT | |
| parent | da29440633706fb7a346391d97894d6f2cbb0d01 (diff) | |
| download | openembedded-core-21d015f6c9927598d64c48c925638619b25cf232.tar.gz openembedded-core-21d015f6c9927598d64c48c925638619b25cf232.tar.bz2 openembedded-core-21d015f6c9927598d64c48c925638619b25cf232.zip | |
insane.bbclass: Don't let warnings make previous errors non-fatal
package_qa_handle_error() returns True on non-fatal issues and False on
fatal issues. But the current usage has been to do
sane = package_qa_handle_error(...)
which would always reset sanity status to be that of the last issue
identified. This change the assignments to use the &= operator instead:
sane &= package_qa_handle_error(...)
As far as I can tell, this is not a real problem in practice, because
warnings of different levels (WARN_QA, ERROR_QA) does not seem to have
been mixed in a way that triggered this issue.
Signed-off-by: Olof Johansson <olofjn@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/COPYING.MIT')
0 files changed, 0 insertions, 0 deletions