Re: [PATCH] parselogs: Ignore uvesafb timeouts

[Jianxun Zhang <jianxun.zhang@linux.intel.com>]

> On Aug 19, 2016, at 8:29 AM, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> 
> We're periodically seeing uvesafb timeouts on the autobuilder. Whitelist these
> errors as there is little it seems we can do about them and we therefore
> choose to ignore them rather than fail the builds.
> 
> [YOCTO #8245]
> 
> There is a better solution proposed in the bug with a -1 timeout however
> this avoids failed builds until such times as that is implemented.
I am working on the -1 timeout patch. It could take another several days for dev and validation in next week.

Please just go ahead to merge this for any urgency. Refer to my inline clarification too.
> 
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> 
> diff --git a/meta/lib/oeqa/runtime/parselogs.py b/meta/lib/oeqa/runtime/parselogs.py
> index 1cfe804..777af57 100644
> --- a/meta/lib/oeqa/runtime/parselogs.py
> +++ b/meta/lib/oeqa/runtime/parselogs.py
> @@ -63,6 +63,9 @@ qemux86_common = [
>     "fail to add MMCONFIG information, can't access extended PCI configuration space under this bridge.",
>     "can't claim BAR ",
>     'amd_nb: Cannot enumerate AMD northbridges',
> +    'uvesafb: 5000 ms task timeout error’,
This line will be whitelisted even when the -1 timeout patch is in because we cannot fix bandwidth issue on AB server and still wanna keep this log visible as heads up.
> +    'detected fb_set_par error, error code: -22',
> +    'uvesafb: mode switch failed’\
These errors from callers should not be whitelisted with the -1 timeout patch. Once we have that patch merged, they are still valid errors to indicate a non-timeout root case, or that patch doesn’t do the expected job. The problem of whitelisting  is we could miss other cases in call chains, or cover other root causes of a same error. This is another variant:

[  126.670550] uvesafb: 5000 ms task timeout error
[  126.673310] uvesafb: Getting VBE info block failed (eax=0x4f00, err=1)
[  126.673684] uvesafb: vbe_init() failed with -22

(bz8245 comment #23)

You may want to add “Getting VBE..” lines in this patch too, just don’t be confused when seeing another new uncaught variant.



> ] + common_errors
> 
> ignore_errors = { 
> 
> 
> -- 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core