In attempting to debug some intermittent failures recently (bug 1052467), I found that I couldn't do things like Cu.reportError() and have those output in the logs. Having the browser console logs available would have been invaluable in helping to understand the true causes of the failure. Even if we have to make it a manual turn on switch so as not to affect the normal perf results, it would have been useful.
Hi Mark, I've started working on this with the help of Joel. In your use case, would this need to be added to every test like in https://dxr.mozilla.org/mozilla-central/source/testing/talos/talos/startup_test/tspaint_test.html#52? Or would setting a preference which would allow you to pull from stdout/stderror be more appropriate?
I think the end goal, would be log output in such a way that when runing tests on treeherder, you can easily get the output, e.g. the "artifact uploaded" links here: https://treeherder.mozilla.org/logviewer.html#?job_id=22849743&repo=mozilla-inbound Obviously we'll want to be able to get those when run manually as well. I don't think I have a specific method in mind.
Status: NEW → RESOLVED
Last Resolved: 4 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.