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

Issue 731506 link

Starred by 1 user
Status: WontFix
Owner:
█ shuqianz@chromium.org
Last visit > 30 days ago
Closed: Jun 2017
Cc:
davidri...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Export suite results to gcloud for async tests

Project Member Reported by dgarr...@chromium.org, Jun 9 2017 
As I understand it, suite report generates a json file describing each suite run, and run_suite then exports that json file to gcloud.

Can we find a way to do this for asynchronous tests, which don't have a run_suite process waiting to do the export?

Comment 1 by shuqianz@chromium.org, Jun 9 2017 

Sorry, I think I gave you the wrong answer yesterday. The suite report is not generated by run_suite.py. It is generated by tko/parse.py, which belongs to one step in scheduler. It will use the afe suite job id to read all the tests from db, and generate report for it. I think asynchronous test is included in the report too

Comment 2 by shuqianz@chromium.org, Jun 9 2017

Status: WontFix (was: Untriaged)

Comment 3 by dgarr...@chromium.org, Jun 9 2017 

Who uploads that data to gcloud?

Comment 4 by shuqianz@chromium.org, Jun 9 2017 

also tko/parser

Comment 5 by davidri...@chromium.org, Jun 12 2017 

We need to change it so we include a buildbot link to suite details (opened  issue 732456 ).  Here's an example async suite.
https://viceroy.corp.google.com/chromeos/suite_details?job_id=122939357

Theres repeated provision so I assume that there's some thrashing going on.
►

Sign in to add a comment