New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 704066 link

Starred by 1 user
Status: Assigned
Owner:
rmhasan@google.com
Cc:
perezju@chromium.org
bpastene@chromium.org
█ mcgreevy@chromium.org
crouleau@chromium.org
jbudorick@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----

Blocked on:
issue 748638


Sign in to add a comment

Get rid of the simplified json test output format

Project Member Reported by tansell@chromium.org, Mar 22 2017 
We currently have to support 3 *different* JSON formats for test result processing. They are;

 * What gtest outputs
 * What layout tests output - described at https://www.chromium.org/developers/the-json-test-results-format
 * Some random "simplified json format" which telemetry seems to output?

We should make our tools all standardized on one json format.

Before we do that, we should just should remove the simplified json format support.

Comment 1 by serg...@chromium.org, Mar 22 2017 

Thanks for filing this. I think we should standardize on https://www.chromium.org/developers/the-json-test-results-format, since this is a native format understood by Test Results Server, which was originally written for layout tests, but was designed in a way to be generic enough for other test suites.

Comment 2 by tansell@chromium.org, Mar 22 2017 

Once we reduce the number of formats down to 2 we can argue about which one to use :-)

Comment 3 by bpastene@chromium.org, Mar 22 2017

Components: -Infra Infra>Platform>Recipes

Comment 4 by iannucci@chromium.org, May 15 2017

Components: -Infra>Platform>Recipes Infra>Client>Chrome
Summary: Get rid of the simplified json test output format (was: Get rid of the simplified json format in recipes)

Comment 5 by ashleymarie@chromium.org, Jul 25 2017

Blockedon: 748638

Comment 6 by ashleymarie@chromium.org, Jul 27 2017 

I'm aiming to get rid of the simplified json output from the Telemetry side in Q4. We're switching over to outputting the json-test-results-format linked in earlier comments so our vote would be to use that over what gtest outputs, if we're trying to get down to one json format for testing :)

Comment 7 by bpastene@chromium.org, Dec 8 2017

Owner: ashleymarie@chromium.org
Status: Assigned (was: Untriaged)
Any updates on switching telemetry's json output?

Comment 8 by erikc...@chromium.org, Jan 4

Cc: bpastene@chromium.org jbudorick@chromium.org
Owner: ----
Status: Untriaged (was: Assigned)
What is this status of this bug?

Comment 9 by martiniss@chromium.org, Jan 4

Cc: nednguyen@chromium.org
I think perf tests output regular test results now. Someone on the perf side might know more.

Comment 10 by nedngu...@google.com, Jan 4

Cc: -nednguyen@chromium.org crouleau@chromium.org
Telemetry's json output (both unittest & benchmark) follows the json test results format

Comment 11 by crouleau@chromium.org, Jan 7

Owner: rmhasan@google.com
Rakib, Can you please link this bug up to to other Core Automation efforts to produce the standard format? Then we should ensure that Telemetry is doing the standard.

Comment 12 by gbeaty@chromium.org, Jan 7

Status: Assigned (was: Untriaged)

Comment 13 by perezju@chromium.org, Jan 10

Cc: perezju@chromium.org

Comment 14 by benhenry@google.com, Jan 11

Labels: Pri-2
Setting defect without priority to Pri-2.
►

Sign in to add a comment