[PATCH] oeqa/parselogs: Added another batch of errors to the whitelist.

[PATCH] oeqa/parselogs: Added another batch of errors to the whitelist.

[Lucian Musat]

Signed-off-by: Lucian Musat <george.l.musat@intel.com>
---
 meta/lib/oeqa/runtime/parselogs.py | 15 +++++++++++----
 1 file changed, 11 insertions(+), 4 deletions(-)

diff --git a/meta/lib/oeqa/runtime/parselogs.py b/meta/lib/oeqa/runtime/parselogs.py
index e9ccd0c..9c1b822 100644
--- a/meta/lib/oeqa/runtime/parselogs.py
+++ b/meta/lib/oeqa/runtime/parselogs.py
@@ -18,6 +18,8 @@ common_errors = [
     "can\'t disable ASPM",
     "Failed to load module \"vesa\"",
     "Failed to load module vesa",
+    "Failed to load module \"fbdev\"",
+    "Failed to load module fbdev",
     "Failed to load module \"modesetting\"",
     "Failed to load module modesetting",
     "Failed to load module \"glx\"",
@@ -26,7 +28,9 @@ common_errors = [
     "_OSC failed (AE_NOT_FOUND); disabling ASPM",
     "Open ACPI failed (/var/run/acpid.socket) (No such file or directory)",
     "NX (Execute Disable) protection cannot be enabled: non-PAE kernel!",
-    "hd.: possibly failed opcode"
+    "hd.: possibly failed opcode",
+    'NETLINK INITIALIZATION FAILED',
+    'kernel: Cannot find map file'
     ]
 
 x86_common = [
@@ -63,7 +67,12 @@ ignore_errors = {
         'mmci-pl18x: probe of fpga:0b failed with error -22',
         'Failed to load module "glx"'
         ] + common_errors,
-    'emenlow' : x86_common,
+    'emenlow' : [
+        '[Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness'
+        ] + x86_common,
+    'core2_32' : [
+        '[Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness'
+        ] + x86_common,
     'crownbay' : x86_common,
     'genericx86' : x86_common,
     'genericx86-64' : x86_common,
@@ -72,13 +81,11 @@ ignore_errors = {
         ] + common_errors,
     'minnow' : [
         'netlink init failed',
-        'NETLINK INITIALIZATION FAILED',
         ] + common_errors,
     'jasperforest' : [
         'Activated service \'org.bluez\' failed:',
         'Unable to find NFC netlink family',
         'netlink init failed',
-        'NETLINK INITIALIZATION FAILED',
         ] + common_errors,
 }
 
-- 
2.1.4

Re: [PATCH] oeqa/parselogs: Added another batch of errors to the whitelist.

[Richard Purdie]

On Fri, 2015-05-29 at 14:29 +0300, Lucian Musat wrote:
> Signed-off-by: Lucian Musat <george.l.musat@intel.com>
> ---
>  meta/lib/oeqa/runtime/parselogs.py | 15 +++++++++++----
>  1 file changed, 11 insertions(+), 4 deletions(-)

This appears to breaks things:
http://errors.yoctoproject.org/Errors/Search/Args/?items=10&query=3bab6127758854542e07edacaeb849b30b0dca86


Cheers,

Richard

Re: [PATCH] oeqa/parselogs: Added another batch of errors to the whitelist.

[Musat, George L]

Hi Richard,

Are you sure it's this patches fault for that? I only added some more errors to the lists. Also I tested the patch locally and runs fine on qemux86 master. For the Centos it looks like a network problem occurred half way into the tests.

-----Original Message-----
From: Richard Purdie [mailto:richard.purdie@linuxfoundation.org] 
Sent: Sunday, May 31, 2015 12:27 AM
To: Musat, George L
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] oeqa/parselogs: Added another batch of errors to the whitelist.

On Fri, 2015-05-29 at 14:29 +0300, Lucian Musat wrote:
> Signed-off-by: Lucian Musat <george.l.musat@intel.com>
> ---
>  meta/lib/oeqa/runtime/parselogs.py | 15 +++++++++++----
>  1 file changed, 11 insertions(+), 4 deletions(-)

This appears to breaks things:
http://errors.yoctoproject.org/Errors/Search/Args/?items=10&query=3bab6127758854542e07edacaeb849b30b0dca86


Cheers,

Richard

Re: [PATCH] oeqa/parselogs: Added another batch of errors to the whitelist.

[Richard Purdie]

On Tue, 2015-06-02 at 09:50 +0000, Musat, George L wrote:
> Hi Richard,
> 
> Are you sure it's this patches fault for that? I only added some more
> errors to the lists. Also I tested the patch locally and runs fine on
> qemux86 master. For the Centos it looks like a network problem
> occurred half way into the tests.

I saw the same error locally, when I reverted the patch it went away so
I'm pretty sure it was from this patch, yes.

Cheers,

Richard