diff mbox series

oeqa/runtime/parselogs: ignore jitterentropy health failure

Message ID 20231003122542.764073-1-ross.burton@arm.com
State New
Headers show
Series oeqa/runtime/parselogs: ignore jitterentropy health failure | expand

Commit Message

Ross Burton Oct. 3, 2023, 12:25 p.m. UTC 
From: Ross Burton <ross.burton@arm.com>

Sometimes the jitterentropy RNG fails to initialise on boot.  My hunch
is that this is due to the hardware timer not being high resolution
enough combined with running inside a virtualised machine on a loaded
host, and whilst the message looks bad it basically says "driver not
suitable for hardware".

I've contacted the author of the jitterentropy code to confirm or deny
this hunch, but until then we can easily ignore the failure.

Signed-off-by: Ross Burton <ross.burton@arm.com>
---
 meta/lib/oeqa/runtime/cases/parselogs.py | 1 +
 1 file changed, 1 insertion(+)
diff mbox series

Patch

diff --git a/meta/lib/oeqa/runtime/cases/parselogs.py b/meta/lib/oeqa/runtime/cases/parselogs.py
index a805edd79dd..a1ffb93b8e4 100644
--- a/meta/lib/oeqa/runtime/cases/parselogs.py
+++ b/meta/lib/oeqa/runtime/cases/parselogs.py
@@ -65,6 +65,7 @@  common_errors = [
     "Failed to read LoaderConfigTimeoutOneShot variable, ignoring: Operation not supported",
     "Failed to read LoaderEntryOneShot variable, ignoring: Operation not supported",
     "invalid BAR (can't size)",
+    "jitterentropy: Initialization failed with host not compliant with requirements: 9"
     ]
 
 x86_common = [