[Bisect] Should CC original owner/reporter in case it gets assigned to culprit CL owner. |
|||||
Issue descriptionI ran a bisect this morning, and the bisect was successful. (https://bugs.chromium.org/p/chromium/issues/detail?id=610015) But I have received no email updating me of that. Because (I believe), the bisect replaced the owner with the culprit CL author. So I was not able to find the bug in my list of bugs either. Quick hack, if you file a regression bug, CC yourself. Fix: Make sure original reporter/current owner are in the CC list before replacing the owner with the culprit CL author. See bug https://bugs.chromium.org/p/chromium/issues/detail?id=610015 for an example
,
May 10 2016
,
May 10 2016
This is a feature request, bisect always replaces the original issue owner with the culprit CL owner, but it makes sense to cc the original issue owner. Assigning this to Kari as this needs modification from Perf dashboard. https://github.com/catapult-project/catapult/blob/master/dashboard/dashboard/update_bug_with_results.py#L210
,
Aug 30 2016
I think this should be done by cc-ing the reporter instead of assigning them. We already have a bug for that in the catapult bug tracker here: https://github.com/catapult-project/catapult/issues/2333
,
Feb 3 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by fmea...@chromium.org
, May 10 2016