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:35 +0100 |
| commit | 16f060c56f509ab1c4a77dfbe02d5cd77c977d54 (patch) | |
| tree | 31c2cf88ff19d0926226cdf97dc4bf463ea55e02 /scripts | |
| parent | fed27b09454c8e84ffdd5e3da65d2aa71db01032 (diff) | |
| download | poky-16f060c56f509ab1c4a77dfbe02d5cd77c977d54.tar.gz | |
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.
(From OE-Core rev: 21d015f6c9927598d64c48c925638619b25cf232)
Signed-off-by: Olof Johansson <olofjn@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions