During testing we're finding some kernel oops messages and other key kernel errors such as irq issues are not triggering our log parsing.
Add those keywords to the list of things to scan for, making such failures much more visible. Signed-off-by: Richard Purdie <[email protected]> --- meta/lib/oeqa/runtime/cases/parselogs.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/lib/oeqa/runtime/cases/parselogs.py b/meta/lib/oeqa/runtime/cases/parselogs.py index 6966923c94d..47c77fccd50 100644 --- a/meta/lib/oeqa/runtime/cases/parselogs.py +++ b/meta/lib/oeqa/runtime/cases/parselogs.py @@ -34,7 +34,7 @@ class ParseLogsTest(OERuntimeTestCase): log_locations = ["/var/log/", "/var/log/dmesg", "/tmp/dmesg_output.log"] # The keywords that identify error messages in the log files - errors = ["error", "cannot", "can't", "failed"] + errors = ["error", "cannot", "can't", "failed", "---[ cut here ]---", "No irq handler for vector"] # A list of error messages that should be ignored ignore_errors = []
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#201171): https://lists.openembedded.org/g/openembedded-core/message/201171 Mute This Topic: https://lists.openembedded.org/mt/106890109/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
