diff options
| author | Jianxun Zhang <jianxun.zhang@linux.intel.com> | 2016-09-27 14:32:04 -0700 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-09-30 16:51:15 +0100 |
| commit | e0e8cd039cc760b6eb24a6d52e7d7bf09aef0abc (patch) | |
| tree | 8aa3456d88f5b301e8ef649ce4e5f8b4896f2772 /meta/classes/live-vm-common.bbclass | |
| parent | 5753147ea214cedb317ca1bbb8599cb896e5dc13 (diff) | |
| download | poky-e0e8cd039cc760b6eb24a6d52e7d7bf09aef0abc.tar.gz | |
parselogs: Update uvesafb errors in qemu whitelist
This change only whitelists the timeout message in infinite
wait case in uvesafb driver.
With the latest timeout patch introducing infinite wait in
uvesafb driver, we whitelist the timeout message since it works
as a warning for issues related to timeout not to be fixed in
build servers.
We remove other errors for bug-discovering purposes in some cases
where these lines are still worthy to be caught (not whitelisted):
The removed errors show up again in the infinite wait case. It
indicates a different root cause or the timeout patch doesn't work
correctly.
Timeout happens when developers explicitly set a non-negative timeout
of a limited period to wait for task completion in uvesafb driver.
Timeout or/and errors occur when kernel doesn't have the latest
timeout patch in driver.
Note: The latest timeout patch is tracked by:
a2966330bcd29e99c0403235edb29433b0c53d56
[YOCTO #8245]
(From OE-Core rev: 2e15b478343c6703c37b9a45e61c9de200d98027)
Signed-off-by: Jianxun Zhang <jianxun.zhang@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes/live-vm-common.bbclass')
0 files changed, 0 insertions, 0 deletions