New issue
Advanced search Search tips

Issue 753297 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

Gerrit: perf_try support for feature branches

Project Member Reported by enricobacis@google.com, Aug 8 2017

Issue description

When running a perf_try job on a feature branch, the patch seems to be applied on top of origin/master HEAD instead of on the base of the feature branch.

Checking the output of the failed perf_try job on this feature branch CL
( https://chromium-review.googlesource.com/c/600667/7 ), the patch seems to fail because of a merge conflict, which should never be the case on a feature branch.

An additional advantage of comparing the CL with the base of the feature branch, is that the only differences in the code should come from the CL, and the benchmark comparison will be affected only by changes in the CL.
 
Cc: -machenb...@chromium.org
Owner: machenb...@chromium.org
Status: Assigned (was: Untriaged)
Project Member

Comment 2 by bugdroid1@chromium.org, Aug 8 2017

FYI: Better fix in flight: https://chromium-review.googlesource.com/c/605609
Status: Fixed (was: Assigned)

Sign in to add a comment