tree 0c0ca5c30611c9a7a4f9c69da9c6c1d23c45d535
parent 96206c5a863b1262868055ebb7b29cb16877bb02
author Prashanth B <beeps@google.com> 1394825789 -0700
committer chrome-internal-fetch <chrome-internal-fetch@google.com> 1396394499 +0000

[autotest] Add clarity to run_suite aborts.

1. Timestamp the create suite job rpc so we know if the devserver took
    too long to stage test control files.
2. Timestamp suite creation, then use it to determine if a suite was
    timed out.
3. Diagnose DUTs in the pool this suite ran/should have run on when
    a timeout happens, so we can easily identify cases of resource
    contention.
4. Diagnose the suite job halfway till its timeout, and log links to
    the incomplete sub-jobs. This also serves to postpone buildbots
    built-in silent timeout.
5. Include a link to the suite job instead of the id.

TEST=Ran suites, timed them out.
BUG=chromium:341494,chromium:351848

Change-Id: Ied99bb102aee12c22ba72da05cfc23562572bcb7
Reviewed-on: https://chromium-review.googlesource.com/190100
Reviewed-by: Prashanth B <beeps@chromium.org>
Commit-Queue: Prashanth B <beeps@chromium.org>
Tested-by: Prashanth B <beeps@chromium.org>