David Matson

And just to clarify, the "streaming" here is specifically what --gtest_stream_result_to does.

@asoffer - I'm hoping to make use of this data in a situation where we need to get this information during test execution. I don't think JSON or XML will...

Even worse: ```c++ #include TEST(SampleFixture, SuccessWithCustomMessage) { GTEST_SUCCEED()

Proposed fix: Change the event=TestPartResult... to add &type=. For example: ``` event=TestPartResult&file=path\to\some_file.cpp&line=123&type=success&message=custom message event=TestPartResult&file=path\to\some_file.cpp&line=123&type=failure&message=custom message event=TestPartResult&file=path\to\some_file.cpp&line=123&type=non_fatal_failure&message=custom message event=TestPartResult&file=path\to\some_file.cpp&line=123&type=skip&message=custom message ```

> Can you say a bit more? What do you mean by "processing"? By "streaming" do you mean text written to `stderr` and `stdout`? Sorry, I should have clarified -...

#3989

@asoffer - would you mind approving the workflow so it can run? Thanks!

@asoffer - I fixed the workflow errors locally; if you wouldn't mind re-approving to run again, that would be great - thanks!

@asoffer - re-configured to include gmock tests and fixed those too; if you wouldn't mind re-approving to run again, that would be great - thanks!

@asoffer - I'm not sure what's happening with the failing tests. The only one that failed before locally seemed completely unrelated to code that's changing in this PR. I rebased...