1046852 - Exception in mozlog structured logging (mozlog 2.1)

Status: RESOLVED FIXED

(Remote Protocol :: Marionette, defect)

Description

[Zac C (:zac)]

Exception in thread Thread-1535:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.7/threading.py", line 763, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/var/jenkins/2/workspace/flame.mozilla-central.ui.functional.non-smoke/.env/local/lib/python2.7/site-packages/mozprocess-0.19-py2.7.egg/mozprocess/processhandler.py", line 774, in _processOutput
    self.processOutputLine(line.rstrip())
  File "/var/jenkins/2/workspace/flame.mozilla-central.ui.functional.non-smoke/.env/local/lib/python2.7/site-packages/mozprocess-0.19-py2.7.egg/mozprocess/processhandler.py", line 719, in processOutputLine
    handler(line)
  File "/var/jenkins/2/workspace/flame.mozilla-central.ui.functional.non-smoke/.env/local/lib/python2.7/site-packages/mozdevice-0.38-py2.7.egg/mozdevice/devicemanager.py", line 69, in _log
    self._logger.debug(data)
  File "/var/jenkins/2/workspace/flame.mozilla-central.ui.functional.non-smoke/.env/local/lib/python2.7/site-packages/mozlog-2.1-py2.7.egg/mozlog/structured/structuredlog.py", line 260, in log
    data = {"level": level_name, "message": unicode(message)}
UnicodeDecodeError: 'ascii' codec can't decode byte 0xd8 in position 750: ordinal not in range(128)


When we upgraded to marionette 0.8.1 some test runs cannot complete due to this error.

I can't see from our test run log what caused it:
http://jenkins1.qa.scl3.mozilla.com/job/flame.mozilla-central.ui.functional.non-smoke/42/consoleFull

Comment 1

[Jonathan Griffin (:jgriffin)]

I think a fix is either landing soon or already landed, in which case we might need to release a new version of marionette with an updated dependency.  cc'ing Chris who knows more.

Comment 2

[Andrew Halberstadt [:ahal]]

I think this is a dupe of bug 1042921. I'll ask over there if that patch would fix this or not.

Comment 3

[James Graham [:jgraham]]

Yes, the patch there should fix this.

Comment 4

[Andrew Halberstadt [:ahal]]

Hey Zac, this should be fixed now. Do you mind testing it out with the latest m-c? If it's fixed we should resolve this a dupe of bug 1042921. Thanks!

Comment 5

[Chris Manchester (limited bugmail, email directly)]

It this isn't fixed by bug 1042921, please let me know.

Comment 6

[Zac C (:zac)]

I'm not sure I'll be able to replicate this locally but I'll run a few tests and see what happens.

Comment 7

[Zac C (:zac)]

Had a few goes at replicating the failure scenario. The example was during a crash and it's hard to replicate. I'm not sure that it's fixed but it's at least working fine.

Comment 8

[Chris Manchester (limited bugmail, email directly)]

It looks like this was taken care of with bug 1042921.