Open
Bug 1442645
Opened 7 years ago
Updated 3 years ago
[mozlog] mozlog.structuredlog: Failure calling log handler, due to KeyError: 'subtest'
Categories
(Testing :: Mozbase, defect, P3)
Tracking
(Not tracked)
NEW
People
(Reporter: bryce, Unassigned)
Details
When running
`./mach mochitest dom/media/tests/mochitest/test_getUserMedia_[a-m]* --use-test-media-devices`
if I encounter test failures (which you can do in this case by stealing focus from the testing window), when the tests finish instead of getting a clean log I get the following:
SUITE-END | took 160s
mozlog.structuredlog: Failure calling log handler:
Traceback (most recent call last):
File "/home/b/projects/mozilla/mozilla-central/testing/mozbase/mozlog/mozlog/structuredlog.py", line 246, in _handle_log
handler(data)
File "/home/b/projects/mozilla/mozilla-central/testing/mozbase/mozlog/mozlog/handlers/base.py", line 96, in __call__
formatted = self.formatter(data)
File "/home/b/projects/mozilla/mozilla-central/testing/mozbase/mozlog/mozlog/handlers/base.py", line 65, in __call__
return self.inner(item)
File "/home/b/projects/mozilla/mozilla-central/testing/mozbase/mozlog/mozlog/formatters/tbplformatter.py", line 44, in __call__
return super(TbplFormatter, self).__call__(data)
File "/home/b/projects/mozilla/mozilla-central/testing/mozbase/mozlog/mozlog/reader.py", line 74, in __call__
return handler(data)
File "/home/b/projects/mozilla/mozilla-central/testing/mozbase/mozlog/mozlog/formatters/tbplformatter.py", line 298, in shutdown
rv.append(self._format_suite_summary(suite, summary))
File "/home/b/projects/mozilla/mozilla-central/testing/mozbase/mozlog/mozlog/formatters/tbplformatter.py", line 289, in _format_suite_summary
rv.append(" {}".format(self._format_status(data)))
File "/home/b/projects/mozilla/mozilla-central/testing/mozbase/mozlog/mozlog/formatters/tbplformatter.py", line 185, in _format_status
data["status"], data["test"], data["subtest"],
KeyError: 'subtest'
Updated•7 years ago
|
Priority: -- → P3
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•