wwag110465 / js-test-driver

Automatically exported from code.google.com/p/js-test-driver
0 stars 0 forks source link

FireFox output from error stream not readable in output log #290

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Cause FireFox to fail and write to the error stream on startup - in our case 
FireFox did not have permission to write to the ~/.mozilla directory
2. Start JsTestDriver, find the FireFox error in the resulting output 

What is the expected output? What do you see instead?

The expected output is the error stream from FireFox. instead we see:

error:
[B@28996b65

(while is a toString()'ed Java byte stream)

What version of the product are you using? On what operating system?

Linux RedHat 4.1, Fedora 15.

Please provide any additional information below.

We patched JsTestDriver to see the error stream output from which we got the 
information to solve our problem, I've attached the diff.

Currently when producing the error log, CommandLineBrowserRunner (line 139) 
calls append() on the StringBuilder using a byte[] as the parameter. This calls 
the append(Object) method on StringBuilder (StringBuilder does not have and 
append(byte[]) method), and .toString is called on the parameter, resulting in 
the memory location output shown above. 

What is should be doing is building a String first out of the byte[] before 
calling append. My diff showing this is attached.

Original issue reported on code.google.com by c.kubi...@gmail.com on 4 Nov 2011 at 11:36

Attachments: