Closed
Bug 794885
Opened 12 years ago
Closed 12 years ago
Decoding app_info object fails with "TypeError: expected string or buffer"
Categories
(Testing Graveyard :: Mozmill, defect)
Testing Graveyard
Mozmill
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: whimboo, Unassigned)
References
Details
(Keywords: regression)
Running Mozmill on Windows gives me the following failure right after the initial start. Looks like we are failing in decoding the appinfo object now. Looks like a regression from my patch on bug 793764. :/ Traceback (most recent call last): File "z:\data\code\mozmill\mozmill\mozmill\__init__.py", line 751, in run mozmill.run(tests, self.options.restart) File "z:\data\code\mozmill\mozmill\mozmill\__init__.py", line 393, in run frame = self.run_test_file(frame or self.start_runner(), File "z:\data\code\mozmill\mozmill\mozmill\__init__.py", line 317, in start_runner self.results.appinfo = self.get_appinfo(self.bridge) File "z:\data\code\mozmill\mozmill\mozmill\__init__.py", line 427, in get_appinfo app_info = json.loads(mozmill.getApplicationDetails()) File "c:\mozmill-2-env\python\Lib\json\__init__.py", line 326, in loads return _default_decoder.decode(s) File "c:\mozmill-2-env\python\Lib\json\decoder.py", line 366, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) TypeError: expected string or buffer
Reporter | ||
Comment 1•12 years ago
|
||
Fixed by backing out the patch on bug 793764. I will take care of the issue on that bug before re-pushing.
Status: NEW → RESOLVED
Closed: 12 years ago
OS: Windows XP → All
Resolution: --- → FIXED
Whiteboard: [mozmill-2.0?]
Assignee | ||
Updated•8 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•