Pinpoint failing to see regression, comparison_magnitude unset when user modifies commit range |
|||||||
Issue descriptionSee bug 893863, especially comments 4-6. From chat w/dtu@: wolenetz: Do you have any idea how I could get pinpoint to realize this is actually a regression and continue bisection: https://pinpoint-dot-chromeperf.appspot.com/job/16dcbcdae40000 dtu: yes, there's a comparison_magnitude parameter that hints to pinpoint the size of regression to look for. but looks like it's unset when the user modifies the commit range. would you mind filing a bug?
,
Nov 6
simonhatch@ is on leave this quarter, I'll take a look this week.
,
Nov 6
,
Nov 8
wolenetz@: when you modify the commit range, do you click on a different point on the graph to run the bisect, or do you click on the alert and then modify the start_commit and end_commit?
,
Nov 9
,
Nov 9
,
Nov 10
,
Nov 13
@#4, sorry I missed your query last week. I clicked on the alert, then the bisect button, then modified manually the start and end.
,
Jan 16
(6 days ago)
stgao's team owns pinpoint now, IIUC |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by wolenetz@chromium.org
, Oct 11