parselogs: add new whitelist entries to address 4.4.3 issues
PATCH v2 1/1 parselogs: add new whitelist entries to address 4.4.3 issues
Adds intel-corei7-64 with x86-common, this makes the x86-common whitelist available for intel-corei7-64 bsp also.
[YOCTO #9179]
--- meta/lib/oeqa/runtime/parselogs.py | 2 ++ 1 file changed, 2 insertions(+)
meta/lib/oeqa/runtime/parselogs.py +2 -0
@@ -54,6 +54,7 @@ x86_common = [ 'wrong ELF class', 'Could not enable PowerButton event', 'probe of LNXPWRBN:00 failed with error -22', + 'pmd_set_huge: Cannot satisfy', ] + common_errors qemux86_common = [
@@ -110,6 +111,7 @@ ignore_errors = { '(EE) open /dev/fb0: No such file or directory', '(EE) AIGLX: reverting to software rendering', ] + x86_common, + 'intel-corei7-64' : x86_common, 'crownbay' : x86_common, 'genericx86' : x86_common, 'genericx86-64' : x86_common,
Signature · 1 line
2.5.0
Did this v2 get missed? I see the first patch got merged.
Sau!
Quoted 34 lines · Saul Wold
Adds intel-corei7-64 with x86-common, this makes the x86-common whitelist available for intel-corei7-64 bsp also.
[YOCTO #9179]
Signed-off-by Saul Wold <[email protected]>---
meta/lib/oeqa/runtime/parselogs.py | 2 ++1 file changed, 2 insertions(+)meta/lib/oeqa/runtime/parselogs.py +1
-0@@ -54,6 +54,7 @@ x86_common = [ 'wrong ELF class', 'Could not enable PowerButton event', 'probe of LNXPWRBN:00 failed with error -22', + 'pmd_set_huge: Cannot satisfy',] +
common_errors
qemux86_common = [meta/lib/oeqa/runtime/parselogs.py +1
-0@@ -110,6 +111,7 @@ ignore_errors = { '(EE) open /dev/fb0: No such file or directory', '(EE) AIGLX: reverting to software rendering', ] + x86_common, + 'intel-corei7-64' : x86_common, 'crownbay' : x86_common, 'genericx86' : x86_common, 'genericx86-64' : x86_common,--
2.5.0
Quoted 1 line · Saul Wold
Did this v2 get missed? I see the first patch got merged.
Clearly it got missed sorry.
I appreciate that is frustrating for people, equally, we do some level of testing of changes going in, which introduces delay and when you have ~80 patches you're about to merge and scan the lists for new versions, its sometimes hard to catch everything :(.
Its also even harder when the v2 is buried in some random git branch somewhere which I appreciate in this case it wasn't but does cause problems in general.
Cheers,
Richard