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

Issue 606617 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

[Findit] Capture try job metadata as it becomes available

Project Member Reported by lijeffrey@chromium.org, Apr 26 2016

Issue description

Currently, all metadata for try jobs are only captured upon completion. If there are errors, much information is lost making determining the root cause difficult. Additionally, we should add whether or not compile targets and heuristic results were used, which are available as soon as the try job is triggered.

1. WfTryJobData should be created as soon as the try job request is made to buildbucket. By then, request_time, has_compile_targets, and has_heuristic_results should all be avilable

2. Try job start_time should be stored as soon as the first response from buildbucket is received, which should contain start_time and try_job_url

3. Upon completion, all other information should become available
 
Status: Fixed (was: Assigned)
Status: Verified (was: Fixed)

Sign in to add a comment