summaryrefslogtreecommitdiff
path: root/meta/recipes-devtools/gcc
diff options
context:
space:
mode:
authorJianxun Zhang <jianxun.zhang@linux.intel.com>2016-09-27 14:32:04 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-09-29 00:32:58 +0100
commit2e15b478343c6703c37b9a45e61c9de200d98027 (patch)
tree38f6ce768e8124ab5f66c7721465af916a62f330 /meta/recipes-devtools/gcc
parent5100bb36502ef7c81220a3c4809eb1b3ac83801f (diff)
downloadopenembedded-core-2e15b478343c6703c37b9a45e61c9de200d98027.tar.gz
openembedded-core-2e15b478343c6703c37b9a45e61c9de200d98027.tar.bz2
openembedded-core-2e15b478343c6703c37b9a45e61c9de200d98027.zip
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] Signed-off-by: Jianxun Zhang <jianxun.zhang@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-devtools/gcc')
0 files changed, 0 insertions, 0 deletions