Bisect is looking for builds in the wrong bucket. |
|||
Issue descriptionhttps://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1423 This seems to be due to the refactor to share code between the tryjobs and the bisect. Trjobs and bisect use different buckets.
,
Jul 19 2016
fixed by https://codereview.chromium.org/2160893002/
,
Jul 25 2016
Just to update, the same perfomance builder is again failing, below is the build where the failure is seen, Link to build -- ================= https://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/360 Link to Log File -- ==================== https://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/360/steps/steps/logs/stdio As the Issue -- 627923 is duped into the the Bug ID -- 629240, so updating this issue. Thank You.
,
Jul 27 2016
Comment 3: that's not this issue, but rather issue 631298
,
Jul 27 2016
Issue 630008 has been merged into this issue.
,
Feb 3 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by dtu@chromium.org
, Jul 19 2016