oeqa/parselogs: Skip hda opcode errors

These occur when running images under virtualisation on machines with
high load which sometimes trigger timeouts in the kernel DMA code.
They're harmless to ignore in these cases.

Adding this since "failing" the build due to this is more annoying
thank useful.

[YOCTO #7387]

(From OE-Core rev: fb29441216435b9bae47ca9cd42db5a6b1fe77d8)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 2 insertions, 1 deletions

diff --git a/meta/lib/oeqa/runtime/parselogs.py b/meta/lib/oeqa/runtime/parselogs.py
index b1dcc1e6ce..cf0f67c628 100644
--- a/meta/lib/oeqa/runtime/parselogs.py
+++ b/meta/lib/oeqa/runtime/parselogs.py
@@ -22,7 +22,8 @@ common_errors = [
     "Failed to load module modesetting",
     "Failed to load module \"glx\"",
     "Failed to load module glx",
-    "[drm] Cannot find any crtc or sizes - going 1024x768"
+    "[drm] Cannot find any crtc or sizes - going 1024x768",
+    "hd.: possibly failed opcode"
     ]
 
 x86_common = [