Traceback (most recent call last):
File "D:\src\llvm\tools\lldb\test\dotest.py", line 7, in <module>
lldbsuite.test.run_suite()
File "D:\src\llvm\tools\lldb\packages\Python\lldbsuite\test\dotest.py",
line 897, in run_suite
setupTestResults()
File "D:\src\llvm\tools\lldb\packages\Python\lldbsuite\test\dotest.py",
line 481, in setupTestResults
formatter_spec.formatter.handle_event(initialize_event)
File
"D:\src\llvm\tools\lldb\packages\Python\lldbsuite\test_event\formatter\pickled.py",
line 72, in handle_event
self.serializer.serialize(test_event, self.out_file)
File
"D:\src\llvm\tools\lldb\packages\Python\lldbsuite\test_event\formatter\pickled.py",
line 45, in serialize
cPickle.dump(test_event, out_file)
TypeError: write() argument must be str, not bytes
Press any key to continue . . .
On Fri, May 13, 2016 at 1:18 PM Zachary Turner <ztur...@google.com> wrote:
> zturner added a comment.
>
> I'm looking into a little bit. Currently I'm seeing that the temporary
> events file is completely empty. I can run the same command line that
> we're using in the subprocess.call() line, where in the code should I be
> looking to see events getting written to the file?
>
>
> http://reviews.llvm.org/D20193
>
>
>
>
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
