New issue
Advanced search Search tips

Issue 806863 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug


Participants' hotlists:
Test-Use-Cases


Sign in to add a comment

output from isolated scripts should be uploaded to test-results.appspot.com

Project Member Reported by jochen@chromium.org, Jan 29 2018

Issue description

output from isolated scripts such as "content_shell_crash_test" should automatically be uploaded to test-results.appspot.com.

Since they don't use testenv.py, I don't see an easy way to achieve this, but it seems like something that should just happen for all isolated scripts?
 
FYI I believe our plan for ShamWow is to have it pull test results from Isolate whenever a test step finishes running on Swarming. 

Comment 2 by jochen@chromium.org, Feb 19 2018

does that mean that I don't have to do anything, and this will just work eventually?
Yes. What format do these tests use for output?

Comment 4 by jochen@chromium.org, Feb 20 2018

The isolated script outputs a single json object { valid: True, failure: 'failure reason' }: https://cs.chromium.org/chromium/src/testing/scripts/content_shell_crash_test.py?rcl=25672cf164676a4d621e54ceb2f1b912dbcf7493&l=73

The actual test writes it status to stdout/stderr
Cc: no...@chromium.org
nodir@ since your team owns test results data now, you should address these problems with whatever you build to replace test-results.
Owner: estaab@chromium.org
reassigning to LUCI team

Sign in to add a comment