Chris Manchester (limited bugmail, email directly) Assignee
	Description • 10 years ago

Getting rid of the regex based output parser in mozharness is the end of the line for unstructured failure output from mochitest.

	Chris Manchester (limited bugmail, email directly) Assignee
	Comment 1 • 10 years ago

This is what I've found. Needs the mozharness piece to test. I'm skeptical an error from manifestLibrary.js would propagate correclty.

	Chris Manchester (limited bugmail, email directly) Assignee
	Comment 2 • 10 years ago

Bug 1097278 highlights that we'll need an "end of test run" marker from javascript in place of the old summary so we don't end up with a green in these situations.

	Andrew Halberstadt [:ahal]
	Comment 3 • 8 years ago

This is definitely something we should do, but the StructuredOutputParser in mozharness should also have the ability to fallback to regexes to find errors in unstructured output. It kind of already does:
https://dxr.mozilla.org/mozilla-central/source/testing/mozharness/mozharness/mozilla/structuredlog.py#49

If we still have a regex based fallback for unstructured output, we don't need to be super paranoid about errors slipping through the cracks.

	Paul Yang [:pyang] (away)
	Comment 4 • 8 years ago

//note to myself
working on poc for individual script to trigger mochitest with structuredLogOutputParser

	Paul Yang [:pyang] (away)
	Comment 5 • 8 years ago

while mochitest emits structured log, this will be solved once bug 1261194 fixed.
chmanchester, do you think we need patch for this bug?

	Chris Manchester (limited bugmail, email directly) Assignee
	Comment 6 • 8 years ago

So long as we're using the regex fallback, the patch in this bug isn't strictly necessary, but skimming it now I think it has some reasonable cleanups in it.