Angle bisects not finishing. |
|||||||||
Issue descriptionSee https://chromeperf.appspot.com/group_report?bug_id=589965 Most of them don't descend into the angle roll, but this one did and only seemed to have tested one CL: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1546 Why didn't they finish? The results aren't clear from the quicklog. Assigning to robertocn, since he is working on bug triage rotation today.
,
Mar 9 2016
,
Mar 16 2016
Logs are lost, but from the buildbot page I notice that I build timedout after 24 hrs. Bisect posted a build request and was waiting for the archive for 5hrs. I assume build might have failed on the builder or was in queue to get its turn. In these kind of situation, bisector should constantly poll the builder for build status and move on with other revisions in the range if build fails or takes more time.
,
Mar 16 2016
,
Mar 19 2016
,
Mar 19 2016
Is anyone working on this? Sorry I don't understand, how do we prevent these jobs from failing?
,
Mar 21 2016
Roberto: ping, since you're on bug triage rotation again today.
,
Mar 22 2016
The check for failed builds finally landed today, launching new jobs to see if we get better results.
,
Aug 10 2016
,
Feb 3 2017
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by sullivan@chromium.org
, Mar 4 2016