Store tombstones url, not the actual tombstones, inside test result.

Store tombstones url, not the actual tombstones, inside test result.

Previously we store the actual, huge tombstones inside test result
object. Now we record tombstones through logdog and view the tombstones
by visiting a url. Thus in test result object, we don't need the actual
tombstones anymore. We can just store the lighter tombstones url.

BUG=631213
Committed: https://crrev.com/6dd8eaafd2b4b13b712428688d0a7d397102bb29
Cr-Commit-Position: refs/heads/master@{#440199}

[BigBossZhiling, 2016-12-15 04:26:22]

Description was changed from

==========
Store tombstones url, not the actual tombstones, inside test result.

Previously we store the actual, huge tombstones inside test result
object. Now we record tombstones through logdog and view the tombstones
by visiting a url. Thus in test result object, we don't need the actual
tombstones anymore. We can just store the lighter tombstones url.

BUG=631213
==========

to

==========
Store tombstones url, not the actual tombstones, inside test result.

Previously we store the actual, huge tombstones inside test result
object. Now we record tombstones through logdog and view the tombstones
by visiting a url. Thus in test result object, we don't need the actual
tombstones anymore. We can just store the lighter tombstones url.

BUG=631213
==========

[BigBossZhiling, 2016-12-15 04:26:22]

hzl@google.com changed reviewers:
+ jbudorick@chromium.org

[BigBossZhiling, 2016-12-15 04:27:27]

Changed the content of json results. After this cl, I will change the test
results presentation file, which makes use of the json results file changed in
thie cl.

[jbudorick, 2016-12-15 22:31:35]

https://codereview.chromium.org/2581553004/diff/20001/build/android/pylib/loc...
File build/android/pylib/local/device/local_device_gtest_run.py (right):

https://codereview.chromium.org/2581553004/diff/20001/build/android/pylib/loc...
build/android/pylib/local/device/local_device_gtest_run.py:418:
resolved_tombstones = None
Should we switch this & the if check below to tombstones_url?

https://codereview.chromium.org/2581553004/diff/20001/build/android/pylib/loc...
build/android/pylib/local/device/local_device_gtest_run.py:427: stream_name =
'tombstones_%s_%s_%s' % (
That said, this stream name may be confusing if we first have a crash for test A
that then gets associated w/ a test B.

[BigBossZhiling, 2016-12-20 19:34:08]

https://codereview.chromium.org/2581553004/diff/20001/build/android/pylib/loc...
File build/android/pylib/local/device/local_device_gtest_run.py (right):

https://codereview.chromium.org/2581553004/diff/20001/build/android/pylib/loc...
build/android/pylib/local/device/local_device_gtest_run.py:418:
resolved_tombstones = None
On 2016/12/15 22:31:35, jbudorick wrote:
> Should we switch this & the if check below to tombstones_url?

Done.

https://codereview.chromium.org/2581553004/diff/20001/build/android/pylib/loc...
build/android/pylib/local/device/local_device_gtest_run.py:427: stream_name =
'tombstones_%s_%s_%s' % (
On 2016/12/15 22:31:35, jbudorick wrote:
> That said, this stream name may be confusing if we first have a crash for test
A
> that then gets associated w/ a test B.

Done.

[jbudorick, 2016-12-21 01:07:56]

lgtm

[BigBossZhiling, 2016-12-21 18:50:01]

The CQ bit was checked by hzl@google.com

[commit-bot: I haz the power, 2016-12-21 18:50:22]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-21 20:18:36]

CQ is committing da patch.

Bot data: {"patchset_id": 40001, "attempt_start_ts": 1482346201967710,
"parent_rev": "68273af7b9cd6896677c90b212446041f3149971", "commit_rev":
"069da668ed272a1f6c60ed47d3f4262faa040cb9"}

[commit-bot: I haz the power, 2016-12-21 20:19:08]

Description was changed from

==========
Store tombstones url, not the actual tombstones, inside test result.

Previously we store the actual, huge tombstones inside test result
object. Now we record tombstones through logdog and view the tombstones
by visiting a url. Thus in test result object, we don't need the actual
tombstones anymore. We can just store the lighter tombstones url.

BUG=631213
==========

to

==========
Store tombstones url, not the actual tombstones, inside test result.

Previously we store the actual, huge tombstones inside test result
object. Now we record tombstones through logdog and view the tombstones
by visiting a url. Thus in test result object, we don't need the actual
tombstones anymore. We can just store the lighter tombstones url.

BUG=631213

Review-Url: https://codereview.chromium.org/2581553004
==========

[commit-bot: I haz the power, 2016-12-21 20:19:08]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-12-21 20:21:11]

Description was changed from

==========
Store tombstones url, not the actual tombstones, inside test result.

Previously we store the actual, huge tombstones inside test result
object. Now we record tombstones through logdog and view the tombstones
by visiting a url. Thus in test result object, we don't need the actual
tombstones anymore. We can just store the lighter tombstones url.

BUG=631213

Review-Url: https://codereview.chromium.org/2581553004
==========

to

==========
Store tombstones url, not the actual tombstones, inside test result.

Previously we store the actual, huge tombstones inside test result
object. Now we record tombstones through logdog and view the tombstones
by visiting a url. Thus in test result object, we don't need the actual
tombstones anymore. We can just store the lighter tombstones url.

BUG=631213

Committed: https://crrev.com/6dd8eaafd2b4b13b712428688d0a7d397102bb29
Cr-Commit-Position: refs/heads/master@{#440199}
==========

[commit-bot: I haz the power, 2016-12-21 20:21:12]

Patchset 3 (id:??) landed as
https://crrev.com/6dd8eaafd2b4b13b712428688d0a7d397102bb29
Cr-Commit-Position: refs/heads/master@{#440199}