summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2023-06-16 16:41:43 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2023-06-17 11:50:56 +0100
commit62c5556025bf9714ab8fb0a1c33ee49c35e2e8ed (patch)
tree8324796b2680f81f9b8fcc7f8a360a71ee41aefb
parent460fabb834758c8a3c47825d44a2363c585786b2 (diff)
downloadpoky-62c5556025bf9714ab8fb0a1c33ee49c35e2e8ed.tar.gz
oeqa/logparser: Fix ptest No-section exception
Occasionally we see: File "/media/build/poky/meta/lib/oeqa/runtime/cases/ptest.py", line 27, in test_ptestrunner_expectfail self.do_ptestrunner() File "/media/build/poky/meta/lib/oeqa/runtime/cases/ptest.py", line 77, in do_ptestrunner results, sections = parser.parse(ptest_runner_log) File "/media/build/poky/meta/lib/oeqa/utils/logparser.py", line 80, in parse self.results[current_section['name']][result.group(1).strip()] = t KeyError: 'No-section' which occurs when there are "results" outside the main log section. The strace tests do then upon failure as they dump logs there. Add code to avoid the tracebacks and just make them warnings. (From OE-Core rev: d9bf95d8cfb123f9d992fd2a95099bdcece97be8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--meta/lib/oeqa/utils/logparser.py5
1 files changed, 4 insertions, 1 deletions
diff --git a/meta/lib/oeqa/utils/logparser.py b/meta/lib/oeqa/utils/logparser.py
index 60df754b36..8054acc853 100644
--- a/meta/lib/oeqa/utils/logparser.py
+++ b/meta/lib/oeqa/utils/logparser.py
@@ -77,7 +77,10 @@ class PtestParser(object):
77 for t in test_regex: 77 for t in test_regex:
78 result = test_regex[t].search(line) 78 result = test_regex[t].search(line)
79 if result: 79 if result:
80 self.results[current_section['name']][result.group(1).strip()] = t 80 try:
81 self.results[current_section['name']][result.group(1).strip()] = t
82 except KeyError:
83 bb.warn("Result with no section: %s - %s" % (t, result.group(1).strip()))
81 84
82 # Python performance for repeatedly joining long strings is poor, do it all at once at the end. 85 # Python performance for repeatedly joining long strings is poor, do it all at once at the end.
83 # For 2.1 million lines in a log this reduces 18 hours to 12s. 86 # For 2.1 million lines in a log this reduces 18 hours to 12s.