http://mozilla-releng-blobs.s3.amazonaws.com/blobs/mozilla-inbound/sha512/7a2337bc9e0fc209f549b18507247539ccb97a99a42172764890bf33e48ff602511b3781f4afbe211ca78fdd6a542458012b51a3f80475fa5d8364a028ca2cd4 Note the mass of '\n' instead of newlines rendering the log basically unusable.
That's a raw JSON log, so actual newlines mean something to machine consumers, and if large amounts of text are stuffed into message objects, readability will inevitably decline. In most cases the TBPL-style log has about as much information critical to debugging failures as the raw mozlog JSON log, but for gaia-ui tests information (such as page sources, where those newlines come in, I think), is added so that the raw JSON log can be used to drive a replacement for the html and xunit reports usually generated by gaia tests. For all marionette based tests, things like the browser stdout end up in gecko.log or logcat. We have a goal this quarter of building a ui in treeherder driven by the raw JSON log, that is tracked by bug 1113873.
Yeah, this is by-design so I propose Invalid. If you want to read the log there are already tools that will allow you to convert a specific log file to a more readable format.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.